On 11/21/2017 03:56 AM, A. Schulze wrote:
Kevin A. McGrail:
If you are checking the SpamAssassin updates more than 2x a day,
expect to be blocked in the very near future. We have people
checking literally every minute and we only release rules currently 1x
per day. There is no need to check this often!
I use sa-update to update all channels I use. From what I've seen on
"sa-update --debug" the default is to test an dns-record.
( "dig 1.4.3.updates.spamassassin.org. txt" for the main channel )
If the DNS answer indicate the same version no HTTP requests are done.
So it SHOULD not hurt to call sa-update more frequently UNLESS one have
specific scripts that directly connect to the updateservers via http.
is this assumtion right?
Andreas
You are correct. I haven't dug into the code to verify but it appears
that 3.4.x sa-update does use the DNS TXT record to know when to
download so it doesn't hurt anything to run this version hourly.
The major offenders are sa-update 3.3.x and generic curl clients based
on the user agent in the logs running from every minute to every 15
minutes and blindly pulling down the same rulesets over and over.
Not sure why those 3.3.x don't just upgrade anyway since it's not that
difficult to do. At some point in the future the older 3.3.x will be
considered end-of-life and no ruleset updates for them. I am pretty
sure they are already considered unsupported so if a ruleset
incompatibility pops up, that could be the end of updates for those
ancient versions.
--
David Jones
