Sieve vacation won't send second reply after timeout interval.

2016-09-21 Thread David Williams
Hi

I solved this by updating to Dovecot 2.2.24



David


Director keeping IMAP connections alive

2016-09-21 Thread Webert de Souza Lima
Hello,

I have a 2 director - 2 dovecot set up in a cluster.

>From time to time I notice high usage of RAM by dovecot process, and
analyzing with doveadm who,
I see many users with dozens, even hundreds of PIDs.

Inspecting those PIDs I see each one of them is an IMAP connection, coming
from either director process, and ESTABILISHED.

A deeper analysis shows me that there ltos of connections from the same
users to BOTH dovecot instances, but as I am using director, this shouldn't
happen, right? Ok. The thing is, one of the dovecot instances have only old
connections (like 3 days old) and the other dovecot have some old and some
newer connections.

So, director is redirecting recent connections to the right dovecot, as
expected, but it is keeping many of old and unused connections open,
consuming resources.

output of doveconf -n from dovecot:
http://pastebin.com/trMEjeAs

output of doveconf -n from director:
http://pastebin.com/EUpHYMKY

Thanks.


dsync-server: Configure lock-file location?

2016-09-21 Thread Udo Waechter
Good day everyone,

I have a situation where my mail-folder structure (mdbox) ist like this:

My users have the following data:


$ doveadm user x...@xx.com

field   value
home/srv/mail/
mailmdbox:foo/x...@xx.com/

I also do replication between 2 nodes. Now, I sometimes (when a lot of
replication is happening I get the following errors:

dovecot: dsync-local(x...@xx.com): Error: Couldn't lock
/srv/mail//.dovecot-sync.lock: Timed out after 60 seconds

This of course not only for x...@xx.com

It seems to me, that my mailbox structure should rather be:

$ doveadm user x...@xx.com

field   value
home/srv/mail/foo
mailmdbox:x...@xx.com/

in order to get rid of these messages? Unfortunatly I cannot change that.

I've searched around and took a look into the code of dsync-server,
unfortunatly the path to the lockfile is not configurable.

Is there a way to somehow configure the lock-file location for dsync-server?

Thanks very much,
udo.




signature.asc
Description: OpenPGP digital signature