3 ms·
The problem with using a standard convention for this sort of thing is that it's easy to detect and subvert (in this case, drop the + character and everything f
by justinlardinois 11y ago
The problem with using a standard convention for this sort of thing is that it's easy to detect and subvert (in this case, drop the + character and everything following it from the username).
If I sign up for, say, a Sears mailing list with the address sears@justinlardinois.com, it's not possible to divine what my "real" email address is.
What are the arguments for this being a bad idea?
- vhost- 11y agoThis is exactly what I do. I point everything in google apps to my primary account and then when an email from <service>@mydomain.com gets leaked, I just create an account for it in google apps and send everything to the trash.
- derekp7 11y agoI like to track down where I used the given email from -- you'd be surprised who leaks your email. Was going through my spam folder, found a bunch of virus-laden phishing emails sent to an address I used one time on Equifax's site to get my credit report.
- varjag 11y agoYou can just use one subscription address for all unimportant services, thus using e.g. subscription+sears@justinlardinois.com. > What are the arguments for this being a bad idea? It enables spammers and makes you vulnerable to their backscatter, and there is no good way around it.
- icebraining 11y agoYou can just use one subscription address for all unimportant services, thus using e.g. subscription+sears@justinlardinois.com. Yes, but if they drop the "+sears" part, you lose the tracking information. What do you mean by wildcard emails enabling spammers? Backscatter is not really a problem, I just filter non-whitelisted addresses to another folder which deletes them after a short while. Known problematic address get filtered to /dev/null. This is really easy to do with Sieve.