Closed
Bug 81208
Opened 24 years ago
Closed 17 years ago
Connection establishment timeout: to a mail server
Categories
(MailNews Core :: Networking, defect, P3)
MailNews Core
Networking
Tracking
(Not tracked)
RESOLVED
WORKSFORME
mozilla1.2alpha
People
(Reporter: mpt, Unassigned)
References
Details
Build: 2001051504, Mac OS 9.1
To reproduce:
* Start Mozilla on a system which uses a dial-up connection.
* Disconnect from the Internet.
* Open the three-pane window.
* Click `Cancel' on the two dial-up networking progress windows which
appear.
* Go away for half an hour. Have a game of tiddly-winks, or file a few bugs
using another computer, or skim-read /War and Peace/.
* Come back and look at Mozilla.
What you should see:
* An alert, which has been there for 29 minutes, saying something like
`Mozilla could not connect to the server mail.foo.bar, because there was a
problem with the Internet connection. Check the connection and make sure
your server settings are correct, and try again.'
What you actually see:
* The throbber still spining merrily away, as if the mail server is going to
respond (via the non-existent Internet connection) any second now.
Comment 1•24 years ago
|
||
Reporter, is this problem occurring on the other platforms as well or just
specific Mac platform?
Keywords: nsbeta1
QA Contact: esther → huang
Comment 2•24 years ago
|
||
moving to 0.9.3
Priority: -- → P3
Whiteboard: [nsbeta1+]
Target Milestone: --- → mozilla0.9.3
Comment 4•24 years ago
|
||
It worksforme on mac 2001061908. I do get the alert and hitting ok on the alert
does stop the throbber.
Comment 5•24 years ago
|
||
marking wfm
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
Comment 6•23 years ago
|
||
Matthew, we don't have the dial-up connection setup internally for Mac platform.
Can you try on the latest build again to see this problem is still occurring?
Please mark as verified if you agree this problem is worksforme now. Thanks.
Comment 7•23 years ago
|
||
This bug either is WFM or fix from bug 99228.
Marking as verified.
Reporter, please reopen this bug if problem is still occurring for the latest
build.
Status: RESOLVED → VERIFIED
Reporter | ||
Comment 8•23 years ago
|
||
Reproduced in build 2001110908, Mac OS 9.1. Reopening.
Status: VERIFIED → REOPENED
Resolution: WORKSFORME → ---
Updated•23 years ago
|
Whiteboard: [nsbeta1+]
Target Milestone: mozilla0.9.7 → mozilla0.9.9
Comment 10•23 years ago
|
||
*** Bug 103278 has been marked as a duplicate of this bug. ***
Updated•23 years ago
|
Comment 12•23 years ago
|
||
This is not platform specific as the dup is on Windows 2000.
Also I think this issue should be adressed sooner -> nominating mozilla1.0
It's very annoying esp. with combination with bug 71792.
Comment 13•23 years ago
|
||
works for me on linux 2002051216 using an imaps (ssl) server - I do get a
messagebox ("error connecting to imap.web.de" or so)
Comment 14•22 years ago
|
||
See a message box that reads "Connection to server server.example.com timed
out", and I have to click "OK" before Mozilla will try to connect to that server
again.
Keywords: nsbeta1-
Summary: Mozilla never times out when trying to connect to a mail server → Connection establishment timeout: to a mail server
Updated•20 years ago
|
Product: MailNews → Core
Comment 16•18 years ago
|
||
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
Comment 17•17 years ago
|
||
Matthew, do you still see this problem?
Tom wrote: I do not use Seamonkey or Thunderbird for e-mail anymore
QA Contact: grylchan → mailnews.networking
Comment 18•17 years ago
|
||
T-bird worked fine until 1/15/2008 but timed out afterward. Message "Alert! Connection to server incoming.yahoo.verizon.net timed out"
Comment 19•17 years ago
|
||
Per previous comment. I think.
Status: NEW → RESOLVED
Closed: 24 years ago → 17 years ago
Resolution: --- → WORKSFORME
Assignee | ||
Updated•17 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•