On Friday, November 22, 2002, at 04:53 AM, Ruud H.G. van Tol wrote:
Tim Allen skribis:
Some spam filters can be CPU and memory hogs. I recently installed
Spamassassin on an otherwise adequate mail server (admittedly pretty
ancient hardware) and found that multiple instances of Spamassassin were
virtually bringing the system to it's knees. A simple fix was to add a
lock file, so ensuring that only one Spamassassin ran at any time:
0fw:/tmp/spamassassin.lock
/usr/local/bin/spamassassin
Hope this may be useful to someone else.
This is interesting, but it seems like slowing down SpamAssassin has the
same effect on mail delivery (slowing it down) - this solution just saves
some system resources. SpamAssassin comes with the spamd/spamc programs as
well, which are much less resource-intensive than SpamAssassin for heavy
use; they're doing quite well for us. See
<http://spamassassin.taint.org/sitewide.html> and
<http://spamassassin.taint.org/dist/spamd/README.spamd> for details on
setting up spamd. Among other things, you can specify a maximum number of
child processes when the daemon is started.
It's much cheaper do DNSBL first, and only hand over those messages to
content-filters that were not tagged by DNSBL already.
This is also an effective solution which we're using.
pjm
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail