Spam slipping through

[Randal, Phil]

No, my whole point was that the MailScanner.conf documentation is wrong.
It change with 3.1.4 or 3.1.5, IIRC.

Cheers,

Phil

--
Phil Randal
Network Engineer
Herefordshire Council
Hereford, UK  

> -----Original Message-----
> From: mailscanner-bounces at lists.mailscanner.info 
> [mailto:mailscanner-bounces at lists.mailscanner.info] On Behalf 
> Of Michael Masse
> Sent: 19 January 2007 17:35
> To: MailScanner discussion
> Subject: RE: Spam slipping through
> 
> >> "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
> > 
> > Mike,
> > 
> > What do you mean by that?  I'm confused.  Are you agreeing or
> > disagreeing with what I wrote?
> > 
> > Is that what it says in your MailScanner.conf?  Or you have some
> other
> > way of divining what the local state dir is?
> > 
> > My comments are based on standard installs of MailScanner and Jules'
> > Install-Clam-SA-3.1.7.
> > 
> > Cheers,
> > 
> > Phil
> > --
> > Phil Randal
> > Network Engineer
> > Herefordshire Council
> > Hereford, UK
> 
> 
> Sorry, I think this is a relative directory issue.     In the snippet
> of the MailScanner.conf you posted, you have the following line:
> # This directory contains the 3.001007/updates_spamassassin_org
> and so you would have to specify /var/lib/spamassassin.
> 
> In my MailScanner.conf that same line shows:
> # This directory contains the
> spamassassin/3.001001/updates_spamassassin_org
> so it appears as though my MailScanner automatically tacks on the
> spamassassin folder, and therefore I only need to specify  
> /var/lib.    
> After looking at this more, I'm concerned that it's showing 3.001001
> instead of 3.001007.   My actual spamassassin sa-update folder is:
> /var/lib/spamassassin/3.001.007.    Is there a way to check that MS is
> absolutely using the sa-updated files?
> 
> Mike
> 
> -- 
> 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! 
>