Spamassassin/mailscanner

[James Gray]

On Fri, 8 Oct 2004 01:01 am, Rodney Green wrote:
> Any known issues with updating spamassassin to version 3? If I install the
> updated version of spamassasin will it work with MailScanner automatically?
> I have MailScanner configured to use SA and have been using it for a while
> now.
>
> Thanks,
> Rod

As Michele Neylon suggests - there is a lot in the last 3 months of archives
for this list, but having done exactly what you are considering  just a few
days ago, here's the "gotcha's" that caught us:

1. Remove the Spamcop URI plug-in rules (if you're using them) - this is
   included by default in SA3.  No need to remove the actual plug-in, just the
   rules.

2. SA3 seems a lot more strict about rule name and description lengths (names
   <= 22chars, descriptions <= 50chars).  We had almost 300 rules or
   descriptions that were "too long".  This shows up when you "--lint" the
   rules (see #4).

3. UPGRADE THE BAYES DATABASE *BEFORE* starting SA3:
   sa-learn --sync -p /opt/MailScanner/etc/spam.assassin.prefs.conf [-D]
   (See note in #4 about running as mail user)

4. Lint all your rules before restarting MailScanner and FIX ANY PROBLEMS:
   spamassassin -p /opt/MailScanner/etc/spam.assassin.prefs.conf --lint [-D]
   If you run your MTA as a specific user (ie, non-root), encapsulate the
   above in an "su" as root:
   su - <mail-user> -c "spamassassin -p....." statement

Other than those four little hic-ups, the upgrade "Just Worked" (tm).  Kudos
to Julian and the SA team!

Cheers,

James

------------------------ MailScanner list ------------------------
To unsubscribe, email jiscmail at jiscmail.ac.uk with the words:
'leave mailscanner' in the body of the email.
Before posting, read the MAQ (http://www.mailscanner.biz/maq/) and
the archives (http://www.jiscmail.ac.uk/lists/mailscanner.html).