News for hackers. Stuff that matters.

A comment on Complexities of e-mail validation logic. Parent comment

Re:Complexities of e-mail validation logic by welder on Monday May 24, 2021 @11:36AM (#27265593)
Yes, in practice I've found the exact same thing. Either use an email validation service or be more restrictive than the RFC. [1] Also prompting "Did you mean [email protected]?" when the user types "[email protected]" helps a lot with human input errors. [2]

[1] https://www.mailgun.com/email-validation/

[2] https://www.npmjs.com/package/mailcheck

[ Parent | on HN ]
Re:Complexities of e-mail validation logic by ivraatiems on Monday May 24, 2021 @12:02PM (#27265968)
Except that as someone with an email at a .co domain, I get really irritated when it asks me "do you mean [mydomain].com?"

I always have to tell people, in real life, "it's .co, not .com," just in case - humans do this too.

[ Parent | on HN ]
Re:Complexities of e-mail validation logic by cygned on Monday May 24, 2021 @12:29PM (#27266349)
Worse, I had services trying to be smart correcting .co to .com
[ Parent | on HN ]
Re:Complexities of e-mail validation logic by welder on Monday May 24, 2021 @12:07PM (#27266040)
Yep, it's solving for the majority case. As long as it doesn't block signup you can just ignore it.
[ Parent | on HN ]