SpamAssassin advanced setup questions
I have SpamAssassin (and Anomy) working with Postfix on Mandrake for the whole site/domain on a single server (single domain, no virtual domains). I am using spamc/spamd, although at first I was calling spamassassin as a script. Most the users never interface the Linux server directly, but rather check their email via POP on Windows machines. Everything is working great.
However, I want to be able to give the users their own whitelists, instead of using a single central one. The problem with having a central one is that I either have to A) Give the users access to the /etc/mail/spamassassin/local.cf or B) Have them send whitelist requests to me and enter them myself.
I found a very nice set of php scripts (WebUserPrefs 0.5) that will allow users to change their own settings into their own user_prefs files, and I have editted it to my liking and needs.
The problem is that the users don't current have any user_prefs files. Moreover, if I'm reading the documentation right, if I use spamc/spamd (daemonized version) then it will ignore users' user_pref (for security reasons). Is this true?
I am also confused as to the user_pref files. It seems by hints in the documentation (although it greatly confuses me, and thus my asking here) that if I place the user_prefs.template file in /etc/mail/spamassassin/, then it will create a basic one for the use based on this one. But also that this one overrides the local.cf, AND that using spamc/spamd will ignore it.
So, how do I alter a working setup from site-wide to user-based, having the users inherit a basic set of rules (especially a whitelist of all our clients, to which they can add their own)?
Should I use user_prefs.template instead of local.cf? And if so, is there a command to create the .spamasassassin directory and user_prefs for users? (I am guessing that command is spamassassin --lint, but do *I* run that command for all the users, or do the users run it themselves?).
I have read many tutorials, etc. but they mostly focus on site-wide, and those that didn't assumed the users already had a user_prefs file. And while I can manually create the initial ones for users or even create a script to very quickly do so, I was wondering if this is a part of SpamAssassin and I just haven't discovered how to use it.
Your help is appreciated. Any links to documents appreciated as well. (Note, I have read the tutorials posted on spamassassin.org, though).
Thanks! :)
However, I want to be able to give the users their own whitelists, instead of using a single central one. The problem with having a central one is that I either have to A) Give the users access to the /etc/mail/spamassassin/local.cf or B) Have them send whitelist requests to me and enter them myself.
I found a very nice set of php scripts (WebUserPrefs 0.5) that will allow users to change their own settings into their own user_prefs files, and I have editted it to my liking and needs.
The problem is that the users don't current have any user_prefs files. Moreover, if I'm reading the documentation right, if I use spamc/spamd (daemonized version) then it will ignore users' user_pref (for security reasons). Is this true?
I am also confused as to the user_pref files. It seems by hints in the documentation (although it greatly confuses me, and thus my asking here) that if I place the user_prefs.template file in /etc/mail/spamassassin/, then it will create a basic one for the use based on this one. But also that this one overrides the local.cf, AND that using spamc/spamd will ignore it.
So, how do I alter a working setup from site-wide to user-based, having the users inherit a basic set of rules (especially a whitelist of all our clients, to which they can add their own)?
Should I use user_prefs.template instead of local.cf? And if so, is there a command to create the .spamasassassin directory and user_prefs for users? (I am guessing that command is spamassassin --lint, but do *I* run that command for all the users, or do the users run it themselves?).
I have read many tutorials, etc. but they mostly focus on site-wide, and those that didn't assumed the users already had a user_prefs file. And while I can manually create the initial ones for users or even create a script to very quickly do so, I was wondering if this is a part of SpamAssassin and I just haven't discovered how to use it.
Your help is appreciated. Any links to documents appreciated as well. (Note, I have read the tutorials posted on spamassassin.org, though).
Thanks! :)
