-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update isEmail to latest specs #469
Comments
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:
|
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 |
Please place a 👍 vote on this comment if you need this feature for your project. |
Here is some good reading on the matter: http://dalibornasevic.com/posts/63-email-address-validation-and-encodings
The text was updated successfully, but these errors were encountered: