5 ms·

Email on Some TLDs Still Aren't Accepted

16 points by bhartzer 4y ago

CharlesW 4y ago
> …this is why I highly highly encourage businesses to stick to .com for email. I run enterprise email and have for a long time. I've seen the sausage. You can be pretty sure other things will work, but .com will always work .net and .org seem to belong in the "always work" category as well.
- Spivak 4y ago
  Country domains are probably safe as well given how popular .io is.
PebblesHD 4y ago
I possess a very short domain on a widely used older TLD, and even that causes some interesting validation bugs like ‘email domain cannot be less than 6 characters’ for example… If only there were some widely documented standard for validating an email address instead of a perl regex passed around campfires since 1979.
- citrin_ru 4y ago
  There is relatively easy way to validate domain part - resolve and check that there is either an A or an MX record (but if you do resolve be prepared to wait - I've seen domains DNS query to which takes many seconds of even minutes because of poor internet links or infrastructure). And the local part just not worth validating. May be reject non-ascii if your system doesn't support SMTPUTF8. Full RFC syntax is very complex for historic reasons and most simple regexps developers tend to use reject addresses people do use. I try to use a email like me+www.service-name.com@example.com when possible but many services reject such perfectly valid address.
throwaway3r6tg 4y ago
Systems I run (e.g. web based account creation) properly validate & accept gTLDs. However, at the same time, my mail servers will flat out 5xx incoming messages for just about all of them. Why? Spammers. Literally >99.9% of emails that use one of those addresses is pure junk. This Is Why We Can't Have Nice Things (tm) Sure, you can ask for an exception and you'll get it, but due to abuse it's a default deny policy around here. IMO, the whole gTLD racket is just a money grab from ICANN anyway, but I digress.
35mm 4y ago
I have a one letter email @ my domain, which some sites think is invalid. Also post brexit, some places in Spain refuse to accept .co.uk emails, which is fun.
camgunz 4y ago
Maybe this is an argument for batteries included in programming languages. If JS included a real email address parser you wouldn't have the current zoo of variously incorrect regexps out there. Or maybe when you're designing a system make sure your identifiers are regular?

16 points by bhartzer 4y ago

> …this is why I highly highly encourage businesses to stick to .com for email. I run enterprise email and have for a long time. I've seen the sausage. You can be pretty sure other things will work, but .com will always work .net and .org seem to belong in the "always work" category as well.

Spivak 4y ago
Country domains are probably safe as well given how popular .io is.

PebblesHD 4y ago

I possess a very short domain on a widely used older TLD, and even that causes some interesting validation bugs like ‘email domain cannot be less than 6 characters’ for example… If only there were some widely documented standard for validating an email address instead of a perl regex passed around campfires since 1979.

citrin_ru 4y ago
There is relatively easy way to validate domain part - resolve and check that there is either an A or an MX record (but if you do resolve be prepared to wait - I've seen domains DNS query to which takes many seconds of even minutes because of poor internet links or infrastructure). And the local part just not worth validating. May be reject non-ascii if your system doesn't support SMTPUTF8. Full RFC syntax is very complex for historic reasons and most simple regexps developers tend to use reject addresses people do use. I try to use a email like me+www.service-name.com@example.com when possible but many services reject such perfectly valid address.

throwaway3r6tg 4y ago

Systems I run (e.g. web based account creation) properly validate & accept gTLDs. However, at the same time, my mail servers will flat out 5xx incoming messages for just about all of them. Why? Spammers. Literally >99.9% of emails that use one of those addresses is pure junk. This Is Why We Can't Have Nice Things (tm) Sure, you can ask for an exception and you'll get it, but due to abuse it's a default deny policy around here. IMO, the whole gTLD racket is just a money grab from ICANN anyway, but I digress.

35mm 4y ago

I have a one letter email @ my domain, which some sites think is invalid. Also post brexit, some places in Spain refuse to accept .co.uk emails, which is fun.

camgunz 4y ago

Maybe this is an argument for batteries included in programming languages. If JS included a real email address parser you wouldn't have the current zoo of variously incorrect regexps out there. Or maybe when you're designing a system make sure your identifiers are regular?