Outlook 2013 IMAP connecting to Cisco Unity Voicemail

Question

The ability to use IMAP in our Outlook 2013 stopped working back in November updates, we worked with MS Support for the other Outlook issues that were broken thinking that whatever fix would also resolve the IMAP issue. This was not the case.
Our voicemail is hosted on a Cisco Unity Server by our provider that we connect to using IMAP. Initially I was unable to connect to their server using IMAP because the November update sent their server to 100% CPU. After a Cisco patch I'm now able to
connect, however functionality is still not there.
Outlook 2010 clients seem to work fine. Outlook 2013 clients will sync the inbox the first time connecting but never after that, you are also unable to delete messages from the reading pane (able to open message and delete).
I'm aware of the root folder "Inbox" and the subscribe methods for troubleshooting this, however neither work.
Does anyone have any suggestions on where to go from here?
Thanks much

Answer 1

So what eventually solved this was Office SP 1.
Below is a set of packet captures with Outlook 2013 interacting with a Unity server both before and after the SP was installed.
OUTLOOK 2103 WITH SP1 – WIIN 8 shows:
Packet 223: UID FETCH 177:4294967295 (UID FLAGS RFC822.SIZE BODY.PEEK[] INTERNALDATE)
Follow TCP Stream shows CUC handles this request fine:
x9tf UID FETCH 177:4294967295 (UID FLAGS RFC822.SIZE BODY.PEEK[] INTERNALDATE)
* 44 FETCH (UID 177 FLAGS (\Recent) RFC822.SIZE 43627 BODY[] {43627}
Date: Wed, 26 Feb 2014 16:46:47 +0000
From: "Spare Phone4" <5555555555@XXXdomain>
To: 4444444444@domain
MIME-Version: 1.0
Message-Id: <MAL.1dfcffe1-aef3-4ba4-b4eb-3d728835f4a0@domain>
X-CiscoUnity-CallerAni: 810168950
Importance: Normal
X-Priority: 3
Sensitivity: None
Subject: Message from Spare Phone[phone])
X-CiscoUnity-MessageType: Voice
Content-Type: audio/wav; name=VoiceMessage.wav
Content-Dis; filename=VoiceMessage.wav; voice=Voice-Message
CUC seems to handle this ok
Packet 708: UID SEARCH UID 178:4294967295 SINCE 24-Feb-2014
Follow TCP Stream shows that CUC returns “invalid arg”.  However, IMAP then  performs “Fetch” request afterwards, which ultimately works
i6kl UID SEARCH UID 178:4294967295 SINCE 24-Feb-2014
i6kl BAD Invalid Argument
kkl1 IDLE
+ idling
DONE
kkl1 OK IDLE Completed
y2mw UID FETCH 1:177 (UID FLAGS)
* 1 FETCH (UID 121 FLAGS (\Seen))
* 2 FETCH (UID 122 FLAGS (\Seen))
* 43 FETCH (UID 174 FLAGS (\Seen))
* 44 FETCH (UID 177 FLAGS (\Seen))
y2mw OK FETCH Completed
BROKEN IMAP shows: (non-SP1)
Packet 32: UID SEARCH UID 155:4294967295 SINCE 17-Feb-2014
Follow TCP Stream shows that CUC returns invalid arg and then IMAP sends LOGOUT request.
my5r UID SEARCH UID 155:4294967295 SINCE 17-Feb-2014
my5r BAD Invalid Argument
jveg IDLE
+ idling
* 32 EXISTS
* 3 RECENT
DONE
jveg OK IDLE Completed
3l5q LOGOUT
* BYE UMSS IMAP4rev1 Server logging out
3l5q OK LOGOUT Completed
So the connectivity is work and the Outlook client now maintains functionality. The last thing I've noticed is that if you try to delete a message from either the view/reading pane or the home ribbon from Win 8/8.1 Outlook 2013/2013 SP1 it fails, you need
to go open the message to delete it.
On a Win7 machine Outlook 2013 you experienced the same thing, however after the SP1 is applied all deletion options work.
When you press the any delete key it seems the client is suppose to send an expunge command (noticed through wireshark). With the delete keys that do not function this command is not sent, those that do work the command is seen with wireshark.