Thanks Gary,
My sa_tag_level_deflt is set to 3. I double checked to make sure the mail
size limit was set to 1 meg. On the messages I am having issues with, this
is an expample:
<...>
No sa timeouts in the logs.
Jan 6 12:08:20 mail4 amavis[3142]: (03142-01) Passed,
<[EMAIL PROTECTED]> -> <[EMAIL PROTECTED]>, quarantine 3iC2DLzj+3Ar,
Message-ID: <[EMAIL PROTECTED]>, Hits: 0
Jan 6 12:08:20 mail4 amavis[3142]: (03142-01) Passed CLEAN,
<[EMAIL PROTECTED]> -> <[EMAIL PROTECTED]>, Hits: 0, tag=3, tag2=5,
kill=5, L/0/0/0
Shane
I show this message was scanned, and it returned a score of 0 (Hits: 0). If
it had not been scanned, it would have said Hits: -
To see X-Spam headers for all messages, set:
$sa_tag_level_deflt = undef;
then you will see what rules hit (did not hit) for messages like this.
Seeing the X-Spam headers will be useful to further diagnose the problem.
It would not hurt to run a spamassassin debug on this and another working
server and compare the output to insure all the rules are loaded. You must
run this as your amavisd-new user. Let's say your amavisd-new user name is
'amavis' and the home directory for the amavisd-new user is '/var/amavis'.
You should be able to capture the output with either:
sudo -H -u amavis spamassassin --lint -D &>/var/amavis/debug.log
(or)
su amavis -c 'spamassassin --lint -D' &>/var/amavis/debug.log
The debug.log should be in the amavisd-new user's home directory (so it is
writeable).
Gary V
_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today - it's FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
