3 ms·

I have a dedicated, very generic sounding domain name just for signups. I use a custom email for each service. Like xyz.amazon@my-generic-domain.com for Amazon

I have a dedicated, very generic sounding domain name just for signups. I use a custom email for each service. Like xyz.amazon@my-generic-domain.com for Amazon, xyz.ycombinator@... and so on. All email is forwarded to a single catch-all account from a good provider, so it is just as convenient to use. But it is trivial to isolate what emails came from which service, who has leaked my email to spammers, to just block a individual recipient, ... . It also makes it easy to have multiple accounts without the annoyance of a fallback email. I wish I had switched to this method much earlier. Ideally that domain would be used by at least a few hundred people to prevent associating via domain name though, with different prefixes (see xyz above) for each user.

prepend 6y ago
I do this too and it’s great except for services that use the reply-to/from as a requirement for service emails.
kyuudou 6y ago
For over a decade I've used hushmail's aliasing feature which allows you to create such custom emails (e.g. dontspamme-hackernews@nym.hush.com) on the fly almost instantaneously. I use one per service that requires an email to sign up. Works great. You can do it with the free account, too. Just delete one if you are obviously getting spam because of a service selling their email lists. Which is a reality for "free" services. Bonus points because you can identify exactly who it is that is doing this and have the option of publicly shaming them.