Harry Putnam wrote: HP> Subject: *****SPAM***** Cron <root@reader> /usr/sbin/netdate time.jtan.com HP> [...] HP> X-Spam-Status: No, hits=-97.9 required=2.0 tests=FROM_MALFORMED,\ HP> TO_MALFORMED,SUPERLONG_LINE,USER_IN_WHITELIST version=2.20 HP> X-Spam-Level: HP> HP> So I guess whitelisting doesn't work quite the way I expected it HP> would. Somehow I assumed, all the earmarking stuff would get turned HP> off.
SA won't modify the subject line if the score is below the threshold (including -ve). I'm guessing you piped a message which had already been marked up back through SA again, and that the "****SPAM*****" was in the message passed in to SA. HP> Then using the above mentioned CRON rule and score of -100, the same HP> message gets sent through to the default spool but contains this: HP> HP> Subject: *****SPAM***** Cron <root@reader> /usr/sbin/netdate time.jtan.com HP> [...] HP> X-Spam-Status: No, hits=-97.9 required=2.0 tests=CRON,FROM_MALFORMED,\ HP> TO_MALFORMED,SUPERLONG_LINE version=2.20 HP> X-Spam-Level: HP> HP> Shouldn't the subject `spam' label be omitted if the score is below HP> the set value.? It is omitted -- but it's not deleted if it's already there. You're undoubtedly passing an already-marked-up message into SA. C _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
