Hacker News new | ask | show | jobs
by ashley95 7 days ago
This is cute and all. But for anyone coming here for real-world advice: just use a regex, normalize to lowercase, and surface any errors to users so they know if their email got rejected. This will avoid 99.9% of issues and work for 100% of real human users. This is what everyone else does, and if you have a user with an esoteric email, they will still be able to furnish another one that passes this validation.
2 comments
pif 7 days ago
Display a warning and propose to edit instead of blocking the operation: your customers will be happier!
link
tracker1 6 days ago
Verify all email address entries before you start using it... I absolutely HATE how much garbage I get because a few people don't understand you actually have to get an email address before you start using whatever you like.
link
ashley95 4 days ago
Right, maybe I worded my response a bit vaguely. Of course you need to do an opt-in and verify them.

My point was rather that if you are operating a service with human users, there is no need to deal with quoted local parts, mixed-case, non-ascii, etc. You will just run into bugs (oh, the user signed up on an iPhone and the email field was auto-capitalized and now they can't find their account?) for almost no marginal benefit.

link