Spam slipping through

[Michael Masse]

>>> On 1/19/2007 at 10:22 AM, in message
<86144ED6CE5B004DA23E1EAC0B569B581237B856 at isabella.herefordshire.gov.uk>,
"Randal, Phil" <prandal at herefordshire.gov.uk> wrote:
> You're possibly not picking up the sa-updated rules when running
> SpamAssassin from within MailScanner.  Running spamassassin from the
> command line will use them.
> 
> At some point SpamAssassin was fixed so that the local state dir
> included /spamassassin, e.g. /var/lib/spamassassin, and not
/var/lib.
> 
> See http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4952#c11 .
> 
> Try amending your MailScanner.conf to read like my config below
(which
> has been tested and verified to use the updated rules):
> 
> # The rules created by the "sa-update" tool are searched for here.
> # This directory contains the 3.001007/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
> 
> Jules, can you fix the default MailScanner.conf to match reality,
> please?
> 

Using Jules latest easy install package, my SpamAssassin local state
dir is still in /var/lib/

Mike