User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040514 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040514 The mail client periodically loses its DNS settings after operating fine up to that point. It typically gives an error on send. It comes up with "cannot resolve localhost". Attempting to get new messages comes up with a similar error for resolving the mail server. I have a single POP3 acct and several IMAP accts configured. The connection is via a reliable LAN. There are no networking problems and certainly no DNS problems or routing problems in the environment. This is definitely internal to mozilla. The browser also cannot resolve URLs when this bug occurs. Mozilla will also not close down the mail client as it can no longer disconnect from the mail server. The only way to exit mozilla is to KILL -HUP the mozilla process. It then exits smoothly and works fine on startup again. Reproducible: Sometimes Steps to Reproduce: 1. Open mail 2. Use mail to send/receive for a while. This can be as much as 1/2 day unfortunately Actual Results: System can no longer resolve DNS. Expected Results: Continued to resolve DNS No crash, core dumps or any error message other that the popup saying that it cannot resolve the URL (in browser) or mail server (in mail client).
Do you have any antivirus running on your system? I'm terribly sorry, I can't recall the bug number, but I'm sure there's an AV that changes the server settings of several mail clients to "localhost".
No antivirus running, no. It's a linux box so thankfully not subject to the onslaught that windows users have! The system loses DNS in the browser as well. All of mozilla fails to resolve when this kicks in although invariably it happens after I have been using mail (then again, I use mail many times more than I browse so this may be misleading). I wish that I could provide an accurate means of reproducing this problem. I am attempting to, but so far it just seems "random" which from a software correction point of view isn't what we want!
Something else that may help: This problem only started when I upgraded to the latest version of Mozilla. It wasn't there before.
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/
Firefox does not suffer from this problem, only Thunderbird. All the latest versions of Thunderbird has this problem too.
I think that probably why no-one else has confirmed this is that I use the thing a lot on the move through 3G wireless which drops off and then reconnects... it keeps everything alive and firefox, ssh, all the rest works... but thunderbird just never refreshes DNS. I am now convinced that this is a DNS refresh problem in thunderbird.
sorry for the spam. making bugzilla reflect reality as I'm not working on these bugs. filter on FOOBARCHEESE to remove these in bulk.
Assignee: sspitzer → nobody
WFM per reporter "Thunderbird 220.127.116.11 (X11/20070728)"
Status: UNCONFIRMED → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → WORKSFORME
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.