[dev] Re: [cvs] commit: passwd main.php passwd/config backends.php.dist passwd/docs CHANGES passwd/templates/main main.inc

[Max Kalika]

Quoting John Morrissey <jwm at horde.net>:

> On Fri, Jul 18, 2003 at 10:49:31AM -0700, Max Kalika wrote:
> % Quoting Chuck Hagenbuch <chuck at horde.org>:
> % > Also, is this really needed?
> 
> I need to use sam's white/blacklist support with imp, but I can't show my
> users the SpamAssassin settings. It'll confuse 99% of them.
> 
> % How about a list of configured/allowed capabilities?  I.e. Allow setting
> % the score, but disallow rewriting subject?
> 
> I'm willing to write this - would a simple multienum in conf.xml suffice?
> When sam is configured, the "allowed" rules attributes could be selected.

I'm going to be using amavisd-new (<http://www.ijs.si/software/amavisd/>)
on my new mailserver which can do per-user spam settings, unfortunately it
stores and has drastically different items.  Which is why I proposed a list
of capabilities.  I'm still not sure what the best way to go about
supporting both.  I think amavisd-new is popular so if we could support its
way of doing things, it would be a big bonus.

For a reference, please see the "SQL Lookups" section (esp the table
definitions) in <http://www.ijs.si/software/amavisd/README.lookups>

---max kalika
--max at lsit.ucsb.edu
-lsit systems administrator