4 ms·
Isn't it up to the email provider whether `+` and `.` are ignored in email addresses, won't removing them to "normalize" end up sometimes mapping different emai
by jrochkind1 4y ago
Isn't it up to the email provider whether `+` and `.` are ignored in email addresses, won't removing them to "normalize" end up sometimes mapping different email addresses to the same identifier?
I guess maybe that edge case is not nearly as bad for the advertisers as failing to link the same person, so it's tolerable?
- oops 4y agoAfaik the period thing is a Gmail thing while the plus thing is in the RFC. However it appears the IAB UID2 README says to only normalize pluses/periods for gmail.com addresses: https://github.com/IABTechLab/uid2docs/blob/main/api/README.md#email-address-normalization https://github.com/IABTechLab/uid2docs/blob/main/api/README....
- brewmarche 4y agoThere is an RFC but it just mentions + as an example of a possible sub-address separator when discussing sub-addresses in Sieve filters. Whether or not + acts as a sub-address separator is server-dependent.
- jrochkind1 4y agoOh good find, of course they can make a special rule for gmail, which is such a large portion of email addresses it's worth it.
- mananaysiempre 4y agoIt’s even up to the email provider to make the local part completely or partially case-sensitive if they wish, but tell that to most government websites in the world. Probably a lost case at this point. Periods are more of a Gmail-specific thing, but as you mention merging two people once in a blue moon is not a terrible price to pay for an analytics system, it’s not like it’s going to send mail to these addresses.
- tlavoie 4y agoOn my own host, a '_' was easily configured. Maybe these companies will normalize everything, but it works for me.