We are currently upgrading our Exchange environment to 2013 from 2007. Our 2007 Exchange is a multi-role and our 2013 is two servers - a CAS role and MBX role. So far, following the deployment guide, we have most everything working and have begun moving mailboxes. However, we can not get IMAP to work. I have started the IMAP services on both the CAS and MBX servers and assigned IMAP to our UC certificate. Checking get-imapsettings on our 2013 CAS server the X509CertificateName does match our UC certificate name on our 2013 CAS. Under ECP > Servers > CAS - I have authentication for IMAP set to Secure TLS connection and everything else as default. When I run the Microsoft Remote Connectivity analyzer using a account that we have migrated to 2013 I get the following error below. It successfully resolves the host name we use for Exchange, the port 993, and shows a valid certificate. Any ideas what I may be missing for IMAP to work. OWA and other services seem to be working just fine. Is there anything manual I need to do with the imap settings for internal/external urls,etc. Any assistance would be greatly appreciated. I have spent 3 days trying to diagnose the problem.
S: * OK The Microsoft Exchange IMAP4 service is ready.
C: 1 CAPABILITY
S: * CAPABILITY IMAP4 IMAP4rev1 AUTH=PLAIN CHILDREN IDLE NAMESPACE LITERAL+
1 OK CAPABILITY completed.
C: 2 LOGIN testuser <password>
S: 2 NO LOGIN failed.
C: 3 LIST "" *
S: 3 BAD Command received in Invalid state.
Microsoft.Exchange.Tools.ExRca.Tests.ImapPop.MailProtocolException: 3 BAD Command received in Invalid state.
at Microsoft.Exchange.Tools.ExRca.Tests.ImapPop.ImapProtocolTester.SendCommand(String command, String logString)
at Microsoft.Exchange.Tools.ExRca.Tests.ImapPop.BaseProtocolTest.PerformTestReally()