Manuel Lemos wrote: > > ------------------------------------------------------------------------ > Most of e-mail anti-spam systems filter messages on the mail server side > but that is no good to me because most of them use rules that are too > generic and often confuse messages that you want to receive with real > spam, even if those messages would be considered as spam by others.
*where* mail is "filtered" is an orthogonal problem IMO (whether client side, server side, or proxy side). > - Filtering is determines if a messages is considered to be spam, not > spam or maybe. Besides the usual rules for filtering, there should be a > way to add more methods to figure if a message is spam/not/maybe. This > should allow the addition of plugins, maybe using Javascript to query > remote knowledge anti-spam knowledge bases like Razor's. 4.x provided JS mail filtering which allowed the user to write their own JS to do the filtering they wanted; very powerful! however this approach (user editing JS) is obviously useless to the average user. front ending such a model w/ GUI might be interesting. providing a base set of general rules that build a JS file for the user and use it in the background. we should consider the open source model used by spam assasin (http://spamassassin.taint.org/). they use a modifiable point based system and the user could set their tolerance level accordingly. Jud
