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 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 SA TWICE... > > The first time, it scores spam, gets re-written, encapsulated, etc. > > The second time, the headers are different because of encapsulation. This > lowers the score, making it no longer regarded as spam, and the > X-Spam-Status header gets over-written with the current state of "No" > > > ---------------------------------------------------------------- Università di Catania - C.E.A. Servizio di Posta Elettronica http://www.cea.unict.it ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id78&alloc_id371&op=click _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
