Hi,
the Dovecot Director determines the backend host in some way by hashing the username:
http://wiki2.dovecot.org/Director
For normal logins username@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@example.org*masteruser1@example.org username@example.org*masteruser2@example.org username@example.org*masteruser3@example.org
go to the same mailbox backend, in order to avoid NFS caching conflicts for mailbox username@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