https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6155
--- Comment #72 from Mark Martinec <[email protected]> 2009-10-06 12:33:09 PDT --- > The longer you wait, more of the logs ID's will no longer match the mail > boxes. The messages whose results are submitted to rescoring are supposed to be preserved, at least until the rescoring runs are done. > BTW, did you do the things written in Comment #38? Not yet, will do in my next iteration. It takes a couple of hours. The JM_SOUGHT results I kept on purpose for now, wondering what their scores would be. On the next round I can just force them to zero, I believe this is equivalent to removing them from the logs. In the first round I got: score JM_SOUGHT_FRAUD_1 2.105 score JM_SOUGHT_FRAUD_2 2.318 score JM_SOUGHT_FRAUD_3 3.270 > So scoring PSBL might be more complicated than this. > > * RCVD_IN_PSBL_2WEEKS was never meant to be published as a run-time rule. It > is valuable in measuring PSBL in masschecks. > * It seems that PSBL is not set to allow reuse? > * PSBL as measured in the rescore masscheck was deep parsing, while we > subsequently agreed to change it to lastexternal. I did the translations from Comment #38 now on the RCVD_IN_PSBL*, will get into the next approximation. > What should we do? There seem to be some other rules in the works, so I'd say let's just finish up whatever was frozen with a call for rescoring results, publish that as beta-1, then examine what we got, polish it, and to another rescoring run before the final release. It's not too bad to just fix some scores manually, we're doing it also for BAYES, SPF, etc. ========== Here is now the first homework, the following were reported as false positives on my last completed attempt. Please check if these are really ham messages (I already checked my two entries, and they are): ham-bayes-net-hege.log /data/sa/h/3/36f18b49dd8ce2ce70586c67eeb780fd /data/sa/h/0/0270ee166042abd0aa94cbdda855400c /data/sa/h/9/9eb11730050002add51ecdc6ed25343d /data/sa/h/5/5dfa06864bb3021674768e8af372a6c9 /data/sa/h/4/4214ade1e7e177f0453c5f1cc98c8b42 ham-bayes-net-bluestreak.log ../../aaa_ham/2009-07_HAM_721117.0 ../../aaa_ham/2009-06_HAM_602375.0 ../../aaa_ham/2009-06_HAM_609153.0 ../../aaa_ham/2009-06_HAM_623012.0 ../../aaa_ham/2009-06_HAM_622736.0 ../../aaa_ham/2009-08_HAM_814010.0 ham-bayes-net-dos.log /home/dos/SA-corpus/ham/leah/ INBOX-Inbox-2007/1195695047.P9700Q22.dilbert.dostech.net:2,S /home/dos/SA-corpus/ham/leah/ INBOX-Inbox-2007/1196258008.P18803Q16.dilbert.dostech.net:2,S /home/dos/SA-corpus/ham/leah/ INBOX-Inbox-2007/1199765108.P20983Q90.dilbert.dostech.net:2,RS ham-bayes-net-jm.log /local/cor/recent/ham/priv.radish.jmason.org.200808310000.mbox.160968 /local/cor/recent/ham/priv.wall.200809081400.mbox.1677188 /local/cor/recent/ham/priv.20050914/126599 ham-bayes-net-mmartinec.log ham/uYUQM2RmF9I0 ham/p+KSEyzZTPOw -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
