5 ms·
What this article really showed me that this RFC is actually pretty harmful. Supporting all of the rules outlined in the spec is probably a huge burden for mai
by Yaina 5y ago
What this article really showed me that this RFC is actually pretty harmful.
Supporting all of the rules outlined in the spec is probably a huge burden for maintainers of mail clients and servers. Obviously some parts of the spec are going to be omitted. It's hard to blame them for it, but the same person that rightfully skipped over implementing the routing thingy might've also wrongfully assumed there won't be a Japanese character in the address. And that's what's so bad.
You might introduce more issues in your system, by taking the full spec into consideration for your validation, instead of using the whatwg regex someone posted here.
- nradov 5y agoWell if there are problems with the RFC then you should work with the IETF to correct those. They have an open standards development process.
- awestroke 5y agoAnother option is to just ignore the RFC
- forgetfulness 5y agoThat does mean that there will only be an ad-hoc undocumented standard for email addresses, rather than one that's serviceable. Web application validation forms add a different layer to the standard and are sort of hard to tame; anyone can push together a few lines of PHP or Javascript code and conjure their own email address standard out of thin air.
- gifnamething 5y agoWill be? There is an ad-hoc standard. If the standard fails to be used, the standard is defective.
- numpad0 5y agoIsn’t it just not very nice to ignore a Request for Comments