On Mon, Dec 12, 2011 at 12:37 PM, Kevin A. McGrail <[email protected]> wrote: > >> My proposal that you replied to does not suggest delay of Mailspike >> inclusion. I am only suggesting letting the scores balance naturally >> then adjusting it manually afterward. I did something similar when we >> included PSBL in 3.3.0. Not difficult. > > So specifically, we are talking about: > > Commenting the new rules in 50_scores.cf, adding a version block on > 20_mailspike.cf in your sandbox, removing the nopublish and then what?
I'll do this later today. > > Don't we already have masscheck scoring on the rules or does the nopublish > disable the statistics you want to see? No, masscheck is not supposed to autoscore anything that is nopublish. IIRC, sa-update rulesets were not supposed to change the "base" rules at all, only auto-promote new rules added since the previous major release? Kevin, have time to talk on the phone sometime this week? I think there is a gap of understanding here that we can clear up on the phone. > > In short, what other steps are you proposing in the immediate future on the > MAILSPIKE scores to make them live for trunk/3.4.0? In general: * Yes, we include some placeholder rule for now. If my understanding is correct, if we add it as if it were a "base" rule the auto-promotion mechanism wont change its score. * BTW, why did you include L2? L2 was *never* tested in masscheck. The years of top-tier performance were confirmed for only L3-L5. Same story regarding H2. Please, let's not change things at the last minute before 3.4? * Set the scores to be conservative (see AXB's post) prior to GA balancing. Let ZBI and L's float in GA rescoring. Then adjust L's to be linear and increase the H's conservatively after we look at the GA results and do some quick fp-fn tests across the entire set. if (version >= 3.400000) #MAILSPIKE RBL ENABLED FOR SA3.4 and above - BUG 6400 # FLOATING SCORES FOR GA - adjust after GA to make L3 to L5 linear score RCVD_IN_MSPIKE_ZBI 2.7 score RCVD_IN_MSPIKE_L5 2.5 score RCVD_IN_MSPIKE_L4 1.7 score RCVD_IN_MSPIKE_L3 0.9 # TEMPORARILY FIXED SCORES - adjust these higher after we look at the GA results # (pending discussion: none of the whitelists should effect the blacklist balancing as they are orthogonal.) # I suspect these should be something like H3 = 0.5, H4 = 1.0, H5 = 2.0, alongside big reductions in IADB and DNSWL. score RCVD_IN_MSPIKE_H3 -0.01 score RCVD_IN_MSPIKE_H4 -0.01 score RCVD_IN_MSPIKE_H5 -0.01 ## These are informational rules, useful in statistical comparisons # FIXED SCORES - leave these scores this way for release score RCVD_IN_MSPIKE_BL 0.01 score RCVD_IN_MSPIKE_WL -0.01 endif
