JavaOne Registration Bug
March 31st, 2008
A coworker was informed (by a flawed web app) that his JavaOne registration could not be found. And he was unable to login because “his email address is invalid”. Apparently his email must end in something like .com, .edu, or perhaps even .cc to be considered “valid”. (at least according to the JavaOne registration system)
Guess what? .coop is a valid domain name extension. When writing data validators, make sure you don’t reject valid data.
Hahaha!! Coop. That’s a good one. Next you’re going to tell me that .museum is a valid tld too.
http://about.museum/
You jest about this but the notion of a “valid email address” is actually surprisingly tricky. Here’s a regex to validate the proper RFC 822 grammar: http://www.ex-parrot.com/~pdw/Mail-RFC822-Address.html
Everybody reading this (both of you) needs to follow Alex’s link. I like the “Perl copes well” statement.
I’ve run into this too with email addresses that use my .name domain name
If I had been drinking coffee, I would have spit it on that grammar!
Validating email addresses is silly. Not as silly as asking twice for a string I can^H^H^Hwill copy/paste. I can give you a million “valid” email addresses that aren’t valid. (#1 nobody@nowhere.com) Email them with the stoopid address for verification.
Hey that’s good. Some even does not accept .info domains.
When choosing an email address, realise that the whole world will be using and acknowledging 3 character tld’s for the next 50 years, and that is unlikely to change.
If you want to spend the rest of your life complaining to the world that your .info, .mobi, .coop or .museum doesn’t work, just have it put on your epitaph.
Yeah, that’s why I dropped my .name account. Even Network Solutions who was hosting the account didn’t recognize it as a valid email address.