SpamAssassin 2.55 problem

[Paul]

I have tried various max children settings - from the default of 5 down
to 1.  I still found MailScanner/SpamAssassin couldn't keep up.

Currently I have 1 MailScanner process and a max of 15 messages per
batch.

As I said before, it seems to me that SpamAssassin 2.55 is the limiting
factor.  As soon as I enable it, everything grinds to a halt.

I'll order more memory this week; taking the box up from its current 32
Mb to its max of 256 Mb.

In the meantime I just wanted to establish that some people have
SpamAssassin 2.55 working well with the latest MailScanner.

----- Original Message -----
From: "Julian Field" <mailscanner at ECS.SOTON.AC.UK>
To: <MAILSCANNER at JISCMAIL.AC.UK>
Sent: 29 June 2003 14:47
Subject: Re: SpamAssassin 2.55 problem


> One of the important things to do on small systems is to reduce the
>          Max Children
> setting in MailScanner.conf. This will greatly reduce the memory
required.
> On a lightly loaded system you probably need only 1 or maybe 2 child
> processes. The default of 5 is for systems which have plenty of RAM.
>