OK Guys,
you are right, just a procmail configuration error...
The message was read twice... and the most of the time SA didn't recognize it as
SPAM (and it was right :)
Tnx
Luca
Scrive Matt Kettler <[EMAIL PROTECTED]>:
> At 03:18 PM 12/9/03 +0100, Luca Palazzo wrote:
> >i'm experiencing a strab
At 03:18 PM 12/9/03 +0100, Luca Palazzo wrote:
i'm experiencing a strabge problem using Spamassassassin (2.60)..
It recognizes a mail as spam, rewrite message (using the rule from
safe_report 1) but adds its header with wrong X-Spam-Status..
This is typicaly what happens when you run mail through S
> X-Spam-Status: No, hits=1.5 required=5.0
> tests=BAYES_50,BIZ_TLD,CASHCASHCASH,
> DNS_FROM_RFCI_DSN,HTML_FONTCOLOR_BLUE,HTML_FONT_BIG,
> HTML_FONT_INVISIBLE,HTML_MESSAGE autolearn=no version=2.60
The message was not spammy enough to trigger SA. Your bayes gave it a
neutral value
