https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6199
Mark Martinec <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #1 from Mark Martinec <[email protected]> 2009-09-13 15:28:39 PDT --- (In reply to comment #0) > Is there really any legimate case where Return-Path should be used in rules > instead of EnvelopeFrom? Isn't the point to respect possible > envelope_sender_header or just use heuristics? Possibly it should be changed > to just be forced alias to EnvelopeFrom. > > 20_vbounce.cf uses Return-Path, breaking my mass-check corpus badly. Amavis > quarantine mails have empty Return-Path and sender in X-Envelope-From. I'll just comment on your last statement. The message that amavisd passes to SpamAssassin has envelope sender presented as Return-Path, which is the only standard way for storing this information in a header section. So this is just what these rule want, and it shouldn't be a problem in this case. While it is true that a quarantined message stored to a file may have a null Return-Path (to prevent bounces in case somebody forwards it to a mailbox), and the envelope sender is indeed in X-Envelope-From, this applies only to such quarantined messages, and should not affect SpamAssassin processing. Moreover, what goes into Return-Path of a quarantined message is configurable: keeping $mailfrom_to_quarantine at undef, which is its default value, will keep the original envelope sender address in Return-Path of quarantined messages. -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
