Strange SpamAssassin upgrade failure

James Gray james at
Wed Jan 21 08:44:16 GMT 2004

Hi All,

I had a strange one today.  I upgraded from SA 2.61 to 2.63 using the source
tar ball from  I did the usual "configure, make, make
test, make install" then restarted MailScanner.

Here lies the problem.  MailScanner restarted happily, SpamAssassin was
scanning happily but SA was ONLY using my custom rules in
/etc/mail/spamassassin!  All the standard rules in /usr/local/spamassassin
were being ignored.  I checked the permissions of the files in
/usr/share/spamassassin and they were all "644 root:root", the
/usr/share/spamassassin directory was 755.

Running "spamassassin --debug --lint -C
/usr/local/etc/MailScanner/spam.assassin.prefs.conf" mentioned NOTHING
about the "default rules dir".  However running without the "-C" option
showed both the default and site rules dirs.

The weirdest thing was when I reverted back to SA 2.61 (without changing ANY
config files) SpamAssassin started using all it's rules again.

Now when I lint the rules with MailScanner's spam.assassin.prefs.conf file,
both the default and site rules dirs are listed.

The system is running FreeBSD and the ports version of MailScanner.  But I'm
using the tar-ball (non-ports) version of SpamAssassin.  Perl is 5.8 from

Any ideas folks?

Fortune cookies says:
The less time planning, the more time programming.

More information about the MailScanner mailing list