Noel, I agree with you about the blocking. I don't use it myself, just tagging.
One of the options is to include the spamminess probability in a message header. So changing this to being in a Mail attribute is trivial. -Chris > -----Original Message----- > From: Noel J. Bergman [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, January 29, 2003 2:49 PM > To: James Users List > Subject: RE: Spam filtering mailets wanted... > > > > The advantage of putting this code on the server side is so that ALL > clients > > can benefit from the SPAM blocking, and you "can" > > avoid the client even having to see the junk email > > Mind you, spam BLOCKING, as opposed to tagging, can be a bit of an issue > unless you are really sure that it is spam. As you noted, it > might be best > to X-tag the spam and deliver it to the user. It might be interesting to > play with the Bayesian filter and "confidence" levels: > > >H spam bucket > L< >H spam tag > <L not spam > > When we have Mail attributes, I'd like to see internal flow controlled by > attributes more than headers (not counting externally generated ones, of > course). The Bayesian filter could attach an attribute, other matchers > could select based upon the attribute, and a separate Mailet would support > converting attributes to X- headers. > > --- Noel > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
