From: "Loren Wilton" <[EMAIL PROTECTED]>
> I'd look at the load average on the system and see if you are running out
of
> memory. I don't know qmail, so can't suggest how to cure it if it is the
> case. However, that is about the most common reason for slow scanning.
You
> don't seem to say how much memory you have. If it is less than 512M, go
get
> some more, SA is memory hungry.
>
> Loren
>
> ----- Original Message -----
> From: "Technical Department" <[EMAIL PROTECTED]>
>
> > Hi
> >
> > We are running Qmail Scanner 1.25 + Spamassassin 3.04 + Clamd 1.86.1 on
> > our dual 1.4Ghz P3 Linux mail server. We've been experiencing some
> > problems with the server taking a long time to scan messages (In most
> > cases they are taking between 60 and 80 seconds). I have the following
> > rulesets installed:
> > 70_sare_adult.cf 70_sare_unsub.cf init.pre
> > 70_sare_bayes_poison_nxm.cf 72_sare_bml_post25x.cf last-update
> > 70_sare_genlsubj0.cf 72_sare_redirect_post3.0.0.cf local.cf*
> > 70_sare_header0.cf 88_FVGT_subject.cf mr_wiggly.cf
> > 70_sare_html0.cf 90_FVGT.cf netcom.cf
> > 70_sare_obfu1.cf 99_sare_fraud_post25x.cf nov2rules.cf
> > 70_sare_oem.cf 99_sober.cf rolex.cf
> > 70_sare_ratware.cf DomainDigits1.cf surbl.cf
> > 70_sare_spoof.cf evilnumbers.cf weeds.cf
> >
> > At the moment I have disabled Razor, SPF and RBL checks from within the
> > Spamassassin configuration.
> >
> > Spamd is started from Daemontools (/service/spamd/run):
> > #!/bin/sh
> > exec /usr/local/bin/softlimit -m 50000000 /usr/bin/spamd -m 8
If softlimit does what I think it does the memory expansion won't help.
Spamd is taking about 63 megabytes of memory. So he may be starving it.
And he may be driving it into swapping. On the other paw 60 to 80
seconds end to end for one message is about right for 1.6 GHz. It's
maybe a bit low for so few rule sets. There is also a potential for
a bad DNS based rule in is batch.
{^_^}
