Spam slipping through

[Julian Field]

Randal, Phil 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?
>   
Can I be reasonably sure that the sa-update will work? And what triggers 
it? Do I need another cron job to do this, or does SpamAssassin do it on 
its own? Please include me directly as my personal address in a Cc for 
this one, I have been trying not to miss a deadline by too much, and 
would still very much like to do a stable release on 1st Feb. It's been 
far too long since the last one. I want to include everything except the 
new p records in Postfix, so if there's anything that needs 
fixing/changing, send it to me personally as soon as possible, as I hope 
to have some time this coming week to work on MailScanner. So I need to 
know the list of outstanding jobs!
> I've posted on the list about this on November 22nd and 23rd last year -
> I spent a productive hour one evening testing various "SpamAssassin
> Local State Dir" settings on a production server
>
> 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 Raymond Dijkxhoorn
>> Sent: 19 January 2007 15:55
>> To: MailScanner discussion
>> Subject: RE: Spam slipping through
>>
>> Hi!
>>
>>     
>>> Thank you, but that doesn't seem to be the problem.  When I 
>>>       
>> run the same 
>>     
>>> mail through spamassassin on the command line, it hits more 
>>>       
>> rules than 
>>     
>>> when it's running through MailScanner.  Both are using the 
>>>       
>> same config.
>>
>> And thats not due to the fact its added LATER on URIBL for 
>> examle? So you 
>> hit more rules when you recheck in time?
>>
>> Bye,
>> Raymond.
>> -- 
>> 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! 
>>
>>     

Jules

-- 
Julian Field MEng CITP
www.MailScanner.info
Buy the MailScanner book at www.MailScanner.info/store

MailScanner customisation, or any advanced system administration help?
Contact me at Jules at Jules.FM

PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
For all your IT requirements visit www.transtec.co.uk



-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
For all your IT requirements visit www.transtec.co.uk