Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.I'm using Drupal 5.7 on a Linux system with PHP 5.2.4 and MySQL 4.1.22-standard. Someone emailed me saying that they never got a confirmation email when they registered, and weren't getting any emails when requesting a password change either. I checked it out and it turns out they registered with an email
*****@AOL
they neglected to put the .com at the end of the email address, yet Drupal still created an account for it. Surely this can't be expected behavior, and I think it should be fixed.
Comments
Comment #1
michelleFeature requests need to go against 7.x. 5.x and 6.x are both feature frozen.
Michelle
Comment #2
j.somers commentedThis belongs to the user module.
I am by far an expert, but I think an email address without a TLD is actually valid according to the RFC. Drupal 7 does not validate the email address itself but uses PHP functions to do this.
Comment #3
vm commentedI'd never noticed this before. After some checking on my end I notice quite a few emails addresses in my DB with .cmo or .nte where the user registering incorrectly typed the email address. or inadvertantly left off the .tld
Which explains why those users wouldn't get a registration email.
:wonders how many drupal.org accounts are floating in the DB with this same situation:
Comment #4
ultimateboy commented#2 is correct, a tld is not needed, but maybe we should implement warnings if a user does not enter an email address in a standard form - such as #3 .cmo, .nte ... a simple warning if it appears the user has made a mistake sounds like a good idea to me.
Comment #5
drewish commentedi would actually say this has been "fixed" by #308138: Make valid_email_address() support IDNs but i think it's a step backwards and disagree with the feature request. in either case it's really a dupe of that issue at this point.