6.0.0-beta1
9/2/25

[#11018] IMAP timeouts for users with shared mailboxes
Summary IMAP timeouts for users with shared mailboxes
Queue IMP
Queue Version 5.0.18
Type Bug
State Not A Bug
Priority 1. Low
Owners
Requester vilius (at) lnk (dot) lt
Created 02/21/2012 (4942 days ago)
Due
Updated 02/21/2012 (4942 days ago)
Assigned 02/21/2012 (4942 days ago)
Resolved 02/21/2012 (4942 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
02/21/2012 10:26:49 PM Michael Slusarz State ⇒ Not A Bug
 
02/21/2012 10:17:52 PM vilius (at) lnk (dot) lt Comment #4 Reply to this comment
Scrap that. Strange but the problem disappeared without a trace.
02/21/2012 09:48:31 PM Michael Slusarz Comment #3
State ⇒ Feedback
Reply to this comment
This indicates an issue with the IMAP server:

C: 9 STATUS INBOX (MESSAGES RECENT UNSEEN)
Slow IMAP Command: 30,03 seconds
ERROR: IMAP read/timeout error.
...
C: 2 EXAMINE INBOX (CONDSTORE)
Slow IMAP Command: 30,03 seconds
ERROR: IMAP read/timeout error.
...
C: 5 STATUS INBOX (RECENT)
Slow IMAP Command: 30,03 seconds
ERROR: IMAP read/timeout error.
C: 6 LOGOUT

If the server is not returning STATUS information after 30 seconds, or 
can't open a mailbox after 30 seconds, there is something wrong with 
that server.  IMP is not receiving any data from the IMAP server 
before the timeout is reached.  We aren't doing anything overly 
complicated here from an IMAP standpoint.
02/21/2012 09:02:16 AM vilius (at) lnk (dot) lt Comment #2
New Attachment: aaa.png Download
Reply to this comment
A screenshot from user workstation.
02/21/2012 09:01:35 AM vilius (at) lnk (dot) lt Comment #1
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ IMAP timeouts for users with shared mailboxes
Queue ⇒ IMP
Milestone ⇒
Patch ⇒ No
New Attachment: imaplog Download
State ⇒ Unconfirmed
Reply to this comment
I have couple of users who have one shared mailbox. Listing messages 
in IMP for these users fails for some strange reason. They are getting 
IMAP timeouts (log attached).

I have tried both traditional and dynamic interfaces. Same problem. 
Horde log doesn't show anything unusual even at the debug level.

Saved Queries