http://bugzilla.spamassassin.org/show_bug.cgi?id=3997





------- Additional Comments From [EMAIL PROTECTED]  2005-01-19 00:29 -------
Loren,

Each DNS query creates a new IO::Socket object which is put into an array object
which is put into a hash table in the DNS::Resolver object, keyed by the host
name and DNS record type that are being queried for. Before sending a query,
there is a check that there is nothing in the hash table for that key, so there
are not any redundant queries. Other elements of the array object that contains
the IO::Socket are set to indicate the tests that this qery is for.

The items in the hash table are iterated through looking for any for which the
IO::Socket object is ready to be read. When it is read, the results are
processed according to the rule information that is in the array object with it.

That should prevent mixups from happening. But obviously mixups are happening.

Vance, as I posted in the comment after the one where I asked you to try a test,
I realized that your comment #23 already includes the information I was hoping
to gather from the test, so no problem about your not being able to reproduce
the prolem anymore.

Here's a question for anyone who is looking at the code. Vance's comment #23
seems to imply that the results from a query to the system DNS of the mail
server host name were retrieved instead of the query to the SURBL. But look at
the code in Dns.pm in sub process_dnsbl_result where it says

  next if ($answer->type ne 'A' && $answer->type ne 'TXT');
  # skip any A record that isn't on 127/8
  next if ($answer->type eq 'A' && $answer->rdatastr !~ /^127\./);

Shouldn't that prevent what Vance's comment #23 debug log output shows even if
the wrong query's results were associated with a SURBL lookup? How could a
non-127 ip address get passed in to the URIRBL processing? The answer to that
may provide a clue to the bug. So far I don't see a path through the code that
could do that.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Reply via email to