Just as a follow up here - on paper you can fire up any IMAP compliant mail application and point it at us. Unfortunately what folks call "IMAP compliant" is a pinch on the squishy side. So far every client we've tested has been just a _little_ bit different on how it handles deleted items, changes in the messaging index out from under us etc... so we can't ever make a blanket statement that any client we haven't looked at will work.

the world of "standards" is sometimes not so standard.

I'd suggest firing it up and testing it out - we'd certainly be interested in hearing your experince - you're not likely going to break anything, our IMAP interfaces are pretty "defensive" - it may not let you, say, delete a message cleanly or show you the updated status if you change it over the phone interface (i.e. toggle the urgent flag of a message in your inbox via the TUI) etc... but it's worth trying at any rate.

Jeff

We have a client who is experiencing high CPU issues connecting from Entourage to Uconn 7.X.

http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCtd17052

Now Uconn 7.X doesn't list Entourage as a supported IMAP client however Ucon 1 and 2.X did list it

http://www.cisco.com/en/US/docs/voice_ip_comm/connection/compatibility/matrix/cucclientmtx.html

http://www.cisco.com/en/US/docs/voice_ip_comm/connection/2x/user_setup/guide/2xcucus030.html#wp1049605

Is there any specific reason for the omission? Has this client been tested with Uconn 7.X?  Any suggestions on what maybe be causing this?

Thanks

Srini