Spamassassin not working after 4.53

Adri Koppes adrik at salesmanager.nl
Wed May 3 14:13:58 IST 2006


 

> -----Original Message-----
> From: mailscanner-bounces at lists.mailscanner.info 
> [mailto:mailscanner-bounces at lists.mailscanner.info] On Behalf 
> Of Glenn Steen
> Sent: woensdag 3 mei 2006 15:06
> To: MailScanner discussion
> Subject: Re: Spamassassin not working after 4.53
> 
> On 03/05/06, Devon Harding <devonharding at gmail.com> wrote:
> > > Is this really the complete debug run? It looks a bit 
> .... cut of in 
> > > the middle, to me at least.
> >
> > Here is the command I use:
> > spamassassin -x -D -p 
> /etc/MailScanner/spam.assassin.prefs.conf --lint
> >
> > > Do you employ the digest checks...? There's no mention of 
> those, nor 
> > > of actually using bayes... Just that a version 3 db is found...
> >
> > Also using MySQL for bayes storage.
> 
> i think Adri is right... Seems like many of the default rules 
> simply aren't there. Does /var/lib/spamassassin/3.001001 
> contain any rule files? Or are they in /usr/share/spamassassin?

On a normal installation of SA, the default rules will reside in
/usr/share/spamassassin.
After running sa-update, the default rules will wtill stay in
/usr/share/spamassassin, but a new directory with the all old and
updated default rules will be created under
/var/lib/spamassassin/3.001001.
When running SA and the local_state_dir variable is set, it SA will NOT
look in /usr/share/spamassassin anymore for default rules.

Adri.


More information about the MailScanner mailing list