https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6112
Summary: non-RBL DNS timeouts
Product: Spamassassin
Version: 3.2.5
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: P5
Component: Libraries
AssignedTo: [email protected]
ReportedBy: [email protected]
Hi there
I just had some casino spam get into my INBOX. Running "spamassassin -D" took
over *TWO MINUTES* and contains the lines:
[14167] dbg: async: completed in 136.660 s: NO_DNS_FOR_FROM, DNSBL-A,
dns:A:yapost.com
[14167] dbg: async: completed in 136.659 s: NO_DNS_FOR_FROM, DNSBL-MX,
dns:MX:yapost.com
[14167] dbg: async: timing: 136.659 . dns:MX:yapost.com
[14167] dbg: async: timing: 136.660 . dns:A:yapost.com
Sure enough, the "yapost" domain has 4 NS records and none are working.
Whatever is happening also seems to mean our DNS servers cannot cache this
failure - so every lookup goes through the entire cycle again and again (ie
yes, we have local cache DNS servers).
Shouldn't there be a SA option to set the max timeouts of "generic" DNS
lookups? (like dns_timeout 15).
More info. Net::DNS::Resolver defaults to 120s for TCP-based lookups, so I
thought that might be the cause. I edited Net/Resolver/Base.pm directly and
changed the default to "10" and it made no difference - so that's not it.
--
Configure bugmail:
https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
