The problem with giving a throwaway e-mail address to people you may have a conversation with is that you have the additional hassle of having to use that address as your Sender identity when you subsequently reply to their e-mails.
Say they write you first. They use your throwaway address. If you just reply to that, you are now using your main address; you have to get your e-mail program to switch to the alternative identity, consistent with the e-mail thread.
That's just one more moving part in the scheme requiring configuration. Some mail programs keep sending identities in their own database. You have to create the entry there and then explicitly switch to it when composing an e-mail.
To automate that, the throwaway e-mail address system now has to configure your client database in addition to the mail-server-side stuff. Plus your e-mail program has to be patched to select that sender based on an address appearing in the To: or Cc: list of the item you are replying to.
I've been using Fastmail the past few years and I'm a great fan. Not alone does it allow me to generate up to 600 random email addresses using domains owned by Fastmail, it also supports catch-all email addresses using my own domains. Ever since I switched to Fastmail I've been able to use a unique email address for each online service that I sign up for.
I have a catchall rule on my personal domain, so I can trivially make up a new <recipientname@mydomain.com> for everyone who wants an email address. If I get more than a small amount of mail from some sender, I just set up a forwarding rule which deposits everything received on that address into an IMAP folder called "recipientname". If the address becomes compromised - which has happened rather less often than I expected it might, when I began using this scheme - I just change the rule and route the mail to /dev/null instead.
I use SimpleLogin aliases via my Proton subscription. But I'm terrified of what happens if I lose access to my Proton account, either because I get banned or the company disappears into a black hole. It would be a personal disaster to lose access to hundreds of accounts.
I could buy my own domains and have them forward to Proton but then they aren't disposable, unless I were to buy a domain for literally every account.
I'm in a similar boat with slightly different details, but I did get my own domain(s). To me this feels like another single point of failure. Now I'm not just worried about losing access to my email provider - I need to worry about the company managing my MX records too.
It's incredible how much information some people express through their email address. Patterns like:
"[firstname].[lastname].[year of birth]@gmail.com"
are still surprisingly common and indicate race, gender and age. These persistent addresses can also be cross referenced to various leaked datasets to get everything from phone numbers to dietary habits.
The expendable email addresses in iCloud is a sleeper feature. I use this to limit the use of my personal email on services and help cull my email spam for one off uses. You can set which email address the expendable email is associated with, currently linked to my gmail. While not perfect, an enterprising person created "iCloud Hide My Email" extension for Firefox so I'm not tied to Safari on my phone and can integrate it into my workflow on Fedora.
The problem with giving a throwaway e-mail address to people you may have a conversation with is that you have the additional hassle of having to use that address as your Sender identity when you subsequently reply to their e-mails.
Say they write you first. They use your throwaway address. If you just reply to that, you are now using your main address; you have to get your e-mail program to switch to the alternative identity, consistent with the e-mail thread.
That's just one more moving part in the scheme requiring configuration. Some mail programs keep sending identities in their own database. You have to create the entry there and then explicitly switch to it when composing an e-mail.
To automate that, the throwaway e-mail address system now has to configure your client database in addition to the mail-server-side stuff. Plus your e-mail program has to be patched to select that sender based on an address appearing in the To: or Cc: list of the item you are replying to.
I've been using Fastmail the past few years and I'm a great fan. Not alone does it allow me to generate up to 600 random email addresses using domains owned by Fastmail, it also supports catch-all email addresses using my own domains. Ever since I switched to Fastmail I've been able to use a unique email address for each online service that I sign up for.
Catch-all is definitely the way I prefer it, easier than having to generate an address with a service each time.
Even better is bitwarden can generate random emails @mydomain.com automatically when creating a new login.
Fastmail, several custom domains, catch-alls and '<service>.<month>.<year>.<nonce>@<domain>' has served me very well for the last 6 years.
I have a catchall rule on my personal domain, so I can trivially make up a new <recipientname@mydomain.com> for everyone who wants an email address. If I get more than a small amount of mail from some sender, I just set up a forwarding rule which deposits everything received on that address into an IMAP folder called "recipientname". If the address becomes compromised - which has happened rather less often than I expected it might, when I began using this scheme - I just change the rule and route the mail to /dev/null instead.
I use SimpleLogin aliases via my Proton subscription. But I'm terrified of what happens if I lose access to my Proton account, either because I get banned or the company disappears into a black hole. It would be a personal disaster to lose access to hundreds of accounts.
I could buy my own domains and have them forward to Proton but then they aren't disposable, unless I were to buy a domain for literally every account.
I'm in a similar boat with slightly different details, but I did get my own domain(s). To me this feels like another single point of failure. Now I'm not just worried about losing access to my email provider - I need to worry about the company managing my MX records too.
It's incredible how much information some people express through their email address. Patterns like:
"[firstname].[lastname].[year of birth]@gmail.com"
are still surprisingly common and indicate race, gender and age. These persistent addresses can also be cross referenced to various leaked datasets to get everything from phone numbers to dietary habits.
If you run Postfix yourself, here's something I wrote to scratch that itch: https://github.com/m3047/trualias
Does anyone have a good self-hosted tool for doing this?
iCloud is almost justified by the number of expendable email addresses one can allocate
The expendable email addresses in iCloud is a sleeper feature. I use this to limit the use of my personal email on services and help cull my email spam for one off uses. You can set which email address the expendable email is associated with, currently linked to my gmail. While not perfect, an enterprising person created "iCloud Hide My Email" extension for Firefox so I'm not tied to Safari on my phone and can integrate it into my workflow on Fedora.