26773 - No alerts on network errors

Status: VERIFIED FIXED

(MailNews Core :: Networking, defect, P3)

Description

[Richard Zach]

There are no alerts on network errors or timeouts in MailNews.

To reproduce (e.g.):
1. Set up new POP or IMAP account with bogus server
2. Try to open folder (IMAP) or download msg (POP).

Actual result: POP: nothing at all, IMAP: throbber starts

Expected result: Alert dialog notifying user of DNS lookup error.

Similar situations that aren't caught: server down, connection refused, server
timeout, no route to host, etc.

Linux build 2000.02.06.09

Suggest this is fixed for bet1, otherwise we'll get a bug report every time
someone can't download their email because their ISP is having problems.

Comment 1

[leger]

Putting on PDT+ radar for beta1.

Comment 2

[(not reading, please use [e-mail] instead)]

I'm going to try to help mscott out with this bug.

he's given me pointers where to start.

Comment 3

[(not reading, please use [e-mail] instead)]

accepting.

Comment 4

[(not reading, please use [e-mail] instead)]

marking m14.

estimating monday.

Comment 5

[(not reading, please use [e-mail] instead)]

fix in hand, awaiting review from mscott.

Comment 6

[(not reading, please use [e-mail] instead)]

still working on one last part of the fix, after you get the alert on imap, the
progress and throbber still go.  I'm trying to figure out how to stop them.

Comment 7

[(not reading, please use [e-mail] instead)]

took the weekend off, working on the last issues today.

Comment 8

[(not reading, please use [e-mail] instead)]

moving to 2-23

we've got all the kinks worked out, except for a leak of nsImapProtocol that
needs to get solved.

Comment 9

[(not reading, please use [e-mail] instead)]

it looks like I'm going to check in my changes (which include a couple related
fixes, all reviewed by mscott)

sadly, the leak of nsImapProtocol is now there, since I removed that bogus call
to NS_RELEASE(me).

I'll log a new bug finding and fixing that leak.

I'll land tonight or tomorrow.

Comment 10

[(not reading, please use [e-mail] instead)]

*** Bug 29295 has been marked as a duplicate of this bug. ***

Comment 11

[(not reading, please use [e-mail] instead)]

there are three errors:  unknown host, connection refused, connection timed out.

right now, unknown host works, but we don't get told about the other two (a
necko bug, necko isn't calling our OnStopRequest when those errors happen, like
it does with unknown host.).

when I mark this fixed, I'll open a new bug for those two errors.

Comment 12

[(not reading, please use [e-mail] instead)]

fixed, now to log the related bugs.

Comment 13

[Richard Zach]

DNS lookup failure results in error on sending mail and POP/IMAp download.
Verified on Linux build 2000.02.26.08.

Comment 14

[laurel]

OK using:
2000-03-06-08 commercial build NT 4.0
2000-03-06-08 mozilla build mac 9.0

Comment 15

[MOZZOLINO]

This is still a problem in 2013 - no clear possibility to distinc between "no mail" or "network problem". Please make Thunderbird more transparent to the user so we can better see, what happens on protocol level (easy accessible protocol log window and last log line visible in status bar.)