Here is what I've learned so far regarding spamassassin per-user prefs with 
simscan.

1. Setting up Spamassassin SQL pref storage is well documented here:
http://wiki.apache.org/spamassassin/UsingSQL
This setup is the same regardless of how spamassassin is called.

2. But in order for per-user prefs to work with qmailtoaster, simscan must be 
configured to call spamc with the -u option:
        -u username 
    This argument has been semi-obsoleted. To have spamd use
    per-user-config files, run spamc as the user whose
    config files spamd should load. If you’re running spamc
    as some other user, though, (eg. root, mail, nobody,
    cyrus, etc.) then you can still use this flag.
Simscan will pass this automatically if the --enable-spamc-user option is added 
to %configure in the simscan-toaster.spec. It is not an ideal method, because 
per-user prefs will ONLY be used if an email has a single recipient. Otherwise, 
the global prefs will be used. This is all described on the Simscan/Guide page:
http://www.qmailwiki.org/index.php?title=Simscan/Guide&redirect=no#Multiple_Recipient_Problem_with_Per_User_simscan_option

I wish a better solution existed, maybe somehow letting simscan process 
single-recipient message, but if the message has multiple recipients pass the 
message through spamassassin *again* at the user level during delivery (maybe 
with vpopmail's --enable-spamassassin or a maildrop rule).

3. spamd must be run with the -q and -x options:
        -q, --sql-config        Enable SQL config (only useful with -x)
        -x, --nouser-config             Disable user config files

4. For users to edit their prefs, a web-based interface needs to be installed. 
The SquirrelMail plugin is well regarded:
http://www.squirrelmail.org/plugin_view.php?id=167
But we're using Horde/IMP so we'll probably use a stand alone script such these 
(or write our own):
http://wiki.apache.org/spamassassin/WebUserInterfaces

The TNPI toaster project has some instructions to get this all working:
http://www.tnpi.biz/internet/mail/toaster/filtering/content/spamassassin/per-user.shtml

I'll get this going on my migration server and report back.

Quinn



On Mon, 09 Oct 2006 12:21:06 -0700, Eric "Shubes" wrote:
> I'd like to see the basic toaster move in this direction. What will it take
> to make this happen?

Reply via email to