> http://bugzilla.spamassassin.org/show_bug.cgi?id=2853 > [EMAIL PROTECTED] changed:
> I intend to re-write most of the masses/ stuff so that it's easier to > use for end users. Namely, I intend to rewrite perceptron in perl, and > fix up the other scripts so they don't use temp files all the time > (there's a lot more reading and writing than i think is necessary). Thank you! > If anyone can think of some pitfalls I need to think about, I'd > appreciate it if you could let me know. Or, if you think what I'm doing > is useless... tell me. My goal is to create a spamassassin-tools/-utils > package with this sort of thing so people can rescore themselves. Useful, appreciated, and very beneficial to those of us interested and (otherwise) able to run against our own corpi. I've managed to make mass-check work for me, but it's a multiple step process, with a structure I had to create by trial and error. Improvements will make it much easier to move from version to version. > One of the biggest weaknesses of SpamAssassin is that scores are hard > to determine and get stale quickly after a release. By allowing users > to make their own scores, we can prolong the "shelf life" of older > version of SpamAssassin. This, combined with plugins should be quite > useful to users. Excellent! As one of the contributors to the Rules Emporium, I know that one of our biggest challenges is the determination of workable first-pass scores. Accepting that people may need to change the scores we develop as they adopt our rules and/or rule sets, it's still important that we score high enough to show whether the rules are useful, and low enough to avoid FPs. Allowing automatic realignment of scores will be a big help to this process, and to the accuracy of Spam Assassin itself! Bob Menschel
