David Velásquez Restrepo wrote:
> Software:
> --------------------------------------------------------------
> A perl script wich takes some file and test it using Mail::SpamAssassin
> to get it´s spam score level
If your script isn't persistent, I'd ditch it and use spamc/spamd as Justin
Mason suggested.
You'll save a lot of processor time from two things using this approach:
1) spamd parses the rulesets when it loads, instead of on a per-message
basis.
2) You'll avoid invoking a perl process on a per-message basis, which
is a huge
waste of CPU time. The perl processes will be preforked by spamd, and only spamc
(a compiled utility) gets invoked per-message.
3) spamc has a built-in message size limit, so you'll avoid scanning
messages
with large attachments that are unlikely to be spam anyway.
> http://www.rulesemporium.com/rules/bigevil.cf
Matt Y already pointed this out, but just to underline it, bigevil will waste
TRULY massive amounts of resources on your system.
Even the author of bigevil (Chris S.) strongly recommends that nobody use it,
and if you go to the website now, it's been deleted to prevent anyone from using
it anymore.
You should easily cut 30MB or more off the size of your processes if you remove
bigevil.
In general it looks like you downloaded every optional ruleset in the world and
added it to your configuration before you started off. I would strongly
discourage doing that kind of approach to any kind of server application, and
it's especially true for spamassassin.
Start off running SA without *ANY* add on rulesets, then start adding them a few
at a time. This way if you add a bloated ruleset like bigevil, the cause of the
problem is immediately obvious.
Be very wary of any ruleset which has a .cf file that's greater than 64k in
size.
Matt Y's comments on duplicated rulesets (such as antidrug.cf, and having both
the pre and post 2.5x versions of several rulesets) is also valid.
> Q) With spamassassin (and all the above info) you need about 20 to 30 seconds
> per email message and LOTS of RAM and CPU:
> a) TRUE
> b) FALSE
a) TRUE, due to misconfiguration. With some tuning based on the tips above, this
will readily change to b) FALSE.
