|
Per-User spamassassin configs |
|
|
|
Written by scott
|
|
Tuesday, 28 October 2003 |
One of the shortcomings of the current qmail-scanner rpm package is that the settings are global. The next big step with the package is to get that down to per user configs, and then to throw a web gui on it so my users can set thier own scores, whitelists, etc. So far Ive managed to get this working, just by manipulating the spamd flags. Setting this:
SPAMDOPTIONS="-u popuser -x -c -a -m5 --virtual-config-dir=/var/qmail/mailnames/%d/%l/ -d"
in /etc/sysconfig/spamassassin
So the good news with that is that ALL the users spamassassin settings get set from their mailnames homedir (ex: /var/qmail/mailnames/atomicrocketturtle.com/scott). You'll be able to drop a user_prefs file off in there, and the .spamassassin directory will store the auto whitelist, and baysien settins. The DOWN side is that for some reason, I cant seem to get the SQL settings to work with this at the same time. It might be that you cant actually do it, or it could be that I dont understand the docs correctly. Either way, I can get the user_prefs files to be loaded from SQL like this:
SPAMDOPTIONS="-u popuser -q -x -c -a -m5 -d"
or I can get the AWL/Baysien stuff to work with this:
SPAMDOPTIONS="-u popuser -x -c -a -m5 --virtual-config-dir=/var/qmail/mailnames/%d/%l/ -d"
but I cant combine the two, so I end up with user_prefs loaded from SQL, and the AWL/Baysien stuff at the same time. Hopefully someone else can look at this and tell me what Im overlooking.
Downside #2: It looks like spamd will just create any old user in the /var/qmail/mailnames/<domainname> dir. Which is bad if you're getting walked by spammers. It will create user directories that dont exist (dont worry, if theres no .qmail file, it wont work), but still, its annoying.
Only registered users can write comments.
Please login or register. Powered by AkoComment 2.0.3! |
