I have this working with only one quirk..

i run spamd standalone daemon with options -c -d -a -v -d -s local4 -u
vpopmail -D

my /etc/mail/spamassassin/local.cf defines a global AWL path.. in my case:

auto_whitelist_path     /etc/mail/spamassassin/whitelist/auto-whitelist
bayes_path              /etc/mail/spamassassin/bayes/
bayes_use_hapaxes       1

i can mail any config files if anyone is interested..

now for the bad news.. vadduser and qmailadmin do NOT create the
$VPOPMAIL/domains/$domain/$user/.spamassassin directory
if you mkdir and chmod it, user_prefs is copied the first email received..

i have had in the past where mail usernames could not be defined.. i.e.
unknown user.. in this case the mail was being delivered first to
so i created a [EMAIL PROTECTED] account and setup .spamassassin for
this user as well.. so far every message in and out gets spam checked no

preferences can be overridden in the
$VPOPMAIL/domains/$domain/$user/.spamassassin/user_prefs which is perms 666
vpopmail.vpopmail (i have no vchkpw group)
so in theory either group perms or keeping evil permissions will make it
possible to use webtools suth as PHP-SA to setup spam prefs. per user..

note the only real function i see disabled in this environment is per-user
auto whitelists..

Nathan Goodman
Unemployed Network Administrator
Casualty of April 2003 Cutbacks

----- Original Message -----
From: Bill Shupp <[EMAIL PROTECTED]>
Sent: Wednesday, September 10, 2003 8:23 PM
Subject: Re: [vchkpw] OT: vpopmail & spamd & user prefs

> On Wednesday, September 10, 2003, at 04:22  PM, Alex Martin wrote:
> > Please post this answer to the list!
> > I have been searching for this answer for two days now, and I was
> > about to
> > post to this list. I think a lot of people would like to know this.
> > -Alex
> Ok, here's where I'm at now:
> I upgraded to spamassassin 2.55, and am starting spamd like so from
> daemontools:
> #!/bin/sh
> exec /usr/bin/spamd -c -D -F0 -L -u vpopmail -v
> And spamc is called via maildrop with these options:
> /usr/bin/spamc -f -u [EMAIL PROTECTED]
> It's now working, but spamd seems to create
> ~/.spamassassin/.spamassassin on the first creation attempt, and
> reports and error that it could not create the prefs file.  Upon second
> attempt, it creates it successfully.  Still trying to pinpoint where
> that's breaking, but other than that it works.
> I'm using this in the context of WebUserPrefs, a PHP config tool for
> SpamAssassin, plus a new panel that allows for optional deletion of
> spam.  Once I get all this working smoothly, I'll post some docs on how
> it's working for me.  Looks pretty cool, tho.
> Cheers,
> Bill Shupp

Reply via email to