search for: domain_first

...g any password). Obviously, in my LDAP backend I can configure something to authorize "someone" to access to "anotherone"'s mailbox. At this momment, I'm trying to use someone at domain.com@anotherone at domain.com as username, with a passdb that uses %{username}@%{domain_first} to authenticate the user, but I'm having problem to configure a userdb map to get the mailbox, because the %{domain_first} variable returns just "domain.com". To fix this, I could use "someone at anotherone@domain.com", but this has problems with virtual domains an diff...

Hi Guys, When I have a username like foo-bar-candy can I get/seperate foo, bar and candy as single variables for my storagepath of the usermail ? Thanks, Matt

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?

very intrigued by your solution Timo, have attempted something similar in the past to no avail. When I tried I was unable to retain the user at domain when setting the domain as extra field - protected is new to me and can't find documentation - but also doesn't work :( # cat passwd.domains 10.100.1.1:::::::domain:protected=foo.org 10.100.1.2:::::::domain:protected=bar.org # cat