dovecot - Nov 2011 - Usage of director without LMTP

Hello,

we want to migrate our dovecot 1.2 installation to verison 2.0 and want
to use the director feature of version 2.
Currently we have a two tier archtiecture, with dovecot proxys and a
mailstore togehter with indexes on NFS. (With the common problems of
this setup...)

For the final setup we want to utilize the director for all protocols
(IMAP,POP,LMTP,SIEVE).
During the transition phase we will not be able to use LMTP for mail
delivery, but we are still stuck with deliver as LDA.
So for mail delivery we will not have the fixed user/server assignment,
but rather a random assignment.

What NFS- and locking settings should be used on the backend servers in
this case.
And should i use different settings for the host the deliver is executed
than the IMAP/POP3 hosts which are accessed through a director proxy.

Thanks in advance,
Oliver Eales

On Wed, 2011-11-16 at 15:02 +0100, Oliver Eales wrote:
> For the final setup we want to utilize the director for all protocols
> (IMAP,POP,LMTP,SIEVE).
> During the transition phase we will not be able to use LMTP for mail
> delivery, but we are still stuck with deliver as LDA.
> So for mail delivery we will not have the fixed user/server assignment,
> but rather a random assignment.
> 
> What NFS- and locking settings should be used on the backend servers in
> this case.
> And should i use different settings for the host the deliver is executed
> than the IMAP/POP3 hosts which are accessed through a director proxy.
All the LDA/IMAP/POP3 servers should use these settings to minimize
problems:

mail_nfs_storage = yes
mail_nfs_index = yes

Once you're using LMTP proxying also you can remove those. Otherwise the
settings are the same.