Hi Marcus
The change of adding an L to
auth_username_format = %Ln"indeed has the side effect, that LMTP delivers wrongly cased addresses. But the main effect and disadvantage is, that authenticating logins with wrongly cased usernames do also succeed, which I actually do not like to happen.
Isn't there another solution? A feature request for a new option lmtp_username_format?
Regards, Adrian.
Am 16.12.13 21:25 schrieb Charles Marcus:
On 2013-12-16 2:36 PM, Adrian Zaugg <adi@ente.limmat.ch> wrote:
How can I tell dovecot to deliver "USER" to the mailbox "user" aswell?
"Username
LDAP lookups are case-insensitive. Unless you somehow normalize the username, it's possible that a user logging in as "user", "User" and "uSer" are treated differently. The easiest way to handle this is to tell Dovecot to change the username to the same case as it's in the LDAP database. You can do this by returning "user" field in the pass_attrs, as shown in the above example.
If you can't normalize the username in LDAP, you can alternatively lowercase the username in dovecot.conf:
auth_username_format = %Lu"
See: http://wiki2.dovecot.org/AuthDatabase/LDAP/PasswordLookups
This really should be the default...