Improve Default Address Handling for Forwarded/BCC Emails
Currently, the "Default Address (Custom Domain)" works only when emails are sent directly to it or to linked catch-all addresses. If the domain's MX does not point to Proton (e.g., it points to a forwarding service), Proton uses the actual recipient address (usually @proton.me) instead of my Default (Custom Domain) address when replying.
Note: In this scenario, it does not work even if the Custom Domain address is already set as the Default.
Example: domain.com points its MX to a mailing list, which then forwards emails to my @proton.me and @gmail.com mailboxes. When a sender emails to @domain.com and the message is forwarded to my @proton.me address, I can't automatically reply using my Default Address (@domain.com). I must manually switch the From address from @proton.me to @domain.com.
I suggest adding checks for forwarded and BCC emails (i.e., in scenarios where "Header To ≠ RCPT TO"):
If "Header To ≠ RCPT TO", check whether the Header To address matches the user's Default Address.
If yes, use the Default Address when replying; otherwise, follow the existing Reply logic.
This ensures that replies consistently use the user's Default (Custom Domain) Address even for forwarded and BCC emails.
Anonymous
shared this idea
-
John Erik Setsaas
commented
Note that this is valid for reply, but also responses to the meeting invites.
Just to show very clearly what I want, here is a screencast with my comments.
https://drive.proton.me/urls/GSQWYMDDY4#Vd0BYPQcyBHo -
John Erik Setsaas
commented
Currently, I have for EVERY email I reply to, verify that the sender is set correctly to the email to which it was sent.
This should be a very simple UX feature to implement. Please put priority on this.
Thank you.