similar to: No subject

Hi:   I did a simple test with Dovecot-2.3.9:            First step : A test account uses mdbox format to store emails with 'mail_location = mdbox:%h/%Ld/%Ln:ALT=%h/altstorage/%Ld/%Ln',           Second step: I adjust 'mail_location = auto:'  and dovecot

some import  configure: plugin {   mail_filter = mail-filter %u # %u = username given to the script as first   mail_filter_out = mail-filter-out %u } service mail-filter {  executable = script /usr/local/bin/mail-filter.sh  user = dovecot  unix_listener mail-filter {    mode = 0600    user = vmail

Hi list, I am faced by a situation where I am trying to make a softphone and a Siemens C450IP talk to each other. Both are hooked up directly to the same asterisk, in the same IP net. - a softphone runs on 192.168.14.3 - the C450IP is at 192.168.14.30 - asterisk runs on the machine known as 192.168.14.1 I am running Asterisk 1.4.11, backported to Debian Etch by Xorcom. If I set

some import  configure: plugin {   mail_filter = mail-filter %u # %u = username given to the script as first   mail_filter_out = mail-filter-out %u } service mail-filter {  executable = script /usr/local/bin/mail-filter.sh  user = dovecot  unix_listener mail-filter {    mode = 0600    user = vmail

Hello,I have 6 Ubuntu 18.04 machines in a Tinc (1.35) network, where 3 are in Spain and 3 in UK.One machine in each country is running Tinc, and as both ends are behind NAT, they both connect outward to an Upcloud VM. The 4 non-tinc machines can Ping and SSH each other without issue, and so from that point of view, the Tinc VPN is working fine.However, the 2 tinc machines can only ping and ssh

I have a server that I have to reach from 2 different networks, the Internet and another private network called downtown and I also have to reach from the server both networks. If I have one of the set of rules running, it works fine, but if I put both set of rules on, it doesn't work. below are my set of rules. Can anyone tell me a how this can be done? Here is the setup. mynetwork

I just modified mail-filter-out.sh like this: cat  mail-filter-out.sh   #!/bin/sh   USER=$1   cat > /tmp/tempfile   cat /tmp/tempfile cat  /tmp/tempfile This message is in MIME format. --nsmail-7bjyg3nr5o-7bmibqhut9 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: base64

Hello everyone, I''ve taken this rating system (http://komodomedia.com/blog/index.php/2005/08/24/creating-a-star-rater-using-css/) and paired it with Prototype (http://prototype.conio.net) so that it reports the ratings via Ajax. I have a working version here (ajax is disabled though): http://kold.homelinux.com/rating_new/rating.html Problem is, the green stars don''t

This looks quite nice at first glance.. http://encytemedia.com/event-selectors/ I would love to hear some of your comments pro or con on how this compares to Behavior. ______________________________________________________________________ Alex Duffield . Principal . InControl Solutions . http:// www.incontrolsolutions.com _______________________________________________ Rails-spinoffs

Hi Louis, Just an update on this. I ran up a new test LXC container and completely removed apparmor. Then install the packages. I got the same errors I thought I would change the DNS from Bind to internal and back to bind. The following is going from Bind9 to Internal root at server5-ad:/var/log# service bind9 stop root at server5-ad:/var/log# systemctl mask bind9 Created symlink

Hai, You posted the correct things here, for a quick fix i I'm buzzy with something else atm but i saw that /dev/urandom part. Add in the bind9 (named) apparmor profile # Samba DLZ /{usr/,}lib/@{multiarch}/samba/bind9/*.so rm, /{usr/,}lib/@{multiarch}/samba/gensec/*.so rm, /{usr/,}lib/@{multiarch}/samba/ldb/*.so rm, /{usr/,}lib/@{multiarch}/ldb/modules/ldb/*.so rm,

Hi, We have some issue with the reverse DNS in Samba AD. We're running Bind9_DLZ on Ubuntu 18.04. The DHCP server(Ubuntu 16.04) is different to the AD server and not in the same AD domain. The DHCP scope points to the Samba AD server as the DNS server When a machine with DHCP assigned address tries to update the DNS record, it is able to update the forward zone but not the reverse zone. The

We recently began seeing server crashes in our cluster related to "pop3-login", which is causing "oom-killer" to be invoked. The server only recovers after a reboot. From dovecot.conf: login_process_per_connection = yes login_processes_count = 16 login_max_processes_count = 256 (Should we try switching processes_per_connection to no?) From dovecot.log: dovecot: Apr 17

Hi Louis, Thank you for that I have made the changes as per below , some items might have duplicated. I then reload apparmor restarted the samba-ad-dc and bind9 services and get the same issue. Every time the forward DNS update works but the reverse doesn't I found a really interesting samba post going back 2017 re the DHCP and DNS

Hi Tim, > Do you have any new insights on the problem with reappearing mail using dovecot replication + pop3? > > It's driving me mad. I'm running dovecot 2.2.34 (874deae) on OpenBSD and it looks like I have the same problem as you have. unfortunately there has been no response, I'm stuck with 2.2.33.2 for the time being. I can only suspect it has something to do with

Hi, Has anyone any idea how to solve or further debug this issue? It seems indeed that it was introduced in 2.2.34 and is still there in 2.3.2.1. I found a couple of posts for this on the mailing list and elsewhere, but no solution: When a message is retrieved and immediately expunged, it gets replicated back from the other dsync node. This usually happens with POP3 but with IMAP as well,