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
