Spamassassin & MS

[Matt Kettler]

At 07:22 PM 10/15/2003, Kevin Miller wrote:
>Anyway, the errors stopped after MailScanner was restarted.  I'm curious of
>anybody else has seen this.  I don't know if it was the sa-learn routine or
>the install that initiated the attempt to spamd.

Neither the 2.60 tarball install, nor sa-learn, will install spamd. Heck,
sa-learn doesn't know what spamd is, much less will it use it or start it.

I'm not sure what tried to initiate it, but it wasn't either of those two
for sure.

>Anyway, I thought I
>might move it to /var/spool/spamassassin/ per the mailscanner version of
>spamassassin user pref file.  I figure I can just stop MS, edit the
>spamassassin file to uncomment out the bayes_path, & bayes_file_mode, mv the
>files over, then restart.  Will that do it?

yes... however, if you want to use sa-learn, make sure to also update
/root/.spamassassin/user_prefs to include the new bayes_path as well,
otherwise sa-learn won't learn to the same bayes DB as mailscanner.

Personally, I just do this by keeping /root/.spamassassin/user_prefs and
mailscanner's /etc/MailScanner/spam.assassin.prefs.conf the same. I started
off by cp'ing the mailscanner file over-top of my user_prefs. Now when I
want to make a config change I do 4 steps:
         1) edit /root/.spamassassin/user_prefs and exit
         2) run spamassassin --lint to make sure I didn't goof up, and
maybe run some test mails through the command-line version.
         3) copy the new user_prefs over top of
/etc/MailScanner/spam.assassin.prefs.conf.
         4) restart mailscanner

This way root and MS always have the same config, and I get to test my
config options before going live.