[Dovecot] Dovecot Director and MasterUsers
Daniel Parthey
d.parthey at metaways.de
Tue Apr 8 13:54:16 UTC 2014
Hi,
the Dovecot Director determines the backend host in some way by hashing the username:
http://wiki2.dovecot.org/Director
For normal logins username at example.org, the director always gets the same hash
for the same username and ensures that the login is always proxied to the same backend.
But what about MasterUsers in combination with Dovecot Director?
http://wiki2.dovecot.org/Authentication/MasterUsers
Which configuration directives should be used to make sure that logins
username at example.org*masteruser1 at example.org
username at example.org*masteruser2 at example.org
username at example.org*masteruser3 at example.org
go to the same mailbox backend, in order to avoid NFS caching
conflicts for mailbox username at example.org which should always
reside on the same NFS client?
Is the master user cut off from behind the master_user_separator?
How is the director hash exactly calculated?
Can the director hashing algorithm be configured in some way?
Regards
Daniel
More information about the dovecot
mailing list