6 ms·
I can only presume this regex is there because Google had to block various scammers trying to use email hosting donain names when novel TLDs came onto the marke
by jeroenhd 2mo ago
I can only presume this regex is there because Google had to block various scammers trying to use email hosting donain names when novel TLDs came onto the market. You can try to manage gmail.zip or outlook.mov but Google will probably flag you as a scammer if you try to email from them. Just because web.de isn't well-known outside of German circles doesn't mean the risk doesn't exist. These email providers, especially the ones hosted by Microsoft, have a history of buying multiple TLDs to offer users a localised email domain.
Blocking a second level domain like the Ukranians tried to use is surprising, though. I guess it's to prevent domains like outlook.co.uk or something like that?
These regexes were put there for a reason so I doubt they'll get removed, but if they fix their frontend-only detection script you're going to be locked out of your domain some day if you force your way through their checks. Seems awfully risky.
- chinathrow 2mo agoThw regex on the frontend only makes zero sense though.
- manarth 2mo ago> "gmail.zip or outlook.mov" will probably flag you as a spammer > "web.de isn't well-known outside of German circles" I'm not sure that "gmail" or "outlook" would cause people to think that the sender was in some way "authoritative", but I can understand the organisations wanting to discourage potential pretexting (plus the trademark violation). I'm not sure how "web.de" or "web.one" would be perceived as especially trustworthy though. "It must be genuine, it's from the official Web"?