SpamAssassin 2.50 Problems

[Gerry Doris]

On Mon, 24 Feb 2003, Julian Field wrote:

> Okay, I am pretty sure it is fixed. It's a little bug in SpamAssassin where
> it doesn't tidy up after itself properly, and leaves a file opened and
> locked that it should have closed and unlocked.

I installed the patch and it fixed the CPU load problem on my system too.
Julian, you've once again earned your princely salary!

BTW, I did notice something else.  I've been running SA 2.50 for several
days calling it through procmail while the fix was being worked on.  After
I patched 2.50 and started using MailScanner to call it I had SpamAssassin
running twice on every message...once with MailScanner and then again with
procmail.

The SpamAssassin scores are different.  Have you any idea why this might
be?  With all the messing around I've been doing with SpamAssassin I'm not
surprised something is now operating strangely!

--
Gerry

"The lyfe so short, the craft so long to learne"  Chaucer