Date: Thu, 9 May 2002 15:50:50 -0300 (ADT) From: "Marc G. Fournier" <[EMAIL PROTECTED]> Cc: Rob Siemborski <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>
Having an idea of how hard such is to do, and how long it could take, is there any way we can get the spam extension added as an #ifdef'd/configure option so that it doesn't get lost? There are more and more sites moving to Cyrus, due to its black box aspect, and, except in very simplistic cases, the arguments for how spam filtering can be done without it don't hold up, as I believe I was able to show today :( Personally I'm not hugely convinced by your argument; I think that way will just get increasingly confusing for users. I agree there is desirable functionality that is inaccessible, but I also can't believe that a site wanting a really scalable solution would be happy running messages through something like SpamAssassin many many times on the same machine as their mail store. I would guess that it would take at least a week and possibly more to re-architect and recode the internals of the Sieve module. Once the library can perform this function, then pulling out the #ifdef'd code and putting it into its own module would be simple enough ... I'm really not interested in maintaining the "spam" functionality. #ifdef's make it very difficult to reason about code. We'd be happy to put the patch into contrib/, but there's no guarantee that it'll continue to patch & compile cleanly. Larry
