Wow! Under consideration for 10 years. Proton has a lot of basic features that needs to implement before making any new products. There are basic features and "easy" to implement.

The inability to create an alias in Mail is a real drawback. Please implement ASAP.

I think the main need is to use alias in the "from" area when sending an email
Some possibilities
- when an alias is created, to have a check box asking "do you want to use this alias to send email?" In that case, it would be good to put the "sender names" that will be displayed for the person how will receive the mail. ANd nothing else to do to have the possibility to choose the alias as sender (no reverse ..... no simplelogin, no ......)
- And what about managing yourself (protonmail) the alias and not using an other compagny? In that case alias would be like xxxxx.yyyyyyy@pm.me and not xxxxxx.yyyyy@passinbox.com?
------ some website are rejecting alias emails
------ it should be more easy to manage for you and for us

Requesting since October 2024. Will I become an old man before its done? :'(

Please please please implement this asap.

Apple has it in Apple Mail. I’m sure Proton can do it better! ;)

Such a basic feature. Unbelievable that it hasn't been implemented yet!

We don't want to copy and paste SimpleLogin's reverse alias every time when we write email

This seems a fundamental requirement for privacy, the core value of Proton

Better integration needed for proton hide-me aliases. Unable to send using hide-me alias, not intuitively at any rate...

Still waiting, hoping it arrives soon™
And besides what everyone else has already suggested, add some icon or coloring to identify in the From and To "original addresses" from "alias" and "reverse-alias" ones? Like when I select one of the contacts I know I am not messing up and using the final address instead of the reverse alias. Or what others said and a checkbox or button that automatically reuses/generates alias+reverse-alias in-place. Thank you very much for your efforts.

same here, countless times I leaked my mail cause of that.

to have to remember to login to simplelogin and copy the reverse alias is a flow that I keep forgetting.

I can only send emails to adresses listed in my simplelogin aliases contacts when replying.

So from time to time I write an address directly, boom address leaked , I get it that this is how it is grown, but just add the ability to select an alias from the web/desktop web app when sending to a mail listed in simplelogin alias contacts

and WARN if I attempt to send an email to a simplelogin contact with my real email

The ability to create +aliases and use them in reply-to emails would highly facilitate mail sorting for lots of people.

Still waiting since Oct 2024. :)

i find it hard to believe you can send emails from your aliases, especially since this has been requested for such a long time now. Please implement asap, thanks.

When logging in with an alias, this is set in Proton Mail as the ‘top on the list’ send from mail address, this is not handy.
Also, the default ‘send from email’, when responding to an incoming alias email, is now set by default to the primary Proton email. This can create problems by accidentally exposing the primary email when responding.

Create a separate menu to set the default ’sent from’ email, to be chosen from primary or aliases, no matter if you’re starting an email or responding to any email.

Compose and send email directly from Simplelogin alias

When sending an email, selecting a simplelogin alias should be offered from the "Compose" window for new messages (reply is an already working scenario).

A suggestion for the approach would be having in the "From" combo list a search box in the first element with and integrated search of simplelogin aliases.

Then, depending on the alias selected and the recepient, the recepient should be changed automatically by the reverse alias.
If the contact is not in the alias list, then create the reverse contact.

Also having a "by default" reverse alias for contacts (in addition of the real email) would be wonderful.

I hope that contact sync in android be in the not so far future and in that case it's interesting having the real email for other apps and in proton mail the default reverse alias.

Just signed up for unlimited and this is by far the most frustrating problem I've run into.

For example I want to contact people on Craigslist using an alias. There is no quick way to do this since Craigslist uses a string of numbers@sale for addresses. Do I need to add every single email to Pass before using Mail?

I subscribed to Mail mainly because I wanted an efficient way to organize aliases and online shopping.

Stilllllll eagerly waiting….. ;)

Edit: I just realized this was posted in 2016, nearly 10 years ago!

Hello,

I am happy to see that this issue is being considered, because the current integration really needs to improve. It is way too easy to mess up and not use an alias during everyday email correspondances.

Please consider, for starters, implementing some kind of user controlled setting that allows for automatically adding cc'd recipients to the adress book, while connecting these to the alias that is used for the main recipient. This should both be done for simplelogin and it should be synchronized to proton Pass.

More importantly for the final solution, safety needs to be improved drastically through massive improvements in the user interface for Proton users ability to control alias usage.

- The interface for choosing adresses used for replies in real time in the proton mail app should be implemented with a much higher degree of transparency - right now we have none, and the fact that sender field is displaying a personal mail adress, and that I have to press send and cross my fingers that settings in the pass app are correct, is not an acceptable or safe approach to handling aliases. Clear choices should be available directly in in the mail app while composing emails. This improves safety, not to mention the increased ease of mind for the user, knowing that their email adresses are not being accidentqlly exposed.

This should be implemented with extremely clearly communicated settings available to the user, and with a very direct control of when and how the user sends a mail through a spefic alias or through the users personal email adresses.

The level of control should be adjustable with both presets for default aliases or personal mail adresses used for individual contacts, but also with catch all settings for assigning aliases to group messaging correspondances, and, with the option of high granularity control available for multi recipient messages.

It should always be extremely clearly communicated to the user, when they are about to send an email that exposes a personal email adress to a recipient and how alias usage so far have connected your activity for any usage involving the same alias for multiple recipients. It should raise a clear warning, notifying the user of the acute risk of exposing the personal email adress, informing the user how excactly it is happening, and, to what degree the users information will be leaked to others. Standard settings can then be offered to the user for a specific thread/group correspondence and to specific contacts, as to avoid warnings for these clearly defined cases in the future, with the possibility of easily changing setrings later.

Further, the user should be able to choose warning levels for individual personal adresses and maybe additionally for group level choices. Specifically the option of outright banning specific personal adresses from being used should be available with a toggle on and off option, and definitely a setting should be available for some intermediate level of security, stating that an adress should never used for replies or for composing emails without explicit consent for individual contacts, groups, or for specific correspondences.

Profiles for professional, private and personal settings could also be considered for different sets of settings, in order to manage which possible adresses will be available and suggested for different types correspondences.

Better user interfaces minimizes the risk of errors in trying to maintain privacy. Hardcore privacy-dependent users might be well versed in the protocols, and they might be good at handling a strict behavioral approach to alias management for privacy, remembering to switch between apps, adding recipients to adress books, connecting these to specific aliases before going back and replying to an email, but the rest of us are to a much higher degree protected by ease of use and error-minimizing user interfaces.