3 ms·

Fastmail supports "masked email", a feature for generating random email addresses. This has 1Password integration and can be set-up on your own domain: https:/

Fastmail supports "masked email", a feature for generating random email addresses. This has 1Password integration and can be set-up on your own domain: https://www.fastmail.help/hc/en-us/articles/4406536368911-Masked-Email https://www.fastmail.help/hc/en-us/articles/4406536368911-Ma... Even before this, Fastmail supported subdomain aliasing. Which you could have on any email host that has customizable forwarding. Including Google Suite (although with GS sending emails from such "aliases" will fail DKIM, not ideal): https://www.fastmail.help/hc/en-us/articles/360060591053-Plus-addressing-and-subdomain-addressing https://www.fastmail.help/hc/en-us/articles/360060591053-Plu... The effect is that you're not going to reuse the same email address. Granted, this may not help with anonymity when the address is reviewed by a human. But anonymity is getting harder anyway, e.g., Gmail requires activation via a phone call, so you have to trust Google to not share your profile. Once upon a time, Twitter was not releasing back unused usernames. But now they've announced that they are. Also, Yahoo. Gmail is well behaved, but it's incredibly frustrating to create a new Gmail username. Sooner or later Google will at least think about reusing usernames, and you won't have any control over it. On domains, I register my personal domain names for 10 years in advance. If I'd die now, my family would have about 9 years to take control, if it helps them in any way; and if not, then why would I care?

jsjohnst 3y ago
> Including Google Suite (although with GS sending emails from such "aliases" will fail DKIM, not ideal) Not if you properly configure DKIM records for it… https://support.google.com/a/answer/177063 https://support.google.com/a/answer/177063
- bad_user 3y ago
  I'm referring to a limitation I bumped into… Let's say that I'm setting up a subdomain, like masked.mydomain.com, and then set a wildcard forwarding rule such that I get all email for *@masked.mydomain.com. Let's say that I subscribe to some service with a username like: blue.velvet9573@masked.mydomain.com Receiving email on that subdomain is perfectly OK, the problem happens when you want to reply / send with such email addresses in “From”. For it to work, “blue.velvet9573” should be an alias defined in the Google Workplace admin. Otherwise, even though Gmail is perfectly happy to accept any aliases, the issue is that emails won't get DKIM-signed unless that alias is an alias defined in Google Workplace. And you can only have 30 aliases per user.

jsjohnst 3y ago

> Including Google Suite (although with GS sending emails from such "aliases" will fail DKIM, not ideal) Not if you properly configure DKIM records for it… https://support.google.com/a/answer/177063 https://support.google.com/a/answer/177063

bad_user 3y ago
I'm referring to a limitation I bumped into… Let's say that I'm setting up a subdomain, like masked.mydomain.com, and then set a wildcard forwarding rule such that I get all email for *@masked.mydomain.com. Let's say that I subscribe to some service with a username like: blue.velvet9573@masked.mydomain.com Receiving email on that subdomain is perfectly OK, the problem happens when you want to reply / send with such email addresses in “From”. For it to work, “blue.velvet9573” should be an alias defined in the Google Workplace admin. Otherwise, even though Gmail is perfectly happy to accept any aliases, the issue is that emails won't get DKIM-signed unless that alias is an alias defined in Google Workplace. And you can only have 30 aliases per user.