Resolved, finally. My thanks to Mark Martinec for his patience and help. This turned out to be a Postfix master.cf issue, not an amavis issue. I set up the two MX hosts with recipient_bcc maps to copy to a little test host that did vanilla local delivery to /var/spool/mail/. Those messages exhibited the same X-Spam-* header discrepancy, so the mailbox host was not the issue.

A diff of the two MX hosts' master.cf files included the following.

-127.0.0.1:10025        inet n  -       n       -       -       smtpd
 -o content_filter=
 -o receive_override_options=no_unknown_recipient_checks
+127.0.0.1:10025 inet n  -       n       -       -       smtpd
 -o content_filter=
+-o receive_override_options=no_unknown_recipient_checks,no_header_body_checks

One of them had been set with no_header_body_checks. The other had been set without that exception, and it was doing "checks" against all the X-Spam "headers" and removing them. This "10025" port is the return trip from Amavis, so the messages' tags were getting stripped as the message returned to Postfix for external delivery. I was not aware Postfix would strip headers in this particular way (or that it would strip X-Spam and not X-Virus), but it was doing just that. I restored ",no_header_body_checks" to MX1, and it resumed delivering messages with X-Spam headers.

>>>>>>>>>>>>>>>>>>>>
Received: from me.comcast.net (blah[1.2.3.4])
        by mx1.franklinamerican.com (Postfix) with SMTP id 4E27AE7293
        for <[EMAIL PROTECTED]>; Thu, 22 Dec 2005 17:01:58 -0600 (CST)
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
subject: 17:02 test
Message-Id: <[EMAIL PROTECTED]>
Date: Thu, 22 Dec 2005 17:01:58 -0600 (CST)
X-Virus-Scanned: by amavis at mx1.franklinamerican.com
X-Spam-Status: No, hits=2.8 tagged_above=0.0 required=3.5 tests=AWL, BAYES_60,
        MSGID_FROM_MTA_ID, NO_REAL_NAME, RCVD_IN_NJABL_DUL, RCVD_IN_SORBS_DUL
X-Spam-Level: **
X-Virus-Scanned: by amavis at imap.franklinamerican.com

after restart, from telnet:25
>>>>>>>>>>>>>>>>>>>>

Now my home Linux box is scoring 2.8, which is a separate issue, but my filter's working again.

--
John Beamon
Systems Administrator
Franklin American Mortgage Co.
em: [EMAIL PROTECTED]

Mark Martinec wrote:
John,


Mail comes into the network through one of the two MX hosts, is filtered
for spam and viruses, and is delivered to the mailbox server.  The
mailbox server runs amavis, but only as a virus scanner.


Ok, so the mailbox server is not stripping X-Spam-* header fileds,
as it has spam checking disabled. Fine (this was my concern).


There are "X-Virus-Scanned: by amavis at" headers for both the filter and the
mailbox server on delivered messages.  The filtering servers began to
differ in their behavior at some time in the last few weeks that
completely slipped under my radar.  Mail from  filtering server #2 still
has "X-Spam-Level: 1.2" style headers added for scores between my
tag_level and my kill_level.  Mail from filtering server #1 now
completely lacks X-Spam-* headers.  I've run sdiff against their config
files.  I've turned on debug logging to a separate log file.  I can't
find the problem.  I'm open to this being an issue with amavisd-new,
spamassassin, or possibly postfix.  I just can't find it.


Please make available log_level 5 log from server #1 of one spam message
(grep log by id).

Generally the most common reason for missing X-Spam-* header fields
is that recipient address does not match local_domains.

  Mark





-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
AMaViS-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/amavis-user
AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/howto/

Reply via email to