Here is some good reading on the matter: http://dalibornasevic.com/posts/63-email-address-validation-and-encodings
I understand that this could be a lot slower. Perhaps config option for what specs to use?
You'll find that a whole bunch of these validate correctly after #258:
> validator.isEmail('"()<>[]:,;@\\\\\\"! #$%&\'*+-\/=?^_`{}| ~.a"@example.com')
true
> validator.isEmail('"pink panther"@example.com')
true
> validator.isEmail('"pink@panther"@example.com')
true
> validator.isEmail('pink.panther@localserver', {require_tld:false})
true
> validator.isEmail('眉ber@m眉nchen.com')
true
A handful don't, though:
pink.panther@[127.0.0.1]pink\@[email protected]pink\ [email protected]Quick question on this one, yes the spec allows these kind of emails, but which emails are actually used in practice? I'm yet to meet some of these emails, would like people to point me to some examples...
Does it mean that we might need to introduce some strict-mode of sorts to create a difference?
Please place a 馃憤 vote on this comment if you need this feature for your project.
Most helpful comment
You'll find that a whole bunch of these validate correctly after #258:
A handful don't, though:
pink.panther@[127.0.0.1]pink\@[email protected]pink\ [email protected]