News for hackers. Stuff that matters.
Re:Falsehoods programmers believe about email by kuon on Thursday September 01, 2022 @04:53AM (#32673777)
I think the part before the @ is actually case sensitive per RFC, but most mail server will treat it case insensitive. But I am not sure I am reading the RFC correctly, citation:

Verbs and argument values (e.g., "TO:" or "to:" in the RCPT command and extension name keywords) are not case sensitive, with the sole exception in this specification of a mailbox local-part.

Re:Falsehoods programmers believe about email by a-dub on Thursday September 01, 2022 @05:40AM (#32674108)
rfc 822 local-parts (stuff to the left of @) are weirdly permissive.

you can include quoted spaces, carriage returns and newlines (!)

Re:Falsehoods programmers believe about email by jwilk on Thursday September 01, 2022 @07:10AM (#32674746)
Quoting CR and LF is no longer allowed in RFC 2822.
Re:Falsehoods programmers believe about email by jwilk on Thursday September 01, 2022 @12:02PM (#32678398)
Correction: it's still allowed, only considered obsolete. :-/
Re:Falsehoods programmers believe about email by derefr on Thursday September 01, 2022 @12:15PM (#32678599)
Which is to say, nobody of note is still allowing it; you can allow it if you like, for anyone who is still doing it; but if you don't, and someone sends you a message, and it bounces, then, well, they already know why.
Re:Falsehoods programmers believe about email by marcosdumay on Thursday September 01, 2022 @12:29PM (#32678838)
Yes, there are very few rules on the standard that could create two binary-different local parts that resolve to the same value (mostly involving parenthesis). But the mail server can add as many rules it wants, including the very common setting of making completely different names resolve to the same mailbox.