Mark Martinec wrote:
John,
I'm not sure I understand your setup - are these mailers processing mail
one after another? There is only one 'Received' header field in your sample.
amavisd-new removes all previous X-Spam-* headers from a message
if it is doing spam checking by itself. This is to protect recipients from
acting on such header fields inserted by untrustworthy foreign mailers.
If you have two amavisd-s in a chain, the second one will remove
X-Spam-* headers fields inserted by previous ones.
Gary,
The $sa_tag_level_deflt only affects the X-Spam type headers. You can
safely include these headers in every mail, spam or not by setting:
$sa_tag_level_deflt = undef;
which for this particular setting means 'lower than any possible score'.
This is only true for amavisd-new-2.0 or later;
from 2.0 release notes:
- if tag level turns out to be undef, it will not be shown in X-Spam-*
header fields, and will be interpreted as having a value lower than any
spam score when deciding whether to insert X-Spam-* header fields or not;
with 20030616 or older undefined tag_level is treated as 0.
Mark
The sample was not a full message; it's an excerpt that shows only one
header and was marked as "(snipped)" in the paragraph above. I
mentioned the following about the setup in my initial post.
"I have two mail filtering servers ahead of my mailbox server, running
postfix-2.1.5-9, amavisd-new-20030616p10-5 and apamassassin-3.0.3 on
stock Debian Sarge."
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. 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.
--
John Beamon
Systems Administrator
Franklin American Mortgage Co.
em: [EMAIL PROTECTED]
-------------------------------------------------------
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/
