Repository navigation
1.0.100: a re-sent message keeps its original envelope sender
A re-sent message keeps its original envelope sender
Release (resend) handed the stored copy to Exim with no sender, so the copy was injected as the daemon's own user: Exim logged <= root@⟨host⟩ U=root P=local, the Messages log showed the re-sent copy as From root@⟨host⟩ from 127.0.0.1, and the receiving server saw the host's root address as the envelope sender, so the real sender's SPF and DMARC were never evaluated.
- Original sender kept: the resend, the bulk Release selected and the user-portal release now pass Exim
-f ⟨original sender⟩, taken from the message log's sender (MailScanner records the envelope sender there) or, when the row is gone, from the stored copy'sReturn-Path:. The receiving server now sees the message as coming from the sender, not from this host. - Bounces stay bounces: a message that arrived with an empty sender is re-sent as
-f <>. - Nothing unsafe reaches the command line: a logged sender that fails the address check is skipped; with nothing usable the message is injected as before.
- Release (forward) and Report to SpamCop are unchanged: the forwarded copy is From the release address and still goes out as the daemon's user.
Wiki: Messages (Release section). Upgrade: msfe-ng upgrade, or the Service tab.