http://bugzilla.spamassassin.org/show_bug.cgi?id=3494
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution| |FIXED
------- Additional Comments From [EMAIL PROTECTED] 2004-10-21 03:40 -------
I looked at the MailScanner mailing list archives at
http://www.jiscmail.ac.uk/cgi-bin/webadmin?S1=mailscanner
and then search for no_dns_for_from
The discussion there indicates that MailScanner inserts a header named
X-MailScanner-From instead of X-Envelope-From. It also inserts it at the bottom
of the headers, where SpamAssassin can't trust it.
They need to use envelope_sender_header in their SpamAssassin preferences and to
put their X-MailScanner-From header near the beginning of the mail headers.
Their mailing list discussion indicatea that when they do that the rule hits ok
when the the mail is sent directly through SpamAssassin. They are still
discussing why it still dos not seem to work when the mail goes through
MailScanner.
But it does seem like it is now down to a problem to be fixed in MailScanner,
possible requiring them to set the envelope_sender_header option in SA.
I'm going to close this again as FIXED, since this bug was incorrectly reopened.
If the MailScanner problem does turn out to demonstrate a bug in SA, that should
be filed as a separate bug. It would not be correct to close this one as
WORKSFORME, even though it has been reopened for a WORKSFORME reasson.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
