https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8193
--- Comment #32 from Sidney Markowitz <sid...@sidney.com> --- I'm considering setting in a file for rule updates dns_block_time 3600 instead of leaving it set to the default 300 seconds. Reasons for: * If a dnsbl does return a BLOCKED code, then it is the case that the dnsbl is blocking the nameserver that SpamAssassin is using, and that is not likely to change soon. Trying again 12 times in an hour is not likely to get different results than trying again once an hour. * However, trying more often increases the load on the dnsbl server from poorly configured SpamAssassin installations, for example those relying on a public access nameserver. This change will reduce the load caused by those installations to 1/12 of what it is now. * If the admin changes the configuration of their setup to fix the problem, it only takes a restart of SpamAssassin to reset it if they don't want to wait an hour. Does anyone have any reason not to do this? If we do this, what file is a good place to put it, given that it is not just for dnswl, but affects all the dnsbls that have a *BLOCKED rule? -- You are receiving this mail because: You are the assignee for the bug.
