-
-
Notifications
You must be signed in to change notification settings - Fork 404
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Need an option to use mailbox.email as "To" header instead of the alias, when forwarding an email to the mailbox. #1928
Comments
Please, can you clarify you use case ? Let me rephrase:
So you want to hit reply and have SL use your real – hidden – email address instead ?
It appears you definitely want to disclose you real, hidden, email address when replying ? Nothing, however, prevents you from replying and replacing the reverse-alias address with the real one from the recipient, thereby bypassing SL entirely and sending your mail from Fastmail instead. Please, feel free to clarify If I did not understand clearly what is your use case. |
Yeah... esample was a typo. sorry for that. I ditched SL and let my aliases be handled by fastmail. Anyways.. as far as my knowledge goes, it wouldn't contradict to SL. In fact it's how SL works. [email protected] sends an email to [email protected] SL handles that incoming email and redirects it to [email protected] (mailbox). The email headers are now, To: [email protected] and From: [email protected] When Bob hits reply, Fastmail sets the From header to [email protected] (previous To header) and attempts to reply to Alice to her reverse-alias. But SL will refuse to handle that mail, since it doesn't allow the From header to be one of the aliases, instead it MUST be the mailbox address. Therefore Bob has to change the From email manually to [email protected], to be able to send the email. SL and ProtonMail handle this automatically, by using X-SimpleLogin-Envelope-To and X-SimpleLogin-Envelope-From headers respectively. But SL and other mail services don't work together very well. I hope this makes it more clear. |
I'm evaluating fastmail (FM), and have encountered the following issue with my setup. My DNS has three MX entries, example.com (handled by FM) and foo.example.com, bar.example.com (handled by SL)
Fastmail
Domain: example.com
Addresses: [email protected], [email protected]
SimpleLogin
Mailboxes: [email protected]), [email protected]
Domains: foo.example.com (mailbox: [email protected], bar.example.com (mailbox: [email protected])
Here's my usecase:
When a mail is sent to [email protected], I want fastmail to use [email protected] as the reply-from address.
However, in fastmail, I only have two options, either using one of the default addresses, or the address the mail is sent to.
In my case I want to use the address the mail is sent to, but in this case, when I hit reply in fastmail, it wants to send the mail as [email protected] instead of [email protected].
I managed to temporarily fix it, by adding the following to
email_handler.py
Is there any caveat to that approach? If not, could we have an option in the UI (per mailbox) to cover this case?
The text was updated successfully, but these errors were encountered: