E.g.: If your Gmail ID is abc.xyz@gmail.com
, it considers this the same as abcxyz@gmail.com
.
Why is this so?
Web Applications Stack Exchange is a question and answer site for power users of web applications. It only takes a minute to sign up.
Sign up to join this communityE.g.: If your Gmail ID is abc.xyz@gmail.com
, it considers this the same as abcxyz@gmail.com
.
Why is this so?
It's done that way to prevent confusion (and possibly impersonation). I'd rather not have brianwhite@gmail.com
get my mail simply because somebody left a dot out when typing my address of brian.white@gmail.com
. (Note: Neither of those is actually me; I was too late registering to get anything even remotely close to my real name. :-)
Also, you can append anything to your username with "+something
" and it'll still come to you. With this, you can create unique email addresses for certain things and then filter on it or just be able to tell which sites are selling your email address to spammers. (Note: some broken sites don't allow "+" in an email address even though it's supposed to be allowed.)
+ext
is very common among MDAs and was around long before gmail. The ignoring of certain characters to create a "canonical" name is also reasonable when considered in the light of avoiding mis-routed messages and impersonation. As for as I know, there is nothing in the RFCs that disallow this; MDAs are largely allowed to route mail as they see fit, hence the support for aliases, filtering, and forwarding. In that light, ignoring dots is no different that creating aliases.
Sep 2, 2017 at 19:00
@
is considered by SMTP to mean whatever the receiving server wants it to mean; there's no expectation that each possible string represents a different inbox, or even that there is such a thing as an inbox at all.
Gmail doesn't recognize dots as characters within usernames, you can add or remove the dots from a Gmail address without changing the actual destination address; they'll all go to your inbox, and only yours. In short:
homerjsimpson@gmail.com = hom.er.j.sim.ps.on@gmail.com
homerjsimpson@gmail.com = HOMERJSIMPSON@gmail.com
homerjsimpson@gmail.com = Homer.J.Simpson@gmail.comAll these addresses belong to the same person. You can see this if you try to sign in with your username, but adding or removing a dot from it. You'll still go to your account.
...
One last thing: Google Apps does recognize dots. If you'd like to have a dot in your username, please ask your domain administrator to add your preferred username as a nickname.
It is a lesson in human nature that so many experts simply recite Google's pat answer on this as if an assertion were identical to empirical reality. I am one of the early account holders with the firstname.lastname@gmail.com
accounts. About three years ago, I began receiving email directed to firstnamelastname@gmail.com
. By triangulating the information I was able to glean from their dry cleaners, car dealer, etc. I was finally able to contact these people (about 3,000 miles from me, BTW). The DO have the same account as me, minus the period. We were able to determine that only a portion of email "leaks" across accounts. Unfortunately, the fact that I had my account 10 years before they had theirs did not convince them to leave the account to me. Thus, I live with the occasional notice from the bank, school, etc. Because of this, I no longer use Gmail for anything important or confidential.
The most disturbing thing to me is Google's insistence that they could not have made a programming mistake when they clearly did. These folks are arrogant in their faux humility.
Gmail likely supports this use of periods in the email address in order to comply with the IETF's email address formatting standards. If you'd like something less verbose, Wikipedia's page on email addresses simplifies understanding their use (and probably reasoning) well.
a.b@foo.com
must be accepted by intermediate systems, but not that foo.com must assign that name to anyone, or to the same person who owns ab@foo.com
.
Apr 21, 2011 at 15:32