https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6510
--- Comment #8 from Daryl C. W. O'Shea <spamassas...@dostech.ca> 2010-11-06 20:57:43 UTC --- [...@dev new-rule-score-gen]$ svn ci -m "bug 6510: temporarily force all generated scores to be non-zero" Sending new-rule-score-gen/do-nightly-rescore-example Sending new-rule-score-gen/merge-scoresets Transmitting file data .. Committed revision 1032191. [...@dev new-rule-score-gen]$ I've temporarily added code to force all generated scores to be non-zero and mark the scores-set# files to indicate that the score was changed from 0.000 to 0.0001 with a "# forced non-zero" notation. I've discovered that most, but not all, of the rules that have problems have been promoted due to "tflags publish"... which means they weren't necessarily selected for promotion due to mass-check results (which may explain their low or zero scores). I've also found that the script generate-new-scores checks out a copy of tags/spamassassin_release_3_2_0_rc_2/rules from the svn repos. I'm not sure yet what it uses it for and what it should use now that we've split rules out of the base release. -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
