The real question (which I should admittedly know the answer to) is whether it is safe to unleash this. I've been hosting it on my own sa-update channel for all that time merely because SA rules updates aren't prompt enough to host directly. Is that still the case?
I do not think these rules are unsafe to run in production (the CIDR8 rules are unsafe in theory and I wouldn't want those scored directly even though it has been safe in practice). I've got some (safer) downstream remixes of these rules that I'll push up if the main updates.spamassassin.org mechanism is safe. (PS, I'm at MAAWG <https://www.maawg.org/> this week and RSA <http://www.rsaconference.com/> next week if anybody wants to network in person.) On 02/18/2014 01:19 AM, Axb wrote: > Could we PLEASE loose this rules file? > > /trunk/rulesrc/sandbox/khopesh/20_khop_sc_bug_6114.cf > > We've been masschecking it for 4 years and it's tflags nopublish and > pretty dangerous to use in production if you have more than a "man & > his dog" setup. > > I see no reason to throw cycles/resources to masscheck such rules for > years. > > Thx >
signature.asc
Description: OpenPGP digital signature
