Email address validity checks suck
6 points ·
MountainMan1312
·
For example, I just signed up for a second line of internet for my homelab with Spectrum. I provided my email address "me+spectrum@example.com". The sales rep's systems accepted it just fine, but when I try to create an account on their online portal, it's suddenly not a valid email address.
This is arguably worse than requiring passwords to contain symbols and numbers.
I bet there's more weird rules that are hurting other people as well.
RFC 2822 Section 3.2.4 [1] says:
atext = ALPHA / DIGIT / ; Any character except controls,
"!" / "#" / ; SP, and specials.
"$" / "%" / ; Used for atoms
"&" / "'" /
"*" / "+" /
"-" / "/" /
"=" / "?" /
"^" / "_" /
"`" / "{" /
"|" / "}" /
"~"
+ is valid atext.I suspect what's happening is they've got some rule against the word "spectrum" or something. Or perhaps they're a bad company and just HAVE to have base-level addresses to sell to the advertisers?
- [1]: https://www.rfc-editor.org/rfc/rfc2822#section-3.4.1
OhMeadhbh ·1 days ago
To make things more annoying, I once had an email address that had a three-level domain, think me@email.example.com instead of a domain with two components like me@example.com. I found more than one email validator that insisted that this was illegal.
dtnewman ·23 hours ago
Show replies
mitchellpkt ·19 hours ago
I've avoided this by using only the first few and/or last few letters of the service in the email tag (e.g. "HaNe" instead of "hackernews"). It's an easy filing system for me, doesn't trigger concerns about phishing, and makes for shorter handles.
lobito25 ·1 days ago
Show replies
codegeek ·20 hours ago