Actually that isn't the issue. The issue is like one I had with ldap,
till I modified it to be case sensitive. And that is, atleast in my
old pre-1.0 version of dovecot, it would authenicate the user with
mixed or uppercase letters, then use that username for the mailpath.
Since the mailpath is case sensitive, it would respond to the user
saying they have no email, cause the path isn't found. But in reality
they have email, in the all lower case letter version of their username.
My fix was to adjust the ldap schema to have case sensitivty, and then
add for user idiot proofing, force usernames to lowercase in horde.
Quoting Noel Butler <[email protected]>:
On Wed, 2009-08-19 at 01:41 -0400, Timo Sirainen wrote:
On Aug 19, 2009, at 1:37 AM, Benny Pedersen wrote:
> others have found this problem ?
Dovecot auth isn't case-insensitive. But MySQL is, and I guess you're
using it? There are several different ways around it.
Which is not a problem since most (all) MTA's normally treat user@ as
case insensitive.
Only an incompetently written portal or mail-management
script/software/setup would allow a user foo@ *and then* allow FOO@
or Foo@ etc to be added.
If you use management software that does that, dump it, and if it's
in-house written, I'd kick the programmers ass for allowing it to be so
poorly designed in the first place.
RFC2821
The local-part of a mailbox
MUST BE treated as case sensitive. Therefore, SMTP implementations
MUST take care to preserve the case of mailbox local-parts. Mailbox
domains are not case sensitive. In particular, for some hosts the
user "smith" is different from the user "Smith".
However, exploiting the case sensitivity of mailbox local-parts impedes
interoperability
and is discouraged.
^^^^^^^^^^^^^^^^^
So although permitted, it is only a fool that actually does it.
