haiku5432
My feedback
5 results found
-
92 voteshaiku5432
supported this idea
·
-
8 votes
An error occurred while saving the comment haiku5432
supported this idea
·
-
56 voteshaiku5432
supported this idea
·
-
3 voteshaiku5432
supported this idea
·
-
26 voteshaiku5432
supported this idea
·
I use proton mail as unified front-end for a couple of mail domains hosted elsewhere.
One is hosted by Google Workspace. This works great:
DNS: customdomain-1.example -> MX points to google, SPF/DKIM allows both google and proton as sender
Proton's OAuth app is installed into Google Workspace. Messages show up in proton and replies use the expected FROM address.
However, with a local small-business email provider this doesn't work so great:
DNS: customdomain-2.example -> MX points to indie provider, SPF/DKIM permits both indie provider and proton
Proton will do one-time imports, but there's no 'permanent' IMAP harvest. So instead, the email address is configured as a forward on the other end: no mailbox, no storage. Indie provider receives mails, and forwards them to proton (on a third custom domain, fully and only linked to proton). The forwards contain valid ARC Chain headers and all that.
When I click reply on these messages, the FROM is set to that third domain. I'd want to use the original domain instead. I can choose it manually, but I want it to be associated by default.