On Tue, Dec 31, 2002 at 04:40:31PM -0500, Doug Eubanks wrote: > Would it be possible to get the coded remerged that allowed SpamAssassin to stop >checking once it reached a certain score and have it disabled by default (turned back >on with a configure option maybe?) because it really was a life saver for those of us >who need it. :-D
It _never_ worked! Putting it back in slows down those of us that don't use it. Furthermore, it is likely to cause FP's, since it _never_ worked! Since it _never_ worked, there is no reason to add it again. You'd be better off having spamassassin spit your mail out after a random period of time. Spamd/spamc are quite fast and used in a large number of different sitewide situations, and I would bet only a very very small number of those use the (broken) -S flag. I sincerely doubt you _need_ it, as you claim. daf@green:~$ date -u Tue Dec 31 22:26:15 UTC 2002 Furthermore, there is an enhancement freeze happening at midnight tonight (or last night, depending on who you ask). There is no way it will be re-added for 2.50. > I do not use the auto-whitelist feature, I guess that I am just trying to figure out >a solution that might fit everyone's needs. When will the 3.0 code be available and >it is even in development stages yet? The auto-whitelist feature is essentially irrelevant to this discussion. The 3.0 code is in early stages (pre-alpha?) of development. It can be obtained in the same way as spamassassin cvs, the module is spamassassin3. -- Duncan Findlay ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk