Spam Assassin driving me starkers!

[Matt Kettler]

1) I'd recommend editing mailscanner's spam.assassin.user.prefs That's what
I do with recent versions of mailscanner.

2) I'd avoid ever editing anything in /usr/share/spamassassin. It all get's
blown away when you upgrade.

3) I'd recommend running spamassassin --lint to make sure you haven't
corrupted your rulefiles. When SA encounters an error it skips large chunks
of the file, Mailscanner isn't informed of the problem, so it doesn't
report it.

4) I'd recommend running spamassassin from the commandline with
spamassassin -tLD <sample-nonspam.txt to see where it reads local.cf from.
You should see this output near the top:

debug: using "/usr/share/spamassassin" for default rules dir
debug: using "/etc/mail/spamassassin" for site rules dir

you want the "site rules dir" to contain your local.cf. MailScanner might
be over-riding that however. I know it over-rides the user_prefs defaults.

At 12:56 PM 10/23/2002 -0500, Sean Embry wrote:
>I'm trying to find out where the local.cf file should go/be to control
>SA config.
>(RedHat 7.3, MailScanner 4.01-8, perl 5.6.1, SpamAssassin 2.43)
>
>
>I've changed settings in:
>/etc/mail/spamassassin
>/usr/local/Mail-SpamAssassin-2.43/rules
>/usr/share/spamassassin
>
>I'm trying to tweek hitpoints for various rule sets, and I'm not seeing
>things change.
>
>I've also changed required_hits from 5 to 9, but my headers still say
>required_hits is at 5.
>I've also tried to change required_hits in the above local files too.
>No luck.
>
>I'm stopping (twice) and starting MailScanner between tweeks and
>testing.
>
>service MailScanner stop
>service MailScanner stop
>service MailScanner start
>
>Roll out on the project is fast approching (Friday night), and I would
>like to have SA on line too.