Open Bug 215129 Opened 21 years ago Updated 16 years ago

scant diagnostics for failed POP configurations

Categories

(SeaMonkey :: MailNews: Message Display, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

People

(Reporter: metaperl, Unassigned)

References

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5a) Gecko/20030718
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5a) Gecko/20030718

I setup Mozilla Mail just like outlook express. Although both failed due to
technical problems on the mail server side. The fact that OUtlook gave an
extensive trace of the TCP/IP traffic made it much easier to show that the
problem was not client side.

You need to give much deeper diagnostic info when things fail instead of just a
popup window claiming that it failed.

Reproducible: Always

Steps to Reproduce:
1.just fail to connect to a mailer server
2.ask yourself if a popup saying "failed" is enough to trace the source of error
3.
We already have the possibility of producing a log. See
http://www.mozilla.org/quality/mailnews/mail-troubleshoot.html for this.

Maybe we should add a UI (Explain-Button) for the client to make it better
accessible.
On the other hand, what percentage of the users would benefit from seeing
cryptic TCP/IP talk? I guess not much more than knowing how to produce the log now.

But nevertheless it could be a nice enhancement, so marking as RFE.
Severity: normal → enhancement
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows XP → All
Hardware: PC → All
Product: Browser → Seamonkey
Assignee: sspitzer → mail
we have a small circular dependency going here - click "show dependency tree"
Assignee: mail → nobody
QA Contact: esther → message-display
You need to log in before you can comment on or make changes to this bug.