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.

### Just sharing my current Paint Point & a Proposal on better flow

#### Current Pain Point:
The current UI/functional flow for sending an email to a brand's support email (first-time communication) involves multiple steps and switching between the Proton Email desktop app and Proton Pass. This process is cumbersome and time-consuming.

#### Current Workflow:
1. Open Proton Email desktop app.
2. Navigate to the Security Center.
3. Click "New Alias."
4. Fill out the alias creation form.
5. Click "Create Alias."
6. Open Proton Pass in a browser.
7. Authenticate with PIN/password.
8. Locate the newly created alias.
9. Open the alias details.
10. Add the brand's support email under "Contacts."
11. Save to create a reverse alias.
12. Copy the reverse alias.
13. Return to the Proton Email desktop app.
14. Click "New Message."
15. Paste the reverse alias in the "To" field.
16. Compose and send the email.

#### Proposed Workflow:
1. In the Proton Email desktop app, click "New Message."
2. Near the "From" address, a checkbox labeled "Send from an alias?" is available. The user clicks it.
3. Upon clicking, two options are presented:
- **Option A:** Send from an existing alias. => On Selection, A search bar allows the user to find and select an existing alias
- **Option B:** Create a new alias. => The current alias creation form allows user to create new alias
4. The user types the recipient's email address in the "To" field.
- System logic: For existign alias , If reverse alias there use it; Else for both existing & new alias => A reverse alias is automatically generated and used as the "To" address.
5. Compose and send the email.

#### Benefits:
- Streamlined workflow with fewer steps.
- No need to switch between the Proton Email app and Proton Pass.
- Automatic reverse alias creation reduces manual effort.
- Enhanced user experience with integrated alias management.

Ideally a reply would trigger a response from the alias it was sent to and not to create a contact alias first to then forward it to that within Proton Mail :)

Please add this feature, the benefit of having an alias is completely lost if I have to reply to emails using my main account.

Vitally important for proper use of the hide-my-email aliases. It is impossible to tell at a glance which email account will be seen by the receiving party. Even after it has been sent the email still shows the main account behind the hide-my-email alias. The level of confusion this creates is frankly counterproductive to the entire concept of privacy which is the entire reason to be using this method of obfuscation. PLEASE make this a priority!!!

This would be so cool!

still eagerly waiting, for a year now actually

still eagerly waiting...

this is a must have and also NEEDS to support different signatures and all the fancy encryption as well! i use multiple aliases/names online, and want to set signatures as well for each name/alias. SimpleLogin's features being integrated more closely into ProtonMail would be awesome, that or redesign the backend of Proton managed domains to be moved to SimpleLogin entirely, and have the cap on domain emails removed, and allow all the usual things like encryption key signing, signatures, etc. right now the feature disparity is pretty vast and a little confusing and definitely convoluted. please integrate email aliases more closely both from SL subdomain registrations and SL domains themselves, as well as personal domains we register

also please add a toggle for each SL subdomain and/or personal domain whether or not it appears in the "from" section, so you can set one or two domains as your send from aliases, and have the rest of them as just for reverse alias use, for example, i'd have my personal domains be included in the from section, and i'd have my subdomains be excluded as i set those up with a catch all so i can just have mail sent and call it a day, no need to really reply to any of those

In addition to this, it blows my mind that I use a simplelogin address attached to my email address for a calendar invite or something similar, but I cannot add it to my Proton calendar because I cannot use any of my SL generated addresses to create a calendar. For example, I used a calendly link to request a meeting with someone, and used a new SL generated address, well, now I cannot addd it to my Proton Calendar becausse "Your email address is not in the original participants list.". This is a huge problem.

We understand that this is under evaluation. What we need (speaking for myself) is better integration between the email service and the feature.

Sending a new email to a contact, instead of a reply, is really a "pain," and I think it can even be confusing for some users.

We know that this requires a lot of assessments, but this feature is very important for saving us time.

One point you cannot overlook is when the user has many aliases. There needs to be a way to organize everything in Proton Mail; otherwise, it becomes a mess.

Why has nothing been done on this yet? For my clients, it's WAY too confusing to explain why they send something to @remax.net and when I reply, it comes from @protonmail.com. Very uinprofessional!

still eagerly awaiting.

It's been almost a full year since you replied. 1 year "considering" is quite a long time, don't you think?

Hello, I just wish to say that I eagerly await implementation of this feature.

This has been in review for 7 or 8 months. I am still eagerly waiting for this to make the aliases practical to use.