Do you run amavisd-new (which is shipped with SLES9, I think)
If you do, there's the culprit: amavisd-new does its own spam testing
using the spamassassin code directly (not via spamc/spamd)
Details can be found at http://www.ijs.si/software/amavisd/#faq-spam
Likey you didn't configure amavisd-new correctly, so there you are.
Dirk
Jaime Aguado schrieb:
Hi all, I have spamassassin 2.64 running on a SuSE Enterprise 9 running
postfix as smtpd.
My spamassassin system is leaking most spam messages (60-80%) without
tagging them.
I have done some configuration tests:
# spamassassin --lint gives no output error.
# spamassassin < /tmp/spam-message
[...]
Subject: *****SPAM***** Special Alert to Investors
Date: Sat, 28 Jan 2006 00:22:23 +0000
Message-Id: <[EMAIL PROTECTED]>
X-Spam-Flag: YES
X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on
trueno.fresh-it.com
X-Spam-Level: *********
X-Spam-Status: Yes, hits=9.7 required=4.0
tests=BAYES_99,DATE_IN_FUTURE_12_24,
MIME_BASE64_TEXT autolearn=no version=2.64
X-Spam-Report:
* 5.4 BAYES_99 BODY: Bayesian spam probability is 99 to 100%
* [score: 1.0000]
* 1.0 MIME_BASE64_TEXT RAW: Message text disguised using base64
encoding
* 3.3 DATE_IN_FUTURE_12_24 Date: is 12 to 24 hours after Received:
date
[...]
# spamc -R < /tmp/spam-message
[...]
Content analysis details: (8.6 points, 4.0 required)
pts rule name description
---- ----------------------
--------------------------------------------------
5.4 BAYES_99 BODY: Bayesian spam probability is 99 to 100%
[score: 1.0000]
1.0 MIME_BASE64_TEXT RAW: Message text disguised using base64
encoding
2.2 DATE_IN_FUTURE_12_24 Date: is 12 to 24 hours after Received: date
The args passed to spamd are: SPAMD_ARGS="-d -c -a -L"
Finally, the message reaches the inbox mail client untagged as spam. What I
am doing wrong?
Thank you.
