296196 - Thunderbird does not resolve hostnames (/etc/hosts and DNS)

Status: RESOLVED EXPIRED

(Thunderbird :: General, defect)

Description

[Hartmut Goebel]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2) Gecko/20040804
Build Identifier: Thunderbird 1.0.2 version 1.0.2-3mdk (20050322)

When fetching mails, Thunderbird does not resolve hostnames. This is very
obscure! The status-bar says "Looking up ..." and an alert pops up "Failed
connecting to ...".

As soon as I change the hostname to the IPv4-Addresse, it works.

I debugged this:
1) With a hostname in /etc/hosts
   * strace shows access to /etc/hosts
   * problem occurs
2) With a hostname in DNS
   * tcpdump does not show an DNS-Lookup
   * problem occurs


Reproducible: Always

Comment 1

[Jo Hermans]

This sounds a problem with your resolver-library, the connection with your DNS
lookup-server, or the DNS-server of that host. Is Mozilla (or Firefox) running
allright ? Can you do a nslookup or dig ?

Comment 2

[Hartmut Goebel]

(In reply to comment #1)

Yes, this sounds like a problem with then resolver-library,. But everything else
works alright: Mozilla, ping, ping6, telnet, ssh, dig, host, getent hosts, etc.
All the utilities can resolve the names.

Comment 3

[Hartmut Goebel]

I figured this out: It's an incompatibility with diverent versions of libnspr4
and libnss3.

I had mozilla 1.7.1 (or so) installed, which included libnspr4-1.7.1 and
libnss3-1.7.1. When installing thunderbird using Mandrake's rpms, the libs did
not get updated. The problem occured.

When I updated Mozilla to 1.7.6, these libs got updates to 1.0.4 and the problem
vanished.

Thus there are two problems: 1) a packaging problem at Mandrake and 2) an
incompatibility in these libs. I will report no.1, it's up to you if and how to
handle no.2

Regards

Comment 4

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 5

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.