http://issues.apache.org/SpamAssassin/show_bug.cgi?id=2142





------- Additional Comments From [EMAIL PROTECTED]  2007-02-26 10:10 -------
> FYI, the default sendmail config adds Return-Path...
| I did notice that eventually; it adds it, but it was then
| removed by another MUA I was using.

The Return-Path is a standard way of storing envelope sender
address into a mail header, normally inserted by LDA.

RFC2821:
   When the delivery SMTP server makes the "final delivery" of a
   message, it inserts a return-path line at the beginning of the mail
   data.  This use of return-path is required; mail systems MUST support
   it.  The return-path line preserves the information in the <reverse-
   path> from the MAIL command.  Here, final delivery means the message
   has left the SMTP environment.  Normally, this would mean it had been
   delivered to the destination user or an associated mail drop, but in
   some cases it may be further processed and transmitted by another
   mail system.

There is no point in reinventing the weel.

> Envelope-Sender (qmail, new-inject(1))
> X-Envelope-From (procmailrc notes this, amavisd are adding it,
                   we recommend it)
> Return-Path (postfix, sendmail, rfc821 IIRC)

Just a minor correction, amavisd-new adds a synthesized
Return-Path (and not X-Envelope-From) as the first header
field of a message as submitted to SA.

Don't know how SA heuristics on obtaining envelope sender
address works, but it should grab the topmost of the
header fields potentially supplying envelope sender address,
and I think the SA recommendation should be to stick with
RFC2821 & RFC2822 standardized header field intended just
for this purpose.

Btw, the Mail::SpamAssassin::Conf man page in 'whitelist_from'
does not mention Return-Path. A documentation bug or a true
omission?

(the envelope recipients are another story, a standard there
is a subfield 'for' in a Received header field (RFC 2821,
section 4.4), which is normally only provided by MTA when there
is only one recipient to a message, for sender privacy reasons)

  Mark



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Reply via email to