6 ms·
The rules never changed. One should only match if the email contains "@" (or better, use browser email inputs), and do the verification by sending an email to i
by Aissen 5y ago
The rules never changed. One should only match if the email contains "@" (or better, use browser email inputs), and do the verification by sending an email to it (as you said). Validating TLDs was never a good idea, and still isn't.
Yes, you can put UX helpers for spelling mistakes on most common domains (gmail…) (helps the majority), but never make it a hard error. It's that simple.
- hu3 5y agoIIRC the RFCs for email address specify mandatory local-part@domain. Not just @. edit: https://datatracker.ietf.org/doc/html/rfc2822#section-3.4.1 https://datatracker.ietf.org/doc/html/rfc2822#section-3.4.1
- krageon 5y agoThe RFC has a specified regex for validating email that absolutely nobody uses. Given that, matching on an @ (if you do it at all - even that is a bad idea. Just send an email) is the easiest approach that you're least likely to mess up.
- hu3 5y agoTotally agree with just sending an email and see if it sticks. Perhaps tech giants could sponsor a new RFC for email addresses.
- krageon 5y agoA tech giant sponsored RFC would just be what (US) tech giants feel is convenient and nothing else. I am vehemently opposed to them getting an even bigger say in how the internet works, it's going downhill fast enough as it is.