5 ms·

The relevant RFCs make it clear what is a correct eMail address. Why should we have to put with lazy or incompetent coders who can't be bothered to meet the sta

The relevant RFCs make it clear what is a correct eMail address. Why should we have to put with lazy or incompetent coders who can't be bothered to meet the standard?

retube 16y ago
Yeah but not all email addresses are RFC compliant. Plenty of mail servers accept, or can be configured to accept, non-compliant addresses.
- frobozz 16y ago
  That's not the issue at hand - the grandparent comment advocates that you shouldn't even expect a service to accept RFC-Compliant addresses. Validating against the RFC is more, not less permissive than the position held by the grandparent comment.
  - soulclap 16y ago
    Well, just go ahead and try signing up at facebook with {^|~!}@gmail.com then.
    - EliRivers 16y ago
      So because Facebook don't know what counts as a valid eMail address, everyone else has to adapt to them?
      - T-hawk 16y ago
        When that's the behavior of the 800-pound gorilla, then the answer is yes. IE6 didn't know what counts as valid DOM or CSS but everybody else adapted to it.
  - retube 16y ago
    Yup, agreed. And of course RFC compliance only specifies syntax. It would pass blah@blah.hlah.
soulclap 16y ago
You probably got me wrong. In a perfect world, it would work just as specified in the RFC, everywhere and I am all for that. But obviously that's not the case. And I am not encouraging people to be lazy and sloppy, I am just saying considering the 'real world', you are better off with an email-address that does not contain any too unusual characters (e.g. - _ . should be fine, as those are commonly used).
tomjen3 16y ago
Because those RFCs are insane. Seriously comments (nested even) in email addresses?