https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6876
Kevin A. McGrail <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #2 from Kevin A. McGrail <[email protected]> --- (In reply to comment #1) > I've suggested it before and I'll suggest it again: if the volume of > sa-update downloads is larger than we're comfortable supporting with > available infrastructure, then the config files should try using the > official mirror servers. This is simple, transparent, automatically > distributed, retrieves from a cache server topologically near the requesting > host, and is (in my experience) reliable. It also makes updates robust in > the face of temporary unavailablility of the mirror servers. > > I'm not offering this as an alternative to code changes that rate-limit > sa-update download attempts, but as anothar approach to use along with such > limits to manage load. I believe this issue is that these are unnecessary checks. For example bug 6655. If someone is checking for updates, that just hits DNS and is minor. But we have systems for no known reason checking repeatedly for updates. While I agree with you John, the reality is that replacing and keeping the existing infrastructure running for the entire project is time consuming. I want to try and focus on publishing code rather than changing/improving infrastructure as much as possible. Regards, KAM -- You are receiving this mail because: You are the assignee for the bug.
