> Which is actually not a valid address
That means validation was working correctly. The email addresses are invalid even if the server will accept email for them.
There's only one sensible validation script: "Send an email with a confirm link".
Taking action with side-effects on entirely unvalidated user input is usually a pretty bad idea.
Re:How to get gmail.com banned (2011)
by GauntletWizard on Tuesday August 04, 2015 @02:07PM
(#10005129)
Sadly, if you're sending e-mail sanely, your mail provider likely validates recipients, and will be annoyed at you if you send them recipients they think are bogus.
Re:How to get gmail.com banned (2011)
by belovedeagle on Tuesday August 04, 2015 @11:36PM
(#10007915)
The relevant rfc (on mobile; don't remember which) specifically states that intermediate servers must not validate mailboxes (local parts). And honestly the domain should be "validated" by the server doing an mx lookup; let dns handle it.
So wait, what now? So you can have an email address like [email protected]? Can you give me a generic example?
Yeah, I'm with the other guy, regardless of whether or not it's a good idea to do validation (it's not), that's not an address that should pass validation because it's not a valid domain or hostname.
I could see it being less of a big deal in the mailbox portion given that it's now kinda kosher to ignore dots there.
[1] https://tools.ietf.org/html/rfc2822#section-3.2.4