https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6400
--- Comment #4 from Warren Togami <[email protected]> 2011-10-13 19:55:55 UTC --- Adding Mailspike is not a simple matter of adding Mailspike. In order to properly include Mailspike we need a full rescore run, as its addition will effect the score of other rules. I suspect we have two problems with a full rescoring: * I fear that the quality and quantity of our corpus has diminished in the past year. I personally haven't been manually sorting mail in a LONG time. https://fedorahosted.org/auto-mass-check/ João, it would be very helpful if you folks could join the nightly masscheck with a variety of ham and a random sample of spam. * masscheck of old and new network rules like DNSBL's is not an Apples to Apples comparison. For old rules like RCVD_IN_PSBL we rely on --reuse of spamassassin tags in the corpora. For new rules, tags are typically missing from corpora, so we are testing old mail against a real-time blacklist. This is not good, as the old DNSBL reflects actual performance while the new blacklist does not. I don't have a solution for this other than all masscheck participants having added MSPIKE rules from a year ago. -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
