6 ms·
> because the rules keep changing the single relevant rule is the same ever since: do an opt in. The spelling of the email address is of zero relevance and mu
by mro_name 5y ago
> because the rules keep changing
the single relevant rule is the same ever since:
do an opt in. The spelling of the email address is of zero relevance and must not be nosed at.
- Semaphor 5y agoYou forget one thing: People make typos. Assuming Sony blocks all LEN(TLD)>3, do you think they’ll lose more customers than they’ll lose from them not getting their validation mail because they typoed their mail? I’d bet that the first group is far smaller than the 2nd. Now instead of blocking it would be nice if they just asked if you are really sure that’s your email, but it’s probably still better than just accepting everything and trying to send a confirmation, both from a business and from a customer-friendliness perspective.
- mro_name 5y agohaven't forgotton. Typos happen not only in the tld. So check and warn if you will. But indeed let it happen and don't gag people. You need the opt-in and have people confirm or repeat in case.
- amerkhalid 5y agoRan into this issue at one of the job. Developers wanted to implement validation based on RFCs. But QA and business refused to believe RFC rules and instead wanted their own rules. Guess what we end up implementing.
- Freak_NL 5y agoWhat did you end up doing? Anything more than checking if the string contains @ is wrong, and you should be able to find dozens of articles supporting this argument by now.
- amerkhalid 5y agoWe checked for dot in addition to @. There was probably also check for special chars which makes sense, iirc. One win we had was, we didn't hardcode any tlds.
- mro_name 5y agoeven a RFC doesn't guarantee the existence of a mailbox - if the address e.g. has a typo in the name. And own rules very much sounds like management ever wanted to invent something.