How does MailScanner docide which spamassassin rules dir to use

[Anthony Cartmell]

>> I run MailScanner 4.55.10-3 and spamassassin 3.1.5-1. I enabled
>> sa-update. But I found MailScanner still uses "/usr/share/spamassassin",
>> NOT "/var/lib/spamassassin/3.001005/", for default spamassassin rules
>> dir. What should I change to let user /var/lib/spamassassin/3.001005/?

I have this too, for 3.001003.

> Did sa-update succeed?

Yes.

> Do you have all the rules "moved and updated"
> to the /var/lib/spamassassin/<version> directory?

Yes.

> Are you sure you are
> running version 3.1.5?

Yes (well 3.1.3).

> No duplicate SA install?

No.

> Can the user you run
> your MTA as (and thus MailScanner ... and SA) read the files in
> /var/lib/spamassassin/<version>?

Yes.

> Short answer "it should work" isn't much help, but perhaps you can
> find a bit more info from the above questions:-). As a stopgap thing
> you could set the Default Rules Dir option, but it's probably better
> to try deduce why it isn't working as intended;-)

spamassassin reads the rules in /var/lib/spamassassin/<version> when  
called direct, but not when called from MailScanner :(

I'm using spamassassin installed by yum for Fedora Core 5. I might try  
installing the version from MailScanner's web site...

Cheers!

Anthony
-- 
www.fonant.com - Quality web sites