-t always generates a report -- it's sort of a debugging option. -P won't generate a report unless the threshold is exceeded.
C Simon Detheridge wrote: SD> Hi, SD> SD> I was running spamassassin fine for a couple of days, and then noticed SD> stupidly large numbers of emails getting tagged as spam, regardless of their SD> score. I tried running "spamassassin -t < sample-nonspam.txt" and it SD> generated the following: SD> SD> SPAM: -------------------- Start SpamAssassin results ---------------------- SD> SPAM: This mail is probably spam. The original message has been altered SD> SPAM: so you can recognise or block similar unwanted mail in future. SD> SPAM: See http://spamassassin.org/tag/ for more details. SD> SPAM: SD> SPAM: Content analysis details: (-2.8 hits, 8 required) SD> SPAM: Hit! (-1.2 points) BODY: Contains 'G.a.p.p.y-T.e.x.t' SD> SPAM: Hit! (0.5 points) BODY: A WHOLE LINE OF YELLING DETECTED SD> SPAM: Hit! (-2.1 points) BODY: Contains a PGP-signed message SD> SPAM: SD> SPAM: -------------------- End of SpamAssassin results --------------------- SD> SD> So, it says "this mail is probably spam" even though it scored -2.8!! _______________________________________________________________ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
