Closed
Bug 672289
Opened 14 years ago
Closed 13 years ago
Odd Idle Behavior
Categories
(MailNews Core :: Networking: IMAP, defect)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: phil, Unassigned)
Details
(Whiteboard: [needs protocol log])
Attachments
(1 file)
|
595 bytes,
application/octet-stream
|
Details |
I'm debugging some odd issues between thunderbird and exchange wrt IDLE. I've attached a packet capture that seems to show two issues - one is what I believe to an Exchange bug, and another I believe to be - an odd TBird behavior at the least, or possibly a bug: tbird has less than a second between IDLE and IDLE DONE.
This is how it goes:
10:53:51.48 C: IDLE
10:53:51.48 S: IDLE accept
10:53:51.52 C: ack (tcp)
10:53:51.64 C: IDLE DONE # less than 2/10ths of a second later, tbird bug??
10:53:51.68 S: ack (tcp)
10:54:51.64 S: IDLE DONE accept # 60 seconds later! exchange bug?
For the exchange side of things I've asked our Exchage admins to push this up to MS, but as I said, I think there's a tbird bug here as well.
Thunderbird: 3.1.10.
- Phil
| Reporter | ||
Comment 1•14 years ago
|
||
Oh, I forgot to mention - this is going through stunnel so that I can debug and see the packets. Port 9999 on is the server (both hosts are localhost).
Component: General → Networking: IMAP
Product: Thunderbird → MailNews Core
QA Contact: general → networking.imap
Version: 3.1 → 1.9.2 Branch
| Reporter | ||
Comment 2•13 years ago
|
||
Ping?
Comment 3•13 years ago
|
||
Are we running an other url after the IDLE Done? Or not? IMAP protocol logging from the client is more informative for us - https://wiki.mozilla.org/MailNews:Logging
and you can add ",timestamp" to the log modules
Comment 4•13 years ago
|
||
Hi Phil. Need an imap:5 protocol log per comment 3 please. Using something in the neighborhood of version 13, now that TB3.x is unsupported
Whiteboard: [closeme 2012-08-01][needs protocol log]
Resolved per whiteboard
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → INCOMPLETE
Whiteboard: [closeme 2012-08-01][needs protocol log] → [needs protocol log]
You need to log in
before you can comment on or make changes to this bug.
Description
•