I also reached out to them on Twitter but they directed me to this form. I followed up with them on Twitter with what happened in this screenshot but they are now ignoring me.
I also reached out to them on Twitter but they directed me to this form. I followed up with them on Twitter with what happened in this screenshot but they are now ignoring me.
Exactly. After the @ they should just confirm there’s at least one period. The rest is pretty much up in the air.
Even that would be technically incorrect. I believe you could put an A record on a TLD if you wanted. In theory, my email could be
me@example.Another hole to poke in the single dot regex: I could put in
fake@com.with a dot trailing after the TLD, which would satisfy “dot after @” but is not an address to my knowledge.Something something http://[2607:f8b0:4004:c09::8a] and http://3627734062 are valid url’s without a dot, and are probably valid for emails too, but I’m too lazy to actually verify that.
deleted by creator
And this sort of thing is exactly how you end up with bad regex that invalidates valid emails.
The point isn’t to invalidate all bad emails. It’s to sort out most of them.
I’ve had issues with this in using govt emails too. DOD accounts all have multiple dots based on branch and dept. It broke so many systems and emails never went through.
Which would still be technically wrong. There does not need to be a dot.
The easiest and most correct check: any character, then @, then any other character.