4.57.4: SA score big, yet delivered

[Jeff A. Earickson]

On Tue, 28 Nov 2006, Erik van der Leun wrote:

> Date: Tue, 28 Nov 2006 14:53:11 +0100
> From: Erik van der Leun <evanderleun at hal9000.nl>
> Reply-To: MailScanner discussion <mailscanner at lists.mailscanner.info>
> To: MailScanner discussion <mailscanner at lists.mailscanner.info>
> Subject: Re: 4.57.4: SA score big, yet delivered
> 
> I've had this problem once (with an older version)
>
> The SpamAssassin Cache was the problem back then...
> When I disabled this, it worked like a charm again...
>
> :)
> Erik
>
>> On Mon, 27 Nov 2006, Jeff A. Earickson wrote:
>>
>>> Date: Mon, 27 Nov 2006 15:54:49 -0500 (EST)
>>> From: Jeff A. Earickson <jaearick at colby.edu>
>>> Reply-To: MailScanner discussion <mailscanner at lists.mailscanner.info>
>>> To: mailscanner mailing list <mailscanner at lists.mailscanner.info>
>>> Subject: 4.57.4: SA score big, yet delivered
>>>
>>> Gang,
>>>
>>> I've had to roll back to 4.56.7 because a bunch of spam got
>>> delivered to people, including me, with no {Spam?} for a
>>> score 5< x < 10, and no delete for High Spam.  I've stared at my
>>> debug output, nothing strange.  The emails in question got properly
>>> tagged with SA scores (in the header and in the syslog output).  Yet
>>> nothing got tagged in the Subject line
>>> or deleted.  Any ideas???
>>
>> In my previous test, the MailScanner.conf file had:
>>
>> Spam Modify Subject = start
>>
>> I changed the "start" to "yes" to see if it makes a difference.  Nope.
>> Spam gets scored properly and then gets delivered, no matter what.
>>

Thanks for the tip on the SA cache.  I stopped MS, blew away the SA
cache.db file, changed the symlink to MS 4.57.4, restarted.  Same
result, spam sails right thru to delivery, no change.  Bummer.  :(

Jeff Earickson
Colby College