You are right but they discourage MTAs from exploiting it. The user portion is case sensitive and the domain portion is case insensitive. >From RFC 2821:
"...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." More here: http://www.ietf.org/rfc/rfc2821.txt On Sep 27, 2:15 pm, mdipierro <[email protected]> wrote: > It is not obvious to me that upper and lower case in emails should be > equivalent? Is the an RFC about this? > > On Sep 27, 11:46 am, "mr.freeze" <[email protected]> wrote: > > > I use a custom auth table and apply the TO_LOWER validator on email > > and username for this reason. I agree, something like this should be > > done in the default auth table. > > > On Sep 27, 2:07 am, Thadeus Burgess <[email protected]> wrote: > > > > If you sign up with an account that has a capital letter in the email, it > > > will say invalid login when you attempt to sign in. > > > > It only works if your email is all lower case. > > > > I have requires email confirmation, and requires approval turned on. > > > > Also, the email field seems to be case SENSITIVE, meaning I can sign up > > > with > > > the same email if I capitalize different letters. > > > > -Thadeus --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
