[Form validation] Built-in email rule says 'bad@email' is a valid email.
See original GitHub issueI entered bad@email
while testing form validation using the built-in email rule and it came back as valid. Is this a bug? I would say the bad@email
is not a valid email.
Issue Analytics
- State:
- Created 7 years ago
- Comments:6 (1 by maintainers)
Top Results From Across the Web
Email address validation in C# MVC 4 application
I have an MVC 4 web application and I need to enter and validate some email addresses, without sending an email to the...
Read more >Email Validation- Microsoft Form
I need create a form with the fields "Name", Telephone" and "Email Address" my question is how can I restrict or validate the...
Read more >modern-cljs/tutorial-12.md at master - GitHub
When you submit the Login Form you should receive a Please complete the form message anytime you do not provide the email and/or...
Read more >What is email validation? - Quora
In order to remove them, invalid, incorrect, nonexistent, and undeliverable email addresses are checked on mailing lists. This process is known as email...
Read more >The 100% correct way to validate email addresses
Did the user correctly type their email address into this field? If you have a well laid-out form with a label that says...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
How about just adding a flag for whether it is strict - per RFC 5321 validation or less-strict, aka, practical - per RFC 5322
Then it is right for all contexts.
I don’t see why this is an issue if you want to use RFC 5322 then you can just specify a custom regex rule.