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.
It's much cheaper do DNSBL first, and only hand over those messages to
content-filters that were not tagged by DNSBL already.
The only content-filters I use are characterset-tests and virus-signatures,
both only called after a specific header-test (so that they are almost
never called).
--
Affijn, Ruud
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail