fwiw, I'm pretty +1 on the idea. I was a bit skeptical of these rules at the start (concerns about the automated nature more than anything else), but things seem to be going pretty well.
I'd like to see several people w/ large corpus publish their own similar channels. The "build it and they will come" aspect of sa-update didn't really happen, unfortunately, so maybe helping to both create and then publish the rules would be helpful. :) Hrm. I wonder if there'd be an easy way to automate publication for developers. Something like sandbox/user/channel, where updates are automatically packaged and the channel updated. (then we could do something like user.updates.spamassassin.org) Not sure about how to deal with the signing of the tarball, but... On Wed, Dec 31, 2008 at 11:52:22AM +0000, Justin Mason wrote: > listen, I've been generating the JM_SOUGHT and JM_SOUGHT_FRAUD rules as an > "unofficial" project for a while. However, I'd like to move them into the > "official" Apache SpamAssassin project aegis. > > Basically, they're automatically-generated. Review takes place > post-publishing, if any. This means there's potential they could cause > lots of false positives somehow, although to date over the past couple of > years, they haven't. > > The main reason I kept them away from "official" status is the danger of > them going haywire and causing FPs. > > This definitely isn't compatible with publishing as part of the "main" > ruleset, but it could be an optional add-on sa-update channel -- > basically, the same way it is now, but at a > sought.rules.spamassassin.apache.org name, instead of > sought.rules.yerp.org, with the same understanding of potential scariness > -- "this is an official product, but use with care". > > WDYT? -- Randomly Selected Tagline: Professor: Doomsday device? Ah, now the ball's in Farnsworth's court. I suppose I could part with one and still be feared.
pgpFNCxzEKfIo.pgp
Description: PGP signature
