Dear Ruairi Newman,
That's what I was afraid of. There's no way - other than a separate independent install of spamassassin - to control the Spamassassin threshold on a per user basis? And add per user whitelists?
Some Clarifications about Spamassassin Calling from MailScanner:
MailScanner calls the function library Mail::Spamassassin directly from Perl, gives the message directly to the function library, and gets the results straight back from it.
SA user_prefs files in individual people's home directories are not consulted by MailScanner, as it doesn't know where the mail is going or how to map an email address onto a user's home dir. You can only do that for local email accounts and even then only at the delivery stage, which means MailScanner would have to be involved in mail delivery.
~/.spamassassin is consulted only for restricted values of ~. Specifically, ~ here refers to the home directory of the mail user (users like root, mail, smmsp, postfix, qmailq ...etc). ~ does not refer to each user on the machine.
SpamAssassin User State Dir
This is the directory where SpamAssassin should store its state information for things like the Bayes database. It avoids having them pile up somewhere unhelpful such as /root or /home/smmsp. Note that only one directory can be specified, therefore it does not apply for each user on the system; there is only one setting.
hope that helps, cheers, Ganesh, KM. -- K.M.Ganesh | Mobile: +91 (0) 9444080290 Opencomputing Technologies | http://opencompt.com Server Side E-Mail Protection.
