if you look in this block of the config.php file

// user_prefs File Location
// If you typed "file" for $prefs_source above, set this variable
// to the location of the user_prefs file. If you included
// authorization above, use the $auth_user variable to include
// the user_prefs file for the user that logged in.
                                                                                       
                                                      
// $user_prefs  = "/path/to/user_prefs";
// $user_prefs  = "/home/$auth_user/.spamassassin/user_prefs";
                                                                                       
                                                      
You can set it there by uncommeting the line right above and
adjusting it to the path for your home directories
to use it with vpopmail on virtual domains it's a little more
tricky than this though ... you would have to log in with the whole
email adress and split it to grab the domain or have it grab the domain
from the url you referenced it with ...

either way you would have to end with something like this

$user_prefs  =
"/home/vpopmail/domains/$domain/$auth_user/.spamassassin/user_prefs"


a much easier way is to use spamassassin with MySQL userprefs ... it
works really well and as a side benefit their prefs easily replicate
across many machine if you add a bunch more and it doesn't create a
bunch of files and directorys to clutter up the place.

notice the 



// $prefs_source   = "db";
// $prefs_source                = "file";


in the config ... just uncomment the one you want.

locally I have about 10k user spread across 6 machines

the only thing on my wish list is what I mentioned here already ...

I would like to be able to specify 2 spam commands in qmailadmin
2 checkboxes one that could be labeled filter and one that could be
labeled identify.

this is so that my users could have the option of having their mail sent
to a quarantine box and never recieving it in their inbox 

and one for people that just want the spam to be tagged and delivered
so  that they can split it out in mailfolders for themselves with rules
on their mail client.

David

On Thu, 2004-01-08 at 11:04, Ken Jones wrote:
> Hi David,
> 
> I checked this out. Looks really nice. One thing I can't figure
> out is how to set the user_prefs directory. Do you know how
> to do that?
> 
> On Tuesday 06 January 2004 10:33 pm, David Rodgers wrote:
> > there is already an amazing tool for this it's called webuserprefs
> >
> > http://www.pipegrep.net/webuserprefs/
> >
> > it can use flat local.cf files or a db for spamassassin  prefs and
> > manages its
> > own auth via imap/pop3/squirrelmail
> >
> > if you use the mysql option you get the added benefit of not having to
> > save the individual files for every user
> > just one dump and you're all backed up.
> >
> > also of interest is that you can extend it's functionality pretty
> > easily by adding panels to it.
> >
> > David Rodgers
> >
> > Ken Jones wrote:
> > >Not quite what I was looking for. I'm probably going to start
> > >working on some changes to add support for spam assassin,
> > >with a --enable-spamassassin option.
> > >
> > >Basicly to allow a user to change their user_prefs file so they
> > >can manage whitelisting and change their hit count.
> > >
> > >Probably it would be best to add it to a new devel version
> > >after 1.2 is released as stable.
> > >
> > >Does anyone have any suggestions?
> > >
> > >Ken Jones
> > >
> > >On Tuesday 06 January 2004 12:43 pm, Rick Widmer wrote:
> > >>Kind of.
> > >>
> > >>--enable-modify-spam  adds a "Spam detection?" checkbox at the bottom of
> > >>the modify users page.  If checked this changes the "Standard" delivery
> > >>option from no .qmail file to one that contains the spam command.  It
> > >>changes the delivery line in "Vacation" delivery, and the "Save a copy"
> > >>option of "Forward to" deliveries from a direct maildir delivery to the
> > >>spam command.
> > >>
> > >>The default spam command is:
> > >>|preline /usr/local/bin/maildrop /etc/mailfilter
> > >>
> > >>It can be set with --enable-spam-command
> > >>
> > >>
> > >>Rick
> > >>
> > >>Ken Jones wrote:
> > >>>Is there currently any support for spam assassin in the
> > >>>latest qmailadmin releases?
> > >>>
> > >>>Ken Jones
> 
-- 
Thanks,
David Rodgers

------------------------------------------------
SCO aka The Santa Claus Operation 
If you believe in them you'll believe anything! 

Reply via email to