mirror of
https://github.com/anonaddy/anonaddy.git
synced 2026-04-25 06:05:55 +03:00
[GH-ISSUE #245] reply not working when envelope-from / return-path is sent by client #782
Labels
No labels
bug
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/anonaddy#782
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @eleith on GitHub (Dec 29, 2021).
Original GitHub issue: https://github.com/anonaddy/anonaddy/issues/245
in the documentation, anonaddy has postfix pass emails to the application as such
anonaddy's reply logic in ReceiveEmail.php depends on
${sender}however, according to postfix's pipe documentation,
${sender}is derived from the sender envelope from (as opposed to directly using theFromheader).mail clients / services that want to track bounces set the
Return-Pathheader with an alternate email address. This email address is also referred to as the envelope-from address. Thus, when set, the${sender}will refer to this alternate email address and not theFromaddress.as a result, this bounce email address will not match any valid recipients and thus all replies will fail to go through.
this issue can be worked around, if after parsing the raw email, you extract the sender using the following method
and pass that value into the various recipient verification calls used to validate and then eventually send the reply.
@eleith commented on GitHub (Dec 29, 2021):
i would prefer a way to do this in postfix directly, but haven't found a way to do this yet.
@willbrowningme commented on GitHub (Jan 4, 2022):
Thanks, I was aware of this but didn't think it would be an issue as the vast majority reply from an email that has the same envelope-from as the "From:" header.
I'll try to sort a fix for this soon, however since the "From:" header can easily be spoofed the server must have appropriate DMARC, SPF and DKIM checks in place if you are self-hosting. I'll check the self-hosting instructions to make sure this is added when setting up Rspamd.
@willbrowningme commented on GitHub (Feb 4, 2022):
This has been fixed in the latest release v0.9.0.