Closed Bug 188353 Opened 22 years ago Closed 19 years ago

access to mail server with dynamic IP works only until its address changes

Categories

(MailNews Core :: Networking, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: tabt, Assigned: mscott)

References

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:1.2) Gecko/20021126 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:1.2) Gecko/20021126 Probably Mozilla caches the resolved IP address (at least for too long) of the mail server (in my case secure IMAP at port 993) which causes it to always connect to the IP address it resolved the first time it accesses the server. Once the server changes its IP address (dyndns address used for DSL line) Mozilla never updates the IP and therefore can no longer connect. Only way to access it again: restart Mozilla completely. Closing of MailNews window does not suffice. Reproducible: Always Steps to Reproduce: 1. add mail account with dyndns server (preferably IMAP or secure IMAP) 2. access the server (it works) 3. wait until server changes IP address 3a. maybe connect to the server via SSH or so to make sure the host OS noticed the change 4. access mail account again (while having tcpdump running to examine the problem) 5. Mozilla still uses old IP address (even after days...) Actual Results: "Mail server does not respond" - no wonder if it uses the wrong IP... Expected Results: Use resolved IP addresses only as long as valid or do not cache at all.
as workaround (dunno if it works) you can switch to Online-> Offline-> Online (the small icon on the left side of the lock in the status bar)
dup 109313? or some of the other DNS bugs bug 61683
Related, probably same root cause: bug 167832
Blocks: 61683
Product: MailNews → Core
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/
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.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.