and did you always do this or did you start at one point having to go back through a lot of old accounts to change emails and passwords?
and did you always do this or did you start at one point having to go back through a lot of old accounts to change emails and passwords?
I'll also use it for sites that I know are going to send me spam, and then immediately create a filter than deletes emails sent to joe+annoyingsite@gmail.com (note: that's not my real email)
I use email.site@domain.com for this purpose and it makes it handy to see who has somehow lost/disclosed my email to third parties and not informed me (FreshDirect for example)
Or, more importantly, it lets you authenticate the sender in some way. Citibank has to send you email to you.citibankiscool1253stuffonlyIknow@example.net and it is unlikely for a spammer to guess that exact wording (without also trying hundreds of others, which would give it away by filling your inbox).
Otherwise, as a 'true' spammer, why wouldn't you just always strip off everything after the plus when adding the email to your distribution list?
I started doing this four years ago but before that I had an email address that I reserved only for signing up for most websites (to prevent spam leaking into my personal email address).
In main.cf:
virtual_alias_maps = hash:/etc/postfix/db/virtual_aliases
This file is in the same standard aliases(5) file format: zzz-foo@example.com my@real-account.com
I started doing this when I moved all of my mail off of Google. It has the advantage (over you+foo@gmail.com) that it doesn't reveal my real mailbox. It does very quickly reveal who shares/sells my e-mail address, though. When that happens, it's simply a matter of deleting the alias from the file.For example:
amazon-flanbiscuit@sneakemail.com
That gets forwarded to your actual email address, and you can see how it was tagged. If needed, you can whitelist/blacklist specific senders from specific tags as well.
That functionality is not an RFC requirement, however.