On Wed, 2003-08-27 at 00:41, Charles Philip Chan wrote:
(1) Using spamd/spamc combo instead of spamassassin. That's what I've been using. Sorry, I thought: spamd/spamc = spamassassin.
(2) Use a lock file to make sure only one message is process at a time. Thanks, this helped a great deal.
(3) Limit the size of the mail scanned since spam messages are small. This wouldn't make much of a difference, as most of the mail I get are quite small.
For example:
# The lock file ensures that only 1 spamassassin invocation happens # at 1 time, to keep the load down. # :0fw: spamassassin.lock # # Limit size to 250 KB * < 256000 # # Use spamc | spamc -d 127.0.0.1 -f -u
Just for the sake of interest, if I understand the manpage correct, can I run spamd on another machine in my local network and have spamc on my machine connect to the other one and have it do the hard work? The "other machine" happens to be a PII-233 with two ancient first generation IDE drives, so I doubt if it will save me any time, but I'm curious.
that is a lot of mail. However, the problem immediately went away after I installed my new 80 GB "WD Caviar Special Edition" with 8Mb cache. Much as I would like to have one of those, that's going to have to wait until next year - I've spent too much money on the machine already this year...
Thanks for the help Hans