[bgro]

No developer working on account authentication for sites has ever used the correct regex to parse and validate a legitimate email. I wouldn’t be surprised to see things like if you’re at anything other than @Gmail.com the email gets flagged as invalid. Maybe there’s a manual approval step here but better just flag your session as suspicious activity or failed bot check for the time being.

Or in the spaghetti parsing, obviously nobody is going to have swear words in their email. Go ahead and blanket ban all of that. And then @JohnsonAssociates.com gets banned.

I’ve also seen email parsing rules get applied to login screens too. So the valid email rules get updated and suddenly you fail validation trying to log into your already existing account. Ran into this today actually.

So having your own domain might solve some problems but you may still end up needing multiple accounts with devs refusing to use correct parsing rules.