deep-email-validator
deep-email-validator copied to clipboard
More flexible parsing options and a stricter default
trafficstars
Fixes #80. Fixes #31. Fixes #21. Fixes #11.
Changes:
- Moved the main parsing function to a more stricter one with a sensible default that should cover the typical usage (web submissions). I left "isEmail" alone as the function name never implied it does any sanitation.
- Fixed a potential SMTP command injection.
I can't get two tests to pass even without modifications, maybe the email domain used in the test changed their configuration?