On Thu, 2 May 2002, Birger Toedtmann wrote: > Ken Murchison schrieb am Wed, May 01, 2002 at 09:36:24AM -0400: > > > > > > "Marc G. Fournier" wrote: > > > > > > Is there any chance that the 'spam' extension to sieve is going to get > > > added to the CVS? *cross fingers* > > > > I don't know about Larry, but I don't plan on adding it, for several > > reasons: > > > > 1. Nobody has made a good enough case for this belonging in Cyrus > > instead of the MTA (yes, I know that Sieve can be used anywhere, but > > this discussion has been in the context of Cyrus). > > > > 2. It goes against the design of Sieve, which does not call external > > programs (Sieve is not procmail or an anti-SPAM measure). > > > > 3. Its not documented. Currently most (if not all) features of Cyrus > > are standards-based, either via an RFC or ID. > > I fully agree with all of the above, anyone could insert X-Spam's at MTA > level as has been numerously pointed out by others. > > However, a side question: IF this weird "spam" extention somehow finds its > way into Cyrus because everyone wants it (hopefully not), will I (the admin- > istrator) be able to prevent my users using it? Or more generally: Is it > possible do disable _specific_ checks/features in sieve? > > I just imagine I won't be able to upgrade after 2.1.5 or <whatever version> > because my 50.000+ accounts will from then on do DNS lookups every n milli- > seconds..... Well, the other way to go will be to completely disable sieve > for good.
The suggestion/thought was that the 'external extension' would be purely a configure option ... hell, it wouldn't even be able to be enabled without spamassassin being detected ... it wouldn't be a 'default' thing, purely optional, at compile time ...
