Local State Dir - /var/lib/spamassassin - SARE rules no hits

[Martin Hepworth]

2008/11/21 Daniel Flensburg <Daniel.Flensburg at iris.se>:
> Can someone please help me with a strange problem. I noticed that my
> recently downloaded SARE-rules have no hits. I believe non of the rules
> in the /var/lib/spamassassin work.
>
> When running the command:
>
> spamassassin -D --lint
>
> I get the result (looks just right):
>
> [4446] dbg: config: using "/etc/spamassassin" for site rules pre files
> [4446] dbg: config: read file /etc/spamassassin/init.pre
> [4446] dbg: config: read file /etc/spamassassin/v310.pre
> [4446] dbg: config: read file /etc/spamassassin/v312.pre
> [4446] dbg: config: using "/var/lib/spamassassin/3.001004" for sys rules
> pre files
> [4446] dbg: config: read file
> /var/lib/spamassassin/3.001004/saupdates_openprotect_com.pre
> [4446] dbg: config: read file
> /var/lib/spamassassin/3.001004/updates_spamassassin_org.pre
> [4446] dbg: config: using "/var/lib/spamassassin/3.001004" for default
> rules dir
> -------------------
>
> But when I run the command:
>
> /opt/MailScanner/bin/MailScanner --debug --debug-sa
>
> I get a different result (a bad one):
>
> [4329] dbg: config: using "/etc/mail/spamassassin" for site rules pre
> files
> [4329] dbg: config: read file /etc/mail/spamassassin/init.pre
> [4329] dbg: config: read file /etc/mail/spamassassin/v310.pre
> [4329] dbg: config: read file /etc/mail/spamassassin/v312.pre
> [4329] dbg: config: using "/usr/share/spamassassin" for sys rules pre
> files
> [4329] dbg: config: using "/usr/share/spamassassin" for default rules
> dir
>
> The setting in my /opt/MailScanner/etc/MailScanner.conf is:
>
> # The site-local rules are searched for here, and in
> prefix/etc/spamassassin,
> # prefix/etc/mail/spamassassin, /usr/local/etc/spamassassin,
> /etc/spamassassin,
> # /etc/mail/spamassassin, and maybe others.
> # Be careful of setting this: it may mean the spam.assassin.prefs.conf
> file
> # is missed out, you will need to insert a soft-link with "ln -s" to
> link
> # the file into mailscanner.cf in the new directory.
> # If this is set then it replaces the list of places that are searched;
> # otherwise it has no effect.
> #SpamAssassin Local Rules Dir = /opt/MailScanner/etc/mail/spamassassin
> SpamAssassin Local Rules Dir =
>
> # The rules created by the "sa-update" tool are searched for here.
> # This directory contains the 3.001001/updates_spamassassin_org
> # directory structure beneath it.
> # Only un-comment this setting once you have proved that the sa-update
> # cron job has run successfully and has created a directory structure
> under
> # the spamassassin directory within this one and has put some *.cf files
> in
> # there. Otherwise it will ignore all your current rules!
> # The default location may be /var/opt on Solaris systems.
> SpamAssassin Local State Dir = # /var/lib/spamassassin
>
> # The default rules are searched for here, and in
> prefix/share/spamassassin,
> # /usr/local/share/spamassassin, /usr/share/spamassassin, and maybe
> others.
> # If this is set then it adds to the list of places that are searched;
> # otherwise it has no effect.
> #SpamAssassin Default Rules Dir = /opt/MailScanner/share/spamassassin
> SpamAssassin Default Rules Dir =
> ------------
> I tried to remove the # in the line below but the result is the same:
> SpamAssassin Local State Dir = # /var/lib/spamassassin
>
> What have I missed?
>
> I have a rather old version of SA 3.1.4 - but I do not want to upgrade
> until I have a backup MS server running, unless an upgrade is the fix
> for this strange behavior.
>
>
> /Daniel
> --
> MailScanner mailing list
> mailscanner at lists.mailscanner.info
> http://lists.mailscanner.info/mailman/listinfo/mailscanner
>
> Before posting, read http://wiki.mailscanner.info/posting
>
> Support MailScanner development - buy the book off the website!
>
Daniel

try making the "SpamAssassin Local State Dir" blank ..

SpamAssassin Local State Dir =

depending on how you've installed the SARE rules you should either be
in /var/lib/spamassassin/3.001004 or /etc/mail/spamassassin.

another thing..check the user mailscanner runs as can access the SA
rules in "/var/lib/spamassassin/3.001004" (file permissions).

-- 
Martin Hepworth
Oxford, UK