https://issues.apache.org/SpamAssassin/show_bug.cgi?id=7070
Kevin A. McGrail <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |[email protected] Resolution|--- |INVALID --- Comment #3 from Kevin A. McGrail <[email protected]> --- Not sure this is accurate. The default Net::DNS::Resolver timeout is 2 minutes. The only entry I see for DNS::Resolver::Timeout is hard coded to 3 seconds in lib/Mail/SpamAssassin/DnsResolver.pm $res->tcp_timeout(3); # timeout of 3 seconds only $res->udp_timeout(3); # timeout of 3 seconds only But async loop uses the rbl_timeout but the config setting can be overridden by the application specified setting. Overall in situations with known bad DNS issues, I have no idea what settings are needed or would resolve your issue. There are a lot of safety valves and optimizations involved in these loops and getting invalid answers can definitely start short circuiting things. Are you getting timeouts or are you getting invalid answers or a combination of both? Do you see debug output saying: async: escaping: lost or timed out requests or responses? My guess is you do because the DNS system is realizing something is bonkers and short-circuiting to prevent loops. In the end, your feature request is very broad and spans too many plugins. Start one by one and give debug output for an email that fails. But do so on a system with known working DNS. If you have known, non-working or wonky DNS, you should run without network tests. If you have SLOW dns, that's a different issue and something timeouts could handle... -- You are receiving this mail because: You are the assignee for the bug.
