Closed
Bug 471115
Opened 16 years ago
Closed 15 years ago
no IMAP logout command issued with SSL connections
Categories
(MailNews Core :: Networking: IMAP, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: stefan2, Unassigned)
References
Details
Attachments
(2 files)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.0.5) Gecko/2008120122 Firefox/3.0.5 Build Identifier: Version 2.0.0.18 (20081105) When I close Thunderbird, my UW-IMAP server logs: Dec 25 12:28:17 mailserver imapd[6786]: Unexpected client disconnect, while reading line user=myself host=my.client Thunderbird does not issue a IMAP logout command when being closed. Reproducible: Always Steps to Reproduce: 1. Close Thunderbird during IMAP session 2. 3. Actual Results: IMAP connection is not properly closed. Expected Results: IMAP connection should have been properly closed. Thunderbird should send a IMAP logout command to properly close the IMAP connection.
Comment 1•16 years ago
|
||
Get IMAP log, and check IMAP level flow first. See Bug 402793 Comment #1 and documents pointed in it for getting log. If timing related issue is involved(such as timeout), See Bug 402793 Comment #6 and get log with timestamp, and check IMAP level flow. If evidence of "Tb's flaw in Tb's code" is seen in log, and if analysis of log by developers will be required, attach log file to this bug(never paste long log data to bug). Please replace sensitive data such as mail-address by meaningless string before open log data to public.
Reporter | ||
Comment 2•16 years ago
|
||
Comment 3•16 years ago
|
||
> TellThreadToDie: close socket connection Tested with Gmai IMAP, with/without IDLE, on MS Win-XP SP3.) > Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1b3pre) Gecko/20081221 Shredder/3.0b2pre Tb trunk also closed socket connection immediately upon termination. No log for LOGOUT was seen. Confirming. RFC says as follows. So Tb's behavior is not RFC compliant. Workaround of "Tb's problem due to immediate connection close after LOGOUT by some servers" in the past? > http://www.faqs.org/rfcs/rfc3501.html > 3.4. Logout State >(snip) > A server MUST NOT unilaterally close the connection without > sending an untagged BYE response that contains the reason for > having done so. A client SHOULD NOT unilaterally close the > connection, and instead SHOULD issue a LOGOUT command. If the > server detects that the client has unilaterally closed the > connection, the server MAY omit the untagged BYE response and > simply close its connection. FYI. >(Bug list, bug summary contains IMAP & LOGOUT, status=open/fixed/dup) > Bug 53488 NEW --- [RFE] Should be possible to logout of IMAP mail account > Bug 115349 RESO FIXE Mozilla doesn't properly handle IMAP logout / connection closes (RFC2060) > Bug 180806 RESO FIXE IMAP backend should avoid unnecessary logout > Bug 277751 RESO DUPL IMAP logout does not wait for answer
Status: UNCONFIRMED → NEW
Component: General → Networking: IMAP
Ever confirmed: true
Product: Thunderbird → Core
QA Contact: general → networking.imap
Version: unspecified → Trunk
Reporter | ||
Comment 4•16 years ago
|
||
Obviously TB sends the LOGOUT command if there is an unencrypted IMAP session.
Assignee | ||
Updated•15 years ago
|
Product: Core → MailNews Core
Comment 5•15 years ago
|
||
David Bienvenu has opened Bug 485995. Setting it in dependency. By the way, "'David has come' is equivalent to 'mail bug will be resolved very soon'" is a my heuristics :-)
Depends on: 485995
Comment 6•15 years ago
|
||
WADA, thx for linking these - this bug is specific to SSL, though it's very possible that the fix in bug 485995 will fix this as well.
Summary: no IMAP logout command issued → no IMAP logout command issued with SSL connections
Comment 7•15 years ago
|
||
I believe this should be fixed by the checkin in bug 485995 - please re-open if it still happens, thx.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Comment 8•15 years ago
|
||
these bugs aren't technically dupes, I don't think, since this one is particular to SSL, and bug 485995 is a more recent regression. The cause is similar - we're trying to cleanup connections too close to shutdown.
Reporter | ||
Comment 9•15 years ago
|
||
Problem still exists in Thunderbird 2.0.0.23
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 10•15 years ago
|
||
but does it occur in tb 3.0 b3? The fix was checked in for the tb 3 code, our next release.
Status: REOPENED → RESOLVED
Closed: 15 years ago → 15 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•