News for hackers. Stuff that matters.
Re:The Correct Way to Validate Email Addresses by tempestn on Wednesday September 07, 2016 @07:43PM (#12448979)
Also relevant was, "If you have a well laid-out form with a label that says “email”, and the user enters an ‘@’ symbol somewhere, then it’s safe to say they understood that they were supposed to be entering an email address."

In other words, it does make sense to check that they entered an '@' symbol somewhere, since it shows that they understood it was an email field. Any 'validation' beyond that is useless.

Re:The Correct Way to Validate Email Addresses by danso on Wednesday September 07, 2016 @07:46PM (#12449001)
How about more than one @ sign? Does the email address spec exclude the possibility of more than one @ symbols?
Re:The Correct Way to Validate Email Addresses by tempestn on Wednesday September 07, 2016 @07:56PM (#12449060)
It doesn't matter. If they have typed an @, they probably understand that it's an email field. Trying to validate to the spec beyond that is pointless, for reasons thoroughly covered in the article.
Re:The Correct Way to Validate Email Addresses by kej on Wednesday September 07, 2016 @07:54PM (#12449042)
Nope, that's valid if one of them is quoted: "[email protected]"@example.com
Re:The Correct Way to Validate Email Addresses by ediblenergy on Thursday September 08, 2016 @01:19PM (#12454998)
It actually used to (maybe still does) signal routing information[1]. An example from the RFC is "@ONE,@TWO:JOE@THREE" [1]: https://tools.ietf.org/html/rfc821
Re:The Correct Way to Validate Email Addresses by zeveb on Thursday September 08, 2016 @11:05AM (#12453662)
The local-part may contain a quoted @: "@"@example.invalid is a valid email address.

@ signs are also permitted in comments: (ted@home)[email protected] is also a valid email address.