4 ms·

You can buy one, just use another email. You are welcome! >How can a normal internet user figure this out? If I wasn't a web developer I would have given up.

by naoqj 5y ago

You can buy one, just use another email. You are welcome! >How can a normal internet user figure this out? If I wasn't a web developer I would have given up. A normal internet user will have a gmail or outlook mail address, not a .pizza one.

Tenoke 5y ago
Those are definitely the most common but a normal user might also not know it matters and sign up for a novelty email service so theirs can sound cooler.
unethical_ban 5y ago
It isn't excusable. Email validation should be in the form of sending an email and clicking a link, not some 90s era regex.
- lvturner 5y ago
  This is great in theory. In practice you can get banned from your provider due to a high bounce rate.
  - unethical_ban 5y ago
    Then that's a problem with the provider. I'm not completely ignorant of the inherent issues of email and spam, but solutions shouldn't be user-hostile. If a "is this real" filter is required, they should write a script to check for new TLDs daily.
    - xboxnolifes 5y ago
      A problem with the provider that leads to an issue with the service is also an issue to thee service.
- frostwarrior 5y ago
  Maybe "normal users" are not a good parameter for comparison after all.
arghwhat 5y ago
A normal internet user may also have a custom domain, like 90% of all companies do. A normal internet user may also be in a country where ".com" is not the main TLD. Granted, .pizza is unusual, but there is no valid excuse for not supporting it, and systems that fail to use it likely also fail other completely "normal" email addresses due to other invalid email validation like assuming a TLD has one dot, that an email address has a certain arbitrary max length, or because they failed to enumerate even common TLDs. The only proper way to validate an email is to send an email to it.
- kroltan 5y ago
  Microsoft does not allow me to use my @kroltan.com email as a recovery email, because "you're not supposed to use business emails as a recovery". I can define what is a business email or not myself, Thank You Very Much.
- input_sh 5y ago
  > A normal internet user may also be in a country where ".com" is not the main TLD. In my experience ccTLDs are always supported (I've used some funky ones over the years like .sh and .dj), while newer general ones (like .online) are sometimes rejected. My "solution" is to keep a ccTLD to use as an email alias.
  - throwaddzuzxd 5y ago
    Their regex fails on some valid ccTLDs: - .香港 is a valid ccTLD (for Hong Kong) - .xn--j6w193g is a valid ccTLD (punycode transliteration of the above)
2000UltraDeluxe 5y ago
There's a growing number of users with addresses ending with .email. Unfortunately, the same issue applies to .email domains. Regardless, the issue is in the validation end here. There's public lists with valid TLD's and any email address validation should ensure valid email addresses are let through.
- roblabla 5y ago
  why would you even try to validate the TLD anyways? Just let it through. If the TLD doesn't exist, it will error out when querying the domain name anyways. Using public TLD lists runs the risk of the list going outdated.
  - 2000UltraDeluxe 5y ago
    Well, I get if you want to verify the submitted data is an actual email address, and checking the TLD is a valid way of doing it. It does seem excessive, though -- as you said, it will bug out on sending the email if it isn't valid.
some1else 5y ago
Define normal
igetspam 5y ago
This is the reply I got from AT&T customer service, when they were sending me all their new subscriber info for people who wanted a cell phone but didn't have email. They assumed my email address was fake. The office of the CEO didn't agree, when I started posting all my new account info online. It was as bad an answer then as it is now.
Brian_K_White 5y ago
A normal user will have anything that any cpmpany offers to sell them. A normal user does not know about common unsafe assumptions in every aspect of programming and IT integration. Once the option to get foo.pizza exists, absolutely a ton of normal users take it, just like they do everything else.

by naoqj 5y ago

Tenoke 5y ago

Those are definitely the most common but a normal user might also not know it matters and sign up for a novelty email service so theirs can sound cooler.

unethical_ban 5y ago

It isn't excusable. Email validation should be in the form of sending an email and clicking a link, not some 90s era regex.

lvturner 5y ago
This is great in theory. In practice you can get banned from your provider due to a high bounce rate.
- unethical_ban 5y ago
  Then that's a problem with the provider. I'm not completely ignorant of the inherent issues of email and spam, but solutions shouldn't be user-hostile. If a "is this real" filter is required, they should write a script to check for new TLDs daily.
  - xboxnolifes 5y ago
    A problem with the provider that leads to an issue with the service is also an issue to thee service.
frostwarrior 5y ago
Maybe "normal users" are not a good parameter for comparison after all.

arghwhat 5y ago

A normal internet user may also have a custom domain, like 90% of all companies do. A normal internet user may also be in a country where ".com" is not the main TLD. Granted, .pizza is unusual, but there is no valid excuse for not supporting it, and systems that fail to use it likely also fail other completely "normal" email addresses due to other invalid email validation like assuming a TLD has one dot, that an email address has a certain arbitrary max length, or because they failed to enumerate even common TLDs. The only proper way to validate an email is to send an email to it.

kroltan 5y ago
Microsoft does not allow me to use my @kroltan.com email as a recovery email, because "you're not supposed to use business emails as a recovery". I can define what is a business email or not myself, Thank You Very Much.
input_sh 5y ago
> A normal internet user may also be in a country where ".com" is not the main TLD. In my experience ccTLDs are always supported (I've used some funky ones over the years like .sh and .dj), while newer general ones (like .online) are sometimes rejected. My "solution" is to keep a ccTLD to use as an email alias.
- throwaddzuzxd 5y ago
  Their regex fails on some valid ccTLDs: - .香港 is a valid ccTLD (for Hong Kong) - .xn--j6w193g is a valid ccTLD (punycode transliteration of the above)

2000UltraDeluxe 5y ago

There's a growing number of users with addresses ending with .email. Unfortunately, the same issue applies to .email domains. Regardless, the issue is in the validation end here. There's public lists with valid TLD's and any email address validation should ensure valid email addresses are let through.

roblabla 5y ago
why would you even try to validate the TLD anyways? Just let it through. If the TLD doesn't exist, it will error out when querying the domain name anyways. Using public TLD lists runs the risk of the list going outdated.
- 2000UltraDeluxe 5y ago
  Well, I get if you want to verify the submitted data is an actual email address, and checking the TLD is a valid way of doing it. It does seem excessive, though -- as you said, it will bug out on sending the email if it isn't valid.

some1else 5y ago

Define normal

igetspam 5y ago

This is the reply I got from AT&T customer service, when they were sending me all their new subscriber info for people who wanted a cell phone but didn't have email. They assumed my email address was fake. The office of the CEO didn't agree, when I started posting all my new account info online. It was as bad an answer then as it is now.

Brian_K_White 5y ago

A normal user will have anything that any cpmpany offers to sell them. A normal user does not know about common unsafe assumptions in every aspect of programming and IT integration. Once the option to get foo.pizza exists, absolutely a ton of normal users take it, just like they do everything else.