Yes you are reading correctly.
Really what I want to do is improve the list and keep as much spam fighting
stuff in there, but try to tweak it where I don't kill the servers.

1 of the servers has a xeon 3GHZ processor and the other is a dual pIII
1GHZ.
If you have any experience with some of the files I am using not really
being effective and just burning cpu cycles, then I guess that is where
everyone's experience can help me.

I do understand what your saying with the fact that the cf file resides in
the directory as well as appreciate the script idea.

Thanks,

Joey
  

-----Original Message-----
From: Kelson [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, February 15, 2006 1:28 PM
To: SpamAssassin
Subject: Re: Help with config... I went a LITTLE overboard

Joey wrote:
> Below is my config, how can I pick what to use -vs- not when we are 
> getting slammed and need all the blocking we can, but of course don't 
> want the server to die in the next 24 hours.  I cleaned up the file 
> some as you can see from my FIRST CONFIG FILE to SECOND.

If I'm reading this right, these are config files for Rules du Jour. 
These only specify which rulesets that script will automatically update, not
which rulesets SpamAssassin will use.  SA will use any .cf files it finds in
/etc/mail/spamassassin, but it will not look in subdirectories.

To disable rulesets temporarily, you'll need to move the .cf files out of
/etc/mail/spamassassin and restart spamd.  If you've picked a set that you
always want to disable under these circumstances, you can create a directory
and write a short script like this:

#!/bin/sh
SA_DIR="/etc/mail/spamassassin"
DISABLED_DIR="/etc/mail/spamassassin/disabled"
SA_RESTART="killall -HUP spamd"
DISABLE_FILES="example1.cf example2.cf example3.cf"

cd $SA_DIR
mv $DISABLE_FILES $DISABLED_DIR
$SA_RESTART


Then when you want to reactivate them, you can just move all the files out
of the disabled directory back to /etc/mail/spamassassin and restart spamd
again.

--
Kelson Vibber
SpeedGate Communications <www.speed.net>


Reply via email to