3 ms·
It's an important consideration; email sovereignty is at odds with a domain hosting relay aliases where you can blend in with everyone else. Perhaps the solutio
by toomuchtodo 2y ago
It's an important consideration; email sovereignty is at odds with a domain hosting relay aliases where you can blend in with everyone else. Perhaps the solution is a mechanism where you can migrate aliases between services, creating new aliases and updating at each service, and invalidating old aliases, all programatically. Somewhat similar to token and secret rotation. It's just a string identifier that can be an email target.
- tamimio 2y agoOr maybe having an option to generate aliases using my own domain. I don’t mind exposing my domain or even creating a new domain only for this purpose, say @aliasdomain.com. That way, I am still in full control and utilizing the generated aliases.
- dinglestepup 2y agoMost people use a catch-all email with custom domains — and Bitwarden does have an option for that.
- tamimio 2y ago> Bitwarden does have an option for that. That’s good to know, thanks!