Re: [SAtalk] spam flag NO despite high score

2003-07-31 Thread Kelson Vibber
[EMAIL PROTECTED] wrote: (1) From: Tail Wagging Offers News Letter <[EMAIL PROTECTED]> X-Spam-Score: 5 X-Spam-Level: * (5) X-Spam-Flag: NO X-Scanned-By: MIMEDefang 2.28 (www.roaringpenguin.com/mimedefang) My spam threshold is set to 1.5. This email should have been flagged

Re: [SAtalk] spam flag NO despite high score

2003-07-30 Thread alan premselaar
Luiz, (B (BOn 2003$BG/(B July$B7n(B 31$BF|(B Thursday, at 11:01 AM, Luiz L Souza wrote: (B (B> Thanks for the prompt reply. (B> Here are two examples of spamassassin info from emails I received: (B> (B> (1) From: Tail Wagging Offers News Letter (B> <[EMAIL PROTECTED]> (B> X-Sp

Re: [SAtalk] spam flag NO despite high score

2003-07-30 Thread Matt Kettler
Hmm.. I'm not really familiar with mimedefang, and the output it's put there isn't very informative. My first question would be how did you set your spam threshold to 1.5? What exact configuration file and command did you use? My next question would be can you generate a X-Spam-Status header,

Re: [SAtalk] spam flag NO despite high score

2003-07-30 Thread Luiz L Souza
PROTECTED]>; <[EMAIL PROTECTED]> Sent: Wednesday, July 30, 2003 1:17 PM Subject: Re: [SAtalk] spam flag NO despite high score > At 11:01 AM 7/30/2003 -0400, Luiz L Souza wrote: > >My mail provider uses spamassassin. I have set the spam threshold > >to a low value, 1.5, and added

Re: [SAtalk] spam flag NO despite high score

2003-07-30 Thread Matt Kettler
At 11:01 AM 7/30/2003 -0400, Luiz L Souza wrote: My mail provider uses spamassassin. I have set the spam threshold to a low value, 1.5, and added some entries to my 'allow' and 'deny' lists in order to reduce the number of spam that gets through spamassassin. Most of the spam is correctly identif

[SAtalk] spam flag NO despite high score

2003-07-30 Thread Luiz L Souza
My mail provider uses spamassassin.  I have set the spam threshold to a low value, 1.5, and added some entries to my 'allow' and 'deny' lists in order to reduce the number of spam that gets through spamassassin.  Most of the spam is correctly identified. The problem is that some emails are f