Unfortunately, using the apple implementation is just one more stone into their walled garden. It's way harder to wildcard block, as there are legit users of the icloud domain, than a wildcard block for:. But it's never been a real issue.įor me, the best implementation of private alias is the Apple one: %randomwords%. The only downside is that people get really confused when they have to deal with your email, for example when calling support. I actually thought about starting a service that provides this, but it's a niche product with non-trivial technical hurdles and potentially lots of support demands, so I'm happy that Mozilla is offering this. I always wanted a shared domain with lots of users to further reduce exposure. And receiving basically always works, even with the most broken email server setup.Ī downside is the unique domain name. But in this case you only need to receive, never send. * Easy self-hosting: email hosting can be a pain. (of course they still use names, address, credit card info, etc but it helps) * Privacy: all those ad data aggregators have a harder time connecting me between accounts. (somewhat redundant with a password manager and unique passwords, but still) ![]() They also can't try to log in to other accounts or do password resets if they get a hold of the password. * Mitigate data leaks: if some database gets compromised, all they get is a throwaway email. ![]() No need to worry about secondary emails just for a few accounts. * Multiple accounts: If you need a second account with some service, you simply use a new alias. * Spam: if I get any spam, I know exactly which company is responsible, whether directly, through selling user data or because of breaches. I have a custom domain just for signups, and I sign up with The domain simply has a catchall email with a password manager (Bitwarden) this is absolutely brilliant.
0 Comments
Leave a Reply. |