Please don't get offended, I think what you're doing is great, but I think a big step was missing from the process, that of collection of requirements/features desired. I would imagine there are dozens of ways that people are implementing SA, some of which are good and others which are cludgey and nasty. I think it would be nice to gather information on these various methods and then settle on 1-2 ways to support this through qmailadmin. For instance, if enabling spam filtering for an entire domain by default were as simple as setting a value in the limits file, then cool, as long as my users can then also update their SA preferences which I current store in a SQL db. I do, however, already have a small plugin for my SquirrelMail webmail interface that customers use to modify their SA preferences (required_hits, blacklist_from, whitelist_from). If we all compare notes on current implementation techniques, we can probably very easily refine them down to a couple solid techniques that can then be thoroughly supported through qmailadmin.
> -----Original Message----- > From: Todd Brill - One Smart Company Sysadmin [mailto:[EMAIL PROTECTED] > Sent: Tuesday, July 08, 2003 12:14 PM > To: Benjamin Tomhave > Cc: [EMAIL PROTECTED] > Subject: RE: [qmailadmin] Help with code! SpamAssassin integration > > > The development has already begun and announced on this list. SA > integration (IMHO) > is something the community wants, I want, and is truly needed. > This project was > started due to the many shortcomings of the Qmailadmin install > process and (mainly) > the interface. > > If the community doesn't like what I'll be offering, so be it, > but I will be > offering this to my customers in leiu of Qmailadmin since my > server setup will > always be the same. :) > > That being said, I agree that we need to know where the > Qmailadmin/Vpopmail w/ MySQL > coding/configuration is going so that we can develop accordingly. > Of course, I'm > more interested in the development of Vpopmail since I'm > essentially coding a PHP > replacement for Qmailadmin. :) > > ==================================== > One Smart Company Hosting Inc. > Affordable Dedicated eMail, eCommerce, and Web servers. > !!! 30-day CASH BACK Guarantee !!! > !!! Unbeatable Price Guarantee !!! > http://www.1osc.com > > > It would probably be worthwhile to level-set things before > launching into > > new development. Where is functionality today in qmailadmin, > how are people > > using SpamAssassin, and how can qmailadmin then be updated to > support those > > uses? > > > >> -----Original Message----- > >> From: Todd Brill - One Smart Company Sysadmin [mailto:[EMAIL PROTECTED] > >> Sent: Tuesday, July 08, 2003 12:04 PM > >> To: [EMAIL PROTECTED] > >> Subject: Re: [qmailadmin] Help with code! SpamAssassin integration > >> > >> > >> I am also integrating SA support into my PostOffice front-end > >> project so I want to > >> see where this is leading development-wise before I start making > >> decisions in the > >> code as to the logic and functionality. > >> > >> Todd Brill > >> > >> ==================================== > >> One Smart Company Hosting Inc. > >> Affordable Dedicated eMail, eCommerce, and Web servers. > >> !!! 30-day CASH BACK Guarantee !!! > >> !!! Unbeatable Price Guarantee !!! > >> http://www.1osc.com > >> > >> > On Tue, 2003-07-08 at 11:27, Tom Collins wrote: > >> > > >> >> I'd really like to see these systems working toward using per-user > >> >> prefs stored in MySQL (see > >> >> <http://useast.spamassassin.org/dist/sql/README> for more > information > >> >> on that feature) and eventually adding an interface as an > extension to > >> >> the modify user page where users can update their personal settings > >> >> (adding addresses to a whitelist or blacklist would be a > good start). > >> >> > >> > > >> > There is currently a project underway (in alpha) to integrate the > >> > spamassassin prefs into horde-imp, which is probably the most logical > >> > place for spamassasin prefs. The project is at: > >> > http://cvs.horde.org/cvs.php/sam for those that are > interested. That'll > >> > work alright unless you use sqwebmail as I do. There is also > a php based > >> > interface for setting spamassassin prefs at: > >> > http://webuserprefs.pipegrep.net/ > >> > > >> > -- > >> > Neil Jolly > >> > > >> > (with Yoda-like voice) > >> > "Confrontation leads to anger... Anger leads to fear... Fear leads > >> > to using Windows NT in mission-critical combat systems... > And this is > >> > how the ancients fell... > >> > > >> > > >> > > >> > >> > > > > > > > >
