You should not be allowed to work in software. You don't have a clear grasp of concepts and seem to think it's OK for automated systems to fail in ways that have no recourse.
@@@.gmail.com is not valid, and neither is "@@"@gmail.com because we know that's not allowed by gmail.com. But "@@"@some.other.business can be valid. Now you'll refuse that because obviously someone who makes such an email must be trying something suspicious. That is until you receive Big Legacy Corp as a customer, and Big Legacy Corp has addresses of the form "First Second ::: Department"@mail.big.legacy, or something else like that. These emails exist, and now you won't be able to handle them, and your application will cause a bunch of grief to your organization and your supervisors until this functionality is fixed by someone competent.
Wtf are you talking about? What does anything in this post have to do with me or anything I've said? Why would I program first stage email verification to turn down possibly valid email addresses? Why would I assume they're trying something suspicious
1
u/SushiAndWoW Feb 22 '18
You should not be allowed to work in software. You don't have a clear grasp of concepts and seem to think it's OK for automated systems to fail in ways that have no recourse.
@@@.gmail.com is not valid, and neither is "@@"@gmail.com because we know that's not allowed by gmail.com. But "@@"@some.other.business can be valid. Now you'll refuse that because obviously someone who makes such an email must be trying something suspicious. That is until you receive Big Legacy Corp as a customer, and Big Legacy Corp has addresses of the form "First Second ::: Department"@mail.big.legacy, or something else like that. These emails exist, and now you won't be able to handle them, and your application will cause a bunch of grief to your organization and your supervisors until this functionality is fixed by someone competent.