At 08:44 7/12/2002 -0700 Steven Stringham wrote: >I am looking to filter my entire domain's email through SpamAssassin. >Sendmail + spamass-milter. > >I am however, concerned with letting valid emails through (we are a Law >Firm). If I were to kill valid messages, there would be real problems. > >The solution: Change the way it reports on the subject line, and let it >all through. > >In PerMsgStatus.pm (which is where the subject line is changed) I am >adding two additional variables: _SPLV_ and _SPLG_. > >Spamlevel = hits/threshold (so hits of 15 with threshold of 10 = 1.5, >hits of 15 with threshold of 5 = 3, hits of 4, threshold of 5 = 0.8). > >I then have a table (Using an if statement): >1.2 <= Possible >1.7 <= Likely >1.7 > Definitely.
Erm. Sorry, if your threshold is 15 then anything over .333 is likely spam and anything over .666 is certainly spam. If your threshold is 3 then anything over 1.5 is likely spam and anything over 3.33 is certainly spam. >I have changed my PerMsgStatus.pm already to implement this. But, I >have two questions for the community: >1) What is your reaction to this approach (is it good, bad, etc.)? >Would it be good to implement in the core product as an option? Use the X-Spam-Level header instead. X-Spam-Level: ***** <-- Likely spam X-Spam-Level: ********** <-- certainly Spam ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Gadgets, caffeine, t-shirts, fun stuff. http://thinkgeek.com/sf _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
