I started looking into email alias services like SimpleLogin, Addy, etc. and I'm wondering if I really need it. Here's why:

My email provider has domain alias functionality. I can connect multiple domains to it. Let's say I'm ratm@domain1.com.

I can buy domain2.com and create an email address called anon@domain2.com. All emails (to both addresses) will land in the same inbox.

I can also create a catch-all email address so that I can create login unique emails for each service, like: lemmy@domain2.com, mastodon@domain2.com, etc.

So I guess my question is: What do I get from an email alias service that I'm not already getting from my email provider?

Is it maybe that I won't be able to reply from the service emails? Like, would I not be able to reply from lemmy@domain2.com since it's only a catch-all? So I can receive mail to it, but can't send from it?

you are viewing a single comment's thread
view the rest of the comments
[–] 11 points 5 months ago* (2 children)

For me, it's that I can make email addresses that are not able to be identified/associated with each other. Meaning alias1@yourcustomdomain.com and alias2@yourcustomdomain.com are clearly both the same identity. It's a fingerprint. This may not be one of your privacy concerns.

  • source
  • hideshow 2 child comments
  • [–] [S] 3 points 4 months ago (1 child)

    Fair enough. So do you do a custom domain for every single service you use?

  • source
  • parent
  • hideshow 1 child comment
  • [–] 3 points 4 months ago

    My aliasing service provides multiple domains to chose from whenever I create a new address. I try to mix them up but no, there aren't enough to have a different one for every single service. But together with the fact that I'm not the only user they have using those domains, I feel there's enough obscurity.

  • source
  • parent