On Wed, 2004-03-31 at 20:09, Charles Sprickman wrote: > On Thu, 18 Mar 2004, Jeremy Kitchen wrote: > > > > > I suggest the goal should be to let vpopmail do the work and make > > > qmailadmin as much as possible just a web interface to the vpopmail library. > > > > yea, but there's that old spam command stuff which is interfering with > > the changes I'm making. > > Well, it's not really "old". In fact, I use it. > > > I just wrote it to stomp on the old stuff since we have no customers > > actually using the --enable-spam-command stuff, and have high demand for > > being able to switch the spamassassin stuff on/off on a per user basis > > via qmailadmin. > > Could you define "stomp"? Does this mean I have to go undo all of this > everytime I update vpopmail/qmailadmin?
the change I made basically removes the old --enable-spam-command functionality. If you have existing .qmail files that have it, it should work fine. > Who is currently making decisions like "should we alter the existing > spamass support" and where does one make their voice heard about such > matters? I simply wrote a patch to make it work. I'm not a maintainer of the package, if they want to modify it to make it work along side with the existing stuff, go right ahead. We are not using the older --enable-spam-command stuff with our customers, so the patch I made doesn't affect any of them, other than allowing their users to enable/disable spamassassin scanning themselves. -Jeremy -- Jeremy Kitchen Systems Administrator [EMAIL PROTECTED] Kitchen @ #qmail on EFNet - Join the party! ..................... Inter7 Internet Technologies, Inc. www.inter7.com 866.528.3530 toll free 847.492.0470 int'l 847.492.0632 fax GNUPG key ID: 93BDD6CE
