MailScanner 4.50.15 not picking up new rules from sa-update

Adri Koppes adrik at salesmanager.nl
Mon Apr 10 09:03:58 IST 2006


 

> -----Original Message-----
> From: mailscanner-bounces at lists.mailscanner.info 
> [mailto:mailscanner-bounces at lists.mailscanner.info] On Behalf 
> Of Kai Schaetzl
> Sent: zondag 9 april 2006 17:09
> To: mailscanner at lists.mailscanner.info
> Subject: Re: MailScanner 4.50.15 not picking up new rules 
> from sa-update
> 
> Adri Koppes wrote on Fri, 7 Apr 2006 09:30:46 +0200:
> 
> > It seems to be sa-update downloads the rules into a 
> separate directory. 
> 
> yes, either beneath /etc/mail/spamassassin when I don't 
> specify the path and if I specify the path then down there. I 
> can't see a reason why SA should use it there, it doesn't 
> know of the path. sa-update doesn't add this path to the SA 
> configuration.

What is your LOCAL_STATE_DIR set to in /usr/local/bin/spamassassin?
If sa-update puts the updates in the directory pointed to by
LOCAL_STATE_DIR, spamassassin will automatically pick them up, replacing
the rules from the system rules.

> > Have you tried running spamassassin -D after running sa-update? 
> 
> As I said, it won't use that path nor will it use any 
> subdirectory off /etc/mail/spamassassin - in that case it 
> would just gulp all my rulesdujour a second time.
> 
> > SpamAssassin should find the updated rules from the 
> subdirectory and use them.
> 
> >From my experience: no.

Try putting the updates in LOCAL_STATE_DIR and try again.
 
Adri.


More information about the MailScanner mailing list