On Wed, 4 Apr 2007, Bill D'Anjou wrote: > For me, the problem seemed to arise when we were under a spam attack. > It appears as though simscan could not keep up under the load (or is > spamassassin the problem?). Are there faster, more robust alternatives > to consider?
Maybe not directly related but, did you tried in that situation raising max-children parameter passed to spamd from the default values? in the servers I have to care for, /service/spamd/run exec line is for example "exec /usr/bin/spamd -m 12 -L -x -u vpopmail -s stderr 2>&1" You'll need more cpu and more memory, you couldn't raise -m without monitoring. regards, __Abel.
