3 ms·
My understanding is + sign is in the RFC, so of course it should be supported. If you want to identify your users by email, you should probably strip the + and
by Santzes 9y ago
My understanding is + sign is in the RFC, so of course it should be supported. If you want to identify your users by email, you should probably strip the + and everything after before checking for uniqueness. On the other hand, dots matter in the RFC and Gmail is breaking it with their "feature".
edit: I was corrected in other comments that the + labeling is optional part of the standard.
- shkkmo 9y ago> I was corrected in other comments that the + labeling is optional part of the standard. Allowing + in emails is not an optional part of the standard. > you should probably strip the + and everything after before checking for uniqueness. No, you shouldn't. Different email providers use different characters to allow "subaddressing" or "tagging" and the presence of those characters doesn't mean that any subaddressing will be done. https://en.wikipedia.org/wiki/Email_address#Subaddressing https://en.wikipedia.org/wiki/Email_address#Subaddressing
- fjsolwmv 9y agoGmail isn't breaking anything. It's none of Netflix's business that Gmail gives its users aliases. This issue has nothing to do with dots, and everything to do with Netflix sending bills to unverified email addresses.
- nebulous1 9y agoAs far as I can tell it isn't in the standard at all, optional or otherwise (although the character '+' is allowable). Gmail are not the only ones to implement this feature though. Also, you'll have to elaborate on how the dot usage actually breaks the RFC. I assume it states that dots are just like any other allowable character, but that's not the same as actually breaking the RFC.