4 ms·
1. I agree, of course. Surely, everyone knows this right? 2. True, but you have to do something. :) What exactly is wrong with m@apple.comm? That could be vali
by dinkumthinkum 14y ago
1. I agree, of course. Surely, everyone knows this right?
2. True, but you have to do something. :) What exactly is wrong with m@apple.comm? That could be valid domain at some point, right? You could filter those out but it's almost a preference sort of question. Does anyone think it would make sense to have "warning" level of validation for email addresses and let the user decide on these sort of examples? Just throwing it out there.
- jiggy2011 14y agoTo fix that, you can do a DNS lookup and check the domain has a valid MX record.
- robomartin 14y agoJust be careful when you do this. If you don't use an absolute FQDN you can trigger severe delay in getting a response from the resolver. It can take twenty or thirty seconds (or more) to get a response.
- guillaumepotier 14y agoAt some point if you want to be absolutely sure, you'll have to send a validation link / email and not doing it frontend in JavaScript ;)
- iambibhas 14y agoHTTP calls for client side validation? That's a great idea!
- optymizer 14y ago"This username has already been taken."