Duncan Findlay writes: > On Tue, Mar 13, 2007 at 10:32:20AM +0000, Justin Mason wrote: > > > There seem to be a lot of... issues... relating to promoting rules, > > > for example, there are rules that were mass-checked under one name and > > > then promoted (I guess I need to check out the exact revision of > > > rulesrc before running any scoring scripts?). Or maybe I just don't > > > understand how it all works. > > > I suspect the latter ;) > > Read the documentation on the wiki: I've kept it up to date for > > the 3.2.0 mass-checks, so it's canonical. > > > http://wiki.apache.org/spamassassin/RescoreMassCheck > > > Basically, you have to keep a single "rules/active.list" file for the > > entire process, and ensure you don't overwrite it with an "svn update" > > halfway through. (see '4.3 resync to mcsnapshot rules list') > > Yeah, sorry I didn't end up reading that the first time round. Guess I > wanted to go off memory... Thanks for the link. > > Anyways, I'm still getting some wierdness: > > make tmp/ranges.data > > spewed a whole lot of errors about tests like T_FRT_CONTACT no longer > existing -- it exists in the mass-check logs, but I don't see it in > the rules directory. Is this just a matter of mass-checkers checking > against 70_sandbox.cf though they shouldn't?
yep, exactly. (well, there's nothing saying they shouldn't -- it's just assumed that the GA/perceptron step will ignore the hits on rules from the sandbox file, or any other rules that don't exist in the std ruleset). --j.
