Email Alias management in Mail (not in pass)
The email alias is a great idea, but I hate that I have to switch over to proton pass to manage them, because I don't use proton pass I use bitwarden and am happy with it.
Please integrate it into the email where it makes much more sense, and allows us who don't use proton pass to still use it with ease.
If I send to an email, it should replace my main email with the alias. Otherwise it just leaks my email anyways.
Better integration into mail is needed. I need full control of the aliases in mail like you do in pass. Pass is not for everyone, and email features should be in the mail app.
mooleshacat
shared this idea
-
Dylan Snyder commented
+1 to this, but also expanding it. Custom domain setup needs to be unified across Pass and Mail. Right now I have customdomain.com setup in Mail, and private.customdomain.com setup in Pass for aliasing.
I was unable to setup customdomain.com in Pass for aliasing (alias@customdomain.com), I assume because it was already being used with Mail, and I don't want to use 2/3 of my custom domains for a domain and a subdomain. So when I receive an email to alias@private.customdomain.com, I'm not going to be able to respond with the subdomain and will instead have to use my regular dylan@customdomain.com, or one of the other aliases I've set up.
Also, both Mail and Pass have the alias concept, but they're treated differently (Mail has a limit of 15, Pass has unlimited but you can't respond as the alias).
-
uma_protection
commented
Agree, I spend my time between 1password and protonmail.
The worst is when I need to send an email, I have to manually create the alias in protonpass or simplelogin before to send an email.
Aliases needs to have a better integration with protomail with UI improvement and avoid switching apps.