Hi, I'm currently using Dovecot 1.1.18 with storage over NFS and there's been the occasional corrupt index. I'm going to be installing a new set of servers soon and would like to start using Dovecot 2.0. I've had a look at the bit there is on the new Dovecot director, but I'm not totally sure how it's intended to be used. Should I install Dovecot on the software load balancers (IMAP/POP3 and other services balanced by haproxy) and configure the director on there? I'm also using maildrop at the moment but would like to switch to Dovecot deliver at some stage. Since mail is delivered to a random mail server (they both have access to the NFS shares), won't I run into the same index problem? Should I look at per user transports before then or can director also be used to effect Dovecot deliver? Thanks Guy -- Don't just do something...sit there!
On Tue, 2010-09-07 at 12:27 +0100, Guy wrote:> Should I install Dovecot on the software load balancers (IMAP/POP3 and other > services balanced by haproxy) and configure the director on there?You need two or more Dovecot proxy-directors somewhere. I don't know if you should put them to software load balancers.> I'm also using maildrop at the moment but would like to switch to Dovecot > deliver at some stage. Since mail is delivered to a random mail server (they > both have access to the NFS shares), won't I run into the same index > problem? Should I look at per user transports before then or can director > also be used to effect Dovecot deliver?You should use LMTP, which can also be proxied via director.