I've solved my problem by putting my spam/ham into a folder and having cron se-learn/delete it periodically.
Personally I don't feel that mail clients should be playing the role of an MTA, and so including native spamassassin support in evo2.0 does not appeal to me. Filtering email should be something that procmail does. In any event, a "pipe email to shell command" is something that would be useful, should any developers be so inclined to write one. -Peter =) On Fri, 2004-01-09 at 10:39, Ian Robertson wrote: > On Fri, 2004-01-09 at 10:09, guenther wrote: > > BTW: Evolution 2.0 will come with built in SpamAssassin based junk mail > > filtering built in. :) > > Will only SpamAssassin be supported? I have been using spamprobe, and > I'd hate to see the database I've built up be thrown away. Similarly, > others use Bogofilter, and so on. > > Now of course, each of these programs use different APIs, but at the > core, it seems that what is needed from the UI perspective are > buttons/key-combos to reclassify spam as ham, and visa-versa. I would > think that all that would be needed would be configuration options for > how to handle messages that such actions were taken on. > > Of course, I suppose I could just continue my current method of labeling > the message as spam, and applying filters, but that's an annoying two > step process, especially since have to use the mouse to set labels... > > - Ian _______________________________________________ evolution maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/evolution
