Hi! On 03/20/2008 10:14 AM Ammar Ibrahim wrote: >> I like this idea. I would suggest to combine implementations for several >> spam detection mechanisms under a common hood. I imagine a component >> where you can configure a pipeline of spam detection mechanisms you'd >> like to use and then make it check a certain text.
> I really like the idea of the pipeline! And maybe we can have a set of > pre-configured pipelines for common tasks, e.g. "blog comment > pipeline", where we would try to find the optimal pipeline to detect > blog spam. Agreed. :) >> Ideas for spam detection mechanisms I have in mind are: >> >> - DNSBL >> - SURBL >> - Akismet >> - Bayes >> - Rule based > This is exactly what I had in mind when I was chatting with Thomas > yesterday. I guess we need to grow the list and make it more > comprehensive. Would something that interfaces into used email spam > detectors be of use(e.g. spam assassin)? or is that too much hassle > and out of the scope to be included in such a component. Why not? In fact, this component would be a bit like Spamassassin, since this one is mainly rule based and also integrated DNSBL and Bayes checks. However, it might be interessting to integrated anyway. :) Since the component should be "easily extendable", as usual, integration of SA should not be a problem to do for oneself, if it does not make it into the component. Ammar, could you create a requirements draft for such a component? Regards, Toby -- Mit freundlichen Grüßen / Med vennlig hilsen / With kind regards Tobias Schlitt (GPG: 0xC462BC14) eZ Components Developer [EMAIL PROTECTED] | eZ Systems AS | ez.no -- Components mailing list [email protected] http://lists.ez.no/mailman/listinfo/components
