D.J. wrote:
> On 9/8/06, Bowie Bailey <[EMAIL PROTECTED]> wrote:
> > D.J. wrote:
> > > Greetings all:
> > >
> > > I intend to eventually have local copies for the lists I wish to
> > > use, so it's important for me to figure this out. Currently, I'm
> > > just trying to get SA to only do checks against the lists that I
> > > want to eventually check. However, it still appearst to be
> > > checking all of them. I've basically taken the 20_dnsbl_tests.cf
> > > and 25_uribl.cf files, copied them to my /etc/mail/spamassassin
> > > directory, and commented out the lists that I don't want checked.
> > > However, as I said, it still appears to be checking things. I have
> > > a feeling this is because the original 20_dnsbl_tests.cf and
> > > 25_uribl.cf files are still in the /usr/share/spamassassin
> > > directory, and simply commenting them from a later file won't
> > > change matters. However, the catch is that from what I've read, I
> > > *don't* want to edit the files under /usr/share/spamassassin as
> > > they'll be overwritten upon upgrades, thus losing my
> > > customizations. What is the best course of action to accomplish
> > > this goal?
> >
> > First, delete the copied files. There is no point in having copies of
> > those files in /etc/mail/spamassassin.
> >
> > Then, add score lines to /etc/mail/spamassassin/local.cf to change the
> > score of the rules to 0. This will prevent them from running.
> >
> > For example:
> >
> > score RCVD_IN_SORBS_DUL 0
> > score RCVD_IN_NJABL_PROXY 0
>
> Excellent! This has worked flawlessly. Now for part 2 of this
> project, sort of related to the first part. So now I have only the
> zones I want to query. When I wish to move to my local servers, is
> it as simple as adding a new "header" line into my local.cf file for
> each list, or will I need to disable the old lists entirely via the 0
> score method and completely rewrite the rules for my local server?
> Thanks for all your help!
You could just change the header line, but I would suggest rewriting
the rules to avoid confusion.
1) Leave the current rule with a zero score
2) Copy the header, describe, tflags, and score settings for the rule
from /usr/share/spamassassin to local.cf
3) Change the name and description of the rule to indicate that it is
using your servers.
4) Change the server name so that it uses your server.
5) Give it the same or different scores than the original
Giving the rule a new name will avoid confusion in the future as it
will make it obvious that this is a different rule. The simplest
thing would be to add a short prefix or postfix to the current
rulename ("RCVD_IN_SORBS_DUL_DJ", for example).
--
Bowie
