FastMail had some of the cleverest ideas for plus addressing. username+tag@fastmail.fm could be given away as tag@username.fastmail.fm
It's been nearly 20 years since I added that feature. I assumed at the time everyone would do it when they saw how handy it is. For some reason that didn't happen...
I use tagname@myusername.mydomain these days, and that's still my favorite feature!
If the website is breached, the login isn’t a login for any other website, and advertisers have a harder time correlating your identity, and if you get spam you know who is the culprit, and you can stop the spam by deleting the alias.
With this, no need for any other antispam logic. Back to the mid 90s (which is a good thing as far as email traffic is concerned!).
Wish every provider would support this as I’m sure spammers have caught on to the plus addressing scheme.
Pharma spam, 419 scams, password leak crypto blackmail... remember that these miscreants rely on low costs to achieve their profits, so any sort of filtering is too expensive. They don't even filter out abuse@, postmaster@, hostmaster@, or mailer-daemon@.
You can use a shared domain:`hackernews@snorremd.kopi.cloud` Or, after setting up an MX and a TXT DNS record, you can use your own domain: `hackernews@mail.snorremd.com`.
You can change the "real address" of any "forwarder" (`snorremd.kopi.cloud`/`mail.snorremd.com`) to relay to any address you want, whenever you want.
You can block individual addresses like `hackernews@mail.snorremd.com` with two clicks starting from your mail client.
You can also configure individual addresses to redirect to RSS so you can read newsletters or other "chatty" services as part of your normal browsing habits.
It's a little longer to read over the phone, but I've never had trouble with it. And I've been able to tell a couple of companies that their email databases had been hacked or stolen.
Disclaimer: just a satisfied customer.
s/(\w+)@(\w+)\.(fastmail\.fm)/\2@\3/g
So for me, I have a few emails in my custom domain:
{firstname}@example.com
market@example.com
(there's others, but it's not relavent to this discussion).
market@example.com just goes straight to spam, as I don't use that email for anything. foo@market.example.com is used for each email instance. It works out extremely well.