On Wed, 2003-10-01 at 13:43, Steve Heggood wrote: > On Wed, 2003-10-01 at 12:27, Radek Doul�k wrote: > > Hi all, > > > > Plugin will be shared library which will be loaded by dlopen/dlsym. Evo > > will get SpamFilterStruct by dlsym, check api_version and then use > > supplied methods. > I would like to see pipe out/in supported so that spamassassin could > be called.
radek's proposal is that spam filtering was done in a dynamically runtime-loaded module... this module would likely pipe to spamassassin or the like. there's no reason there needs to be a second pipe/exec feature for spam filtering. > > Also, it would be GREAT if a mechahnism could pe provided for auto > imports. I don't see what this has to do with spam filtering? > > Suppose you had /evolution/spool/spam60 that contained > mbox format messages that external filter had classified as 60 percent > spam probability. > In the mail scan cycle, have evolution check the spool directory, place > a lock file there, import the data into a folder matching the filename, > and release the lock. > This would be useful in areas other than spam as well. huh? I don't understand the point of this at all. assuming this was to seed the spam filter (bayesian algorithm?), why couldn't the bayesian spam filter plugin code do this? :-) -- Jeffrey Stedfast Evolution Hacker - Ximian, Inc. [EMAIL PROTECTED] - www.ximian.com _______________________________________________ evolution-hackers maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/evolution-hackers
