Charles Gregory wrote on Fri, 1 Jan 2010 09:50:24 -0500 (EST): > I speak for the unguessable number of people who have installed a > 'standard' 3.2.x install with their linux variant, and don't monitor > closely, or watch this list. Some of them, we can hope, will have > 'sa-update' running in their nightly cron job. But will that do any good > if this 'patch' is not 'rushed' out as an sa-update for the current > version?
This bug is also hitting a good number of mail providers and has made it to the news. Makes for a good measurement for support at those companies. ;-) Where you still see this rule scoring there's obviously nobody paying attention on holidays ... > > You could release 3.3.0 today, but that would not benefit people who don't > know about the upgrade and leave it at 3.2.x..... > > And my pity to all those people who don't run sa-update..... :( Well, that's their problem. Really. It should be made clear that a well-tuned sa setup will put thru all the ham still as ham. Most of our customer's ham scores even after applying this rule between 1 and 3 and easily makes it thru. If a considerable amount of ham is turned to spam on a certain setup there's likely something wrong with that setup. Kai -- Kai Schätzl, Berlin, Germany Get your web at Conactive Internet Services: http://www.conactive.com
