Closed Bug 277071 Opened 19 years ago Closed 18 years ago

Timeout by mail.pop3_response_timeout should be notified to user


(MailNews Core :: Networking: POP, enhancement)

Not set


(Not tracked)



(Reporter: World, Assigned: Bienvenu)



Spin off from Bug 253886(a DUP of Bug 228649).

Bug 127461 introduced mail.pop3_response_timeout(default=45sec.) to resolve
"forever wait" problem on 2004-10-26.
This has made symptom of Bug 228649 improved.
 - "forever wait" is improved to "RETR error due to timeout"
However, this timeout is not notified to user, then problem such as Bug 270014
or Bug 273369 are reported.
The only way to know "timeout" is "get POP3 protocol log" currently. 
The timeout should be notified to user by error message.

Component is set to "Networking: POP" initially.
But "timeout" is not POP3 only problem as Bug 127461 Comment #65 says.
Error message when timeout should be notified to user for any networking protocol.
Assignee: sspitzer → bienvenu
fix for 189363 will fix this.
Depends on: 189363
OK, mail.pop3_response_timeout is now obsolete/deprecated. mailnews now uses one
pref, mailnews.tcptimeout for all our timeouts (imap/pop3/nntp/smtp...). And now
you should get an alert on a timeout. I'm sorry I had to deprecate
mail.pop3_response_timeout, but now the timeout is more general.
Closed: 18 years ago
Keywords: relnote
Resolution: --- → FIXED
Was this fixed by bug 189363 (which is still not resolved), or is it actually
WORKSFORME or even INVALID at this point?
yes, as I said in Comment #2 - the fix in  bug 189363 will fix this as well. 
bug 189363 is still open because I have to check in the imap fix. The pop3 fix
was checked in earlier, and this bug is about pop3.
Product: Core → MailNews Core
Keywords: relnote
You need to log in before you can comment on or make changes to this bug.