MailScanner 4.50.15 not picking up new rules from sa-update

[Martin Hepworth]

Adri

Have a look in MailScanner.conf and the Advanced SpamAssassin Settings
section. You can put extra things into the SA rules path there,

Also I presume you're restarting MS after the update and not just waiting
for the children to die?

--
Martin Hepworth 
Snr Systems Administrator
Solid State Logic
Tel: +44 (0)1865 842300

> -----Original Message-----
> From: mailscanner-bounces at lists.mailscanner.info [mailto:mailscanner-
> bounces at lists.mailscanner.info] On Behalf Of Adri Koppes
> Sent: 06 April 2006 09:03
> To: mailscanner at lists.mailscanner.info
> Subject: MailScanner 4.50.15 not picking up new rules from sa-update
> 
> I am running the MailScanner port on FreeBSD 5.4 with sendmail as my MTA
> and SpamAssassin 3.1.1.
> I recently ran the 'sa-update' program included in SpamAssassin to pick
> up newly added and changed rules.
> The sa-update program correctly downloads the updated rules to the
> default location of
> '/var/lib/spamassassin/3.001001/updates_spamassassin_org' and when
> running spamassassin -D --lint, I can see the new rules being used.
> However the new rules are NOT being used by SpamAssassin when called
> from inside MailScanner.
> I believe this is due to an omission in SA.pm when creating a new
> instance of Mail::SpamAssassin.
> The LOCAL_STATE_DIR config option, which is normally '/var/lib' is not
> included in the $settings.
> 
> Adri.
> --
> 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!


**********************************************************************

This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote confirms that this email message has been swept
for the presence of computer viruses and is believed to be clean.	

**********************************************************************