On 05 Dec 2015, at 11:42, Filip Pytloun filip@pytloun.cz wrote:
Anyway because of the above and high possibility of GlusterFS split-brains, I have decided to setup Dovecot Director according to the docs [1] but I have a couple of questions:
- is custom monitoring still required? Poolmon [2] is 4 year old so I would suppose there's some progress since that?
I think it's always going to be a separate script. In different environments people may want to do it slightly differently.
- documentation states that it still doesn't work for LMTP [3]? Which is probably important for my setup, because both Postfix servers are using dovecot-lmtp for mail delivery so there can be still some issues (but probably less frequent?) when both servers will deliver new mails for one user at once. So do I really have to split directors from backends?
You can run director and backend in the same servers, but they'd have to be in different config files (so two dovecot instances). Or you could also do it with a single instance:
[3] "LMTP however doesn't currently support mixing recipients to both being proxied and store locally."
This is a problem only if there are multiple recipients in the same LMTP session. So if you configure your MTA to restrict the recipient limit to 1, this mixing can't happen and a single Dovecot instance can work.
v2.3 will solve this problem completely.