On Thu, Sep 27, 2007 at 02:54:08PM +0100, Stephen Gran wrote: > This one time, at band camp, [EMAIL PROTECTED] said: > > On Thu, Sep 27, 2007 at 12:59:18PM +0100, Stephen Gran wrote: > > > This one time, at band camp, Darren Salt said: > > > > I demand that Lars Wirzenius may or may not have written... > > > > > > > > [snip] > > > > > Obfuscation which can easily be reversed by a human, but not so > > > > > easily by a > > > > > computer, does not render contact information incorrect. If I write my > > > > > e-mail address as follows, it's still correct: "My full name is Lars > > > > > Ivar > > > > > Wirzenius, and you can send me e-mail by taking my initials and > > > > > putting > > > > > them in front of the at sign and iki.fi after it." > > > > > > > > But is that LIW or liw or Liw or...? :-) > > > > > > I know it was a joke, but since email is (usually) case-insensitive, it > > > won't matter in practice. > > > > not at all. > > > > rfc2821 2.4 "The local-part of a mailbox MUST BE treated as case sensitive." > > > > So, senders should use LIW@ but the MTA at the other end is free to accept > > liw@ and Liw@ etc ... > > "However, exploiting the case sensitivity of mailbox local-parts impedes > interoperability and is discouraged." > > Hence the '(usually) case-insensitive'.
yes, I caught that '(usually)'. figured that was what you meant :-) I don't think that drawing the conclusion I did counts as "exploiting the case sensititivity of mailbox local-parts", it being explictly covered in the passage I quoted, although I would agree that perhaps Lars should be discouraged from depending on this interpretation ... ;-) On the other hand, relying on the case-insensitivity of the local-part is explicitly broken, even if it works in practice :-) I'm so glad we have standards to make these things clear ;-) Regards, Paddy -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
