https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6644
--- Comment #17 from AXB <[email protected]> 2011-11-01 16:22:58 UTC --- (In reply to comment #16) > (In reply to comment #15) > > (In reply to comment #14) > > > So we have a third possibility which is just DNS related possibly. > > > > I like that one. Any objections to it? > > I'm very wary of breaking things and need people who are intimately familiar > with the way mass-check works and sa-update works to weigh in. Eventually, > I'll vote +1 if needed because you have to break eggs to make omelets. But > after 9 weeks of no mass check (thanks for your idea on time again, BTW), I'm > more than a bit reticent to just jump in and break it again. while I understand your "fear", it may be better to risk now and have it working and if it doesn't atm, it won't do as much harm as it would shortly after a release. Postponing just means a long wait before we know the outcome.. +1 to break eggs now :) The change has to be well documented so a rollback doesn't become an ordeal. -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
