>>>>> "KK" == Kjetil Kjernsmo <[EMAIL PROTECTED]> writes:
KK> The scoring systems seems like a very nice feature, and I figured it KK> would be nice to use it with several different thresholds: Personally, I'd never bit-bucket a message. Always return to sender, even if that means double-bounces on my end (which end up at dev null, but at least the sender gets the chance to see the bounce if they want). This is important for false-positives so the sender knows what happened. That said, I use 7 as the return to sender threshhold, and 4 as the mark for manual inspection level. KK> Would it be easy to set up SpamAssasin (and Exim) with something like KK> this? What would your thresholds be, if you were to do this? I use postfix + amavisd-new. I believe the next release will have the ability to mark at a certain threshhold and reject at another, and be tunable per recipient. But I'm not sure if these new features will make it in. KK> Something that wasn't quite clear to me with spamtraps (yes, I have a KK> few spamtraps), the message goes into Vipul's Razor, but isn't there a KK> bit of a lag there? So my concern was that if the spamtrap catches it, Yes, there is lag. But just think how long it takes to deliver millions of messages. Chances are sometimes you'll be the first reporter, and sometimes not. The overall effect is good, but it is not 100%. Just this weekend, I got some spam through that got into razor after I recieved it, and it would have been sufficient to block those messages had they already been listed. That's just how it works. _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas - http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
