You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spamassassin.apache.org by bu...@bugzilla.spamassassin.org on 2005/03/24 15:49:44 UTC
[Bug 4222] New: DNSBL fails if primary nameserver unavailable
http://bugzilla.spamassassin.org/show_bug.cgi?id=4222
Summary: DNSBL fails if primary nameserver unavailable
Product: Spamassassin
Version: 3.0.2
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P3
Component: Plugins
AssignedTo: dev@spamassassin.apache.org
ReportedBy: maddenj+spamassassin@skynet.ie
I have noticed a few times that the DNSBL tests fail if our primary nameserver
is down. dig et al. work fine from the same machine, using the backup nameserver.
Relevant sections from spamassassin -D --lint
root@hal:~# grep NS SA-D-lint
debug: diag: module installed: Net::DNS, version 0.48
debug: plugin: loading Mail::SpamAssassin::Plugin::URIDNSBL from @INC
debug: plugin: registered Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x8582fcc)
debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x8582fcc) implements
'parse_config'
debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x8582fcc) implements
'parsed_metadata'
debug: is Net::DNS::Resolver available? yes
debug: Net::DNS version: 0.48
debug: looking up NS for 'kernel.org'
debug: NS lookup of kernel.org succeeded => Dns available (set dns_available to
hardcode)
debug: is DNS available? 1
debug: URIDNSBL: domains to query:
debug: registering glue method for check_uridnsbl
(Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x8582fcc))
debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x8582fcc) implements
'check_tick'
debug: DNS: timeout for ahbl after 15 seconds
debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x8582fcc) implements
'check_post_dnsbl'
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
[Bug 4222] DNSBL fails if primary nameserver unavailable
Posted by bu...@bugzilla.spamassassin.org.
http://bugzilla.spamassassin.org/show_bug.cgi?id=4222
------- Additional Comments From sidney@sidney.com 2005-03-24 08:10 -------
This behavior is inherent in the way DNS queries are being done, using the
bgsend method of Net::DNS::Resolver. SpamAssassin sends out DNS queries in the
background to the first nameserver in the list, then collects results as they
come in after processing other rules. There is no provision for determining that
the first nameserver has failed and then trying another, as the send method
would do.
I will leave it to others to decide if this behavior is a bug in SpamAssassin or
just a tradeoff for being able to background the queries.
If the latter, it does mean that DNS tests will only work if the host's primary
nameserver is operational even it is configured to list multiple nameservers.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
[Bug 4222] DNSBL fails if primary nameserver unavailable
Posted by bu...@bugzilla.spamassassin.org.
http://bugzilla.spamassassin.org/show_bug.cgi?id=4222
maddenj+spamassassin@skynet.ie changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
------- Additional Comments From maddenj+spamassassin@skynet.ie 2005-05-01 09:16 -------
This isn't exactly "fixed", but it's being worked on as part of a couple of
other bugs, so there's no need to leave this bug open. Can be reopened in
future, if this problem is still around.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
[Bug 4222] DNSBL fails if primary nameserver unavailable
Posted by bu...@bugzilla.spamassassin.org.
http://bugzilla.spamassassin.org/show_bug.cgi?id=4222
------- Additional Comments From sidney@sidney.com 2005-05-01 09:27 -------
Actually this really is fixed. I forgot about this bug when I worked on bug
4278. I should have linked them somehow. Another change turned the problem of
DNS not working when the primary nameserver is down into a hang when the primary
server is down. In the course of fixing that I removed the requirement that the
primary nameserver be up when SpamAssassin starts.
It is still the case that if the nameserver being used goes down while
SpamAssassin is running, then SA will not switch to the next nameserver in the
list. The code I added only looks through the list for a working nameserver at
initialization time.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.