Spamassassin not working after 4.53

[Julian Field]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Not quite.
After it has done it the first time, it will have some rules in the 
/var/lib/... directory. If it fails in future it just won't copy the 
screwed rules into place.

But yes, it has a bad failure mode that if it fails the first time it 
leaves you with a system that doesn't work properly.

Can Matt Kettler forward this to the SpamAssassin guys (e.g. Justin) and 
file this as a bug please?

Devon Harding wrote:
> So, to sum it up.  If sa-update has an issue (and creates an empty
> /var/lib/spamassassin/3.001001/), Mailscanner will look there for SA
> rules, not find any, and let SPAM through?

- -- 
Julian Field
www.MailScanner.info
Buy the MailScanner book at www.MailScanner.info/store
Professional Support Services at www.MailScanner.biz
MailScanner thanks transtec Computers for their support

PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654


-----BEGIN PGP SIGNATURE-----
Version: PGP Desktop 9.0.6 (Build 6060)

iQA/AwUBRFj1lBH2WUcUFbZUEQJmXwCg45Mhw4DqGXsLA4jb3xBJFFxO5AcAn0WI
kSHhFs5iF317OlDP+GyBM/go
=JhJh
-----END PGP SIGNATURE-----

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
MailScanner thanks transtec Computers for their support.