4 ms·
I have something similar when I used contact@<firstname>.<lastname>.name There were various ways in which that failed. 1. ".name" was pretty new by then, so s
by omnibrain 6y ago
I have something similar when I used contact@<firstname>.<lastname>.name
There were various ways in which that failed.
1. ".name" was pretty new by then, so some frontends did not accept it
2. some frontends objected to the third level of my domain part, accepting third levels only in such cases as the well know. ".co.uk" for example
3. some frontends let me sign up, but something in the backend failed, I can only suspect if it was the ".name" tld or my third level, but I never got any mails after signing up
- lorenzhs 6y agoThe number of sites that send mail to "foo@bar.com" when you give them "foo@sub.bar.com" is staggering, too. It's a mystery to me why they would ever want to do that, but it happens a lot.
- 0xFluegel 6y agoI can see how that happens immediatly... var domain = addr.split(['@','.']).take_last(2) var tld = domain[1] // check TLD against wacky rules... See, boss, it's easy. What's next?
- snet0 6y agoIt's also possibly just some arcane regex incantation that someone implemented 12 years ago and nobody has been able to decipher it since.
- Sebb767 6y ago> 2. some frontends objected to the third level of my domain part, accepting third levels only in such cases as the well know. ".co.uk" for example This is actually not such a rare edge case. My university, for example, uses <name>@students.<university>.de . So there's really not much excuse for not handling this.