Closed
Bug 608469
Opened 14 years ago
Closed 8 years ago
imap server connection not closed until exit of Seamonkey
Categories
(MailNews Core :: Networking: IMAP, defect)
Tracking
(Not tracked)
People
(Reporter: mozilla, Unassigned)
Details
(Whiteboard: [dupeme])
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.14) Gecko/20100930 SeaMonkey/2.0.9 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.14) Gecko/20100930 SeaMonkey/2.0.9 If one has an imap server, and if the "Use IDLE command if the server supports it" is off, and if "Check for new messages every N minutes" if off, then seamonkey still hold the server connection open after reading mail. Reproducible: Always Steps to Reproduce: 1. configure an imap mail server 2. open and read mail 3. close mail Actual Results: tcp connection to server remains open Expected Results: tcp connection should be closed Additionally, if one turns "Check for new messages every N minutes" off, then why should IDLE commands still occur? If one does not want to learn of new messages then it should not happen. The "Check for new messages every N minutes" setting being turned off should override any "Use IDLE command if the server supports it" setting. But in any case, if both options are turned off then the tcp connection should be closed when the mail window closes.
Updated•14 years ago
|
Severity: major → normal
Component: General → Networking: IMAP
Product: SeaMonkey → MailNews Core
QA Contact: general → networking.imap
Version: unspecified → 1.9.1 Branch
Comment 1•10 years ago
|
||
connections stay open until they timeout. I'm pretty sure this is a duplicate of another seamonkey bug report, but I'm not finding it.
Whiteboard: [dupeme]
Comment 2•8 years ago
|
||
Found it. This is bug 49473 and there are no plans to change this
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
Summary: imap server connection not closed until exit → imap server connection not closed until exit of Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•