spam.assassin.prefs.conf not being read - was Re: Problem with ALL_TRUSTED since 4.48

[Brian Lewis]

I'm having the exact same problem!!!
After upgrading to MailScanner 4.49.1, I find that although MailScanner is 
executing SpamAssassin 3.1.0, certain aspects of my SA 3.1.0 are not 
launching especially SNFILTER.  
spamassassin --lint -D
Works great, shows it executing SNFILTER properly
Yet I know its not executing via the MailScanner 4.49.1
Prevous Config was MailScanner 4.28 and it had no problem with SA 
3.1.0/SNFilter.

Any ideas?  File Permission somewhere?  
snfilter.pm/snfilter.cf as well as the /tmp/sniffertmp are all chmod 777

Any idea on how to make MailScanner launch the 'old way' yet use the new 
4.49.1 code?

------------------------ MailScanner list ------------------------
To unsubscribe, email jiscmail at jiscmail.ac.uk with the words:
'leave mailscanner' in the body of the email.
Before posting, read the Wiki (http://wiki.mailscanner.info/) and
the archives (http://www.jiscmail.ac.uk/lists/mailscanner.html).

Support MailScanner development - buy the book off the website!