On Fri, 2008-09-26 at 10:35 -0700, RobertH wrote: > > > > > No, it boils down to the attitude in your e-mail - "Why didn't the > > SpamAssassin benefactors do their job better". I for one am impressed > > with their willingness to provide such a useful piece of software, and > > maintain it. But most of them have real jobs, and don't spend every > > waking moment trolling the webpages of obscure rbl'slooking for notices > > that things are borked. > > > > Dan > > The OP had a good point regardless of whether anyone sees it as an attack on > SA folks or whatever. > > When people design and build a system(s) of any type, there should be checks > and balances designed in that can check and see if sub parts of the systems > (or called by the system(s)) are broken or disappeared or what have you so > that allowances / changes can be made in a quicker, more orderly fashion.
right, and they run a test every night to ensure that the rules still --lint. And RCVD_IN_DSBL was working - the name servers responded quickly, and there were no false positives. just lots of false negatives ;-) If you went to the dsbl.org site to see what happened, they lost a disk drive in May. The master database, with all of the removal requests, was lost. They stated, back in May, that they thought it was going to be a temporary state of affairs. Since SpamAssassin still wasn't throwing any errors, the rules were left there so that when they came back to life, there would be no changes required. Recently they posted that they were simply giving up, for good. someone noticed and mentioned it on the user list. another person saw that and filed a bug. Then one of the developers made the change, pushed out the update, and closed the bug. I don't see that there is any crisis here that needs to be solved. > Even if the checking mechanisms are external to the main system, maybe > something should be written and tested??? They run a bunch of tests every night, and are notified by nagios if the tests fail. lurk on the -dev mail list every now and again and you'll see it. -- Daniel J McDonald, CCIE #2495, CISSP #78281, CNX Austin Energy http://www.austinenergy.com
signature.asc
Description: This is a digitally signed message part