Share via

Server errors with IMAP command pipelining

Anonymous
2020-06-29T14:23:09+00:00

Connecting to the Outlook365 mail using a 3rd party IMAP client yields errors. This happens quite frequently, several times every hour. Here is a part of the IMAP protocol log:

15:57:24.976 >>> y585 STATUS "Sent Items" (MESSAGES UNSEEN RECENT)␍␊

15:57:24.976 >>> y586 STATUS Tasks (MESSAGES UNSEEN RECENT)␍␊

15:57:25.079 <<< y566 STATUS "Calendar/Bir* STATUS Archive (MESSAGES 0 UNSEEN 0 RECENT 0) ␍␊

15:57:25.079 <<< y566 STATUS "Calendar/Bir* STATUS Archive (MESSAGES 0 UNSEEN 0 RECENT 0) ␍␊y563 OK STATUS completed.␍␊

15:57:25.084 UnexpectedHere UnexpectedHere

y566 STATUS "Calendar/Bir* STATUS Archive (MESSAGES 0 UNSEEN 0 RECENT 0)

^ here

The developers of the IMAP client say that it is a problem of Exchange server with "pipelining" of IMAP commands. Please read all the details here:

https://bugs.kde.org/show_bug.cgi?id=417756

Outlook | Windows | Classic Outlook for Windows | For home

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more

  2. Anonymous
    2020-06-29T14:29:31+00:00

    Why this is a bug in Exchange, quoting the Trojita IMAP client developer:

    Anyway, just check the raw IMAP log when this happens again. You'll see that "sometimes", Exchange takes part of its input socket buffer and sends it back to the client with seemingly no additional processing. Going back to the snippet of the log that you posted, it reads:

    y433 STATUS "Deleted Item* STATUS INBOX (MESSAGES 525 UNSEEN 0 RECENT 0)

    That just does not make sense. It starts as a tagged response ("y433" is a tag we used for a command), but then there's no OK/NO/BAD, so that's a broken server right there. It looks as if y433 STATUS "Deleted Item (note the missing "s" and the trailing quote of the quoted-string) came directly from our output (and therefore Exchange's input), while \* STATUS INBOX (MESSAGES 525 UNSEEN 0 RECENT 0) looks like a valid server's untagged response.

    Was this answer helpful?

    0 comments