> Thus spake Karsten M. Self (kmself@ix.netcom.com):
> 
> > There are two aspect to dealing with spam.  One is filtering the
> > messages.  The other is reporting it.  
> 
> You can configure a threshold above which spamassassin will report spam
> as well.  I'm not sure of the details, though. 
> 
> > My filters provide similar functionality to spamassasin.  The response
> > scripts fill in an additional role.
> 
> Nice, I will have a look at your setup sometime. :-)

I was going to keep my peep shut, as discussing spam in any notable detail
often gets more painful than the original slice.  (I can cheerfully hit
d-lete on the first one.  The replies may have useful things.)

But after some recent client work in the category I heartily recommend the
set of scripts at spambouncer.org.   

The woman there maintains them;  you can check into the scoring levels by 
various subcategories - as seperate recipes, so they are much easier to 
read than most.  For instance I was able to go in and tweak the "anti porn" 
category to be more brutal in its scores.  As a result, there are far less 
burning ears over in cube-land, and the client is quite happy.  She already 
has programmed in having an options-file so you can toggle various preferences
(such as complaining upstream).  It adds headers to things so if you have a 
site where people have different opinions, they can apply their own 
Judgements via their MUA or personal procmail script, using the scores and 
comments.

and yes, she accepts "fresh spam" at a spamtrap address, providing that it
has actually failed to be spotted by her recipes.

Good luck in the war vs. unpleasant bulkmail.

  . | .   Heather Stern                  |         [EMAIL PROTECTED]
--->*<--- Starshine Technical Services - * - [EMAIL PROTECTED]
  ' | `   Sysadmin Support and Training  |        (800) 938-4078


Reply via email to