Alexandr Sabitov
2013-Mar-03 22:54 UTC
[Dovecot] Exposing masteruser info to cllients via lmtp-proxy connections
Hello, Please somebody suggest me how to remove the "*masteruser" appendix from the dovecot director database while using masteruser authentication. My situation is: - all users get authenticated in LDAP on the dovecot-director frontend - then they are forwarded to dovecot backend as username*masteruser ( this is a way how to proxy users with encrypted passwords). To enable it a added an extra field in LDAP-dovecot configuration: destuser=%u*masteruser This works OK, but problems are: - I have lmtp-proxy on the dovecot frontend and I have to use the same "%u*masteruser" field in lmtp passdb because the director thinks that me at mail.com and me at mail.com*masteruser are different users and would send lmtp-proxy connections to other dovecot backend. Here is a problem: "Delivery-To" and "Received" fields in any email contains "*masteruser" ! I need to remove any mentions about "masteruser" authentication from client emails. Also another little problem: - If I run "doveadm status" tool then to get user's data I need to specify user as "username*masteruser" Thank you in advance. Alexandr Sabitov Netregistry
Timo Sirainen
2013-Mar-20 16:52 UTC
[Dovecot] Exposing masteruser info to cllients via lmtp-proxy connections
On 4.3.2013, at 0.54, Alexandr Sabitov <alexandr.sabitov at netregistry.com.au> wrote:> Please somebody suggest me how to remove the "*masteruser" appendix from the dovecot director database while using masteruser authentication.Not sure about how to fix that, but maybe you can get rid of the *masteruser completely? Instead of using that, just return "master=masteruser" field. http://wiki2.dovecot.org/PasswordDatabase/ExtraFields/Proxy#Master_password