Hi, I am attempting to enable IMAP4 on Exchange 2007 but cannot get it to work. This is only for one internal application server, no remote access is needed. Here is what I have done so far: Started the IMAP4 service and set it to start automatically. Ensured the mailbox I want to use for IMAP has IMAP4 access active. I have set the logintype to PlainTextLogin and restarted the IMAP4 service. In the management shell when I type: Test-ImapConnectivity -MailboxCredential:(Get-Credential domain\user) I get the error (using a proper domain and username of course): "Microsoft.Exchange.Monitoring.ProtocolException: Authentication failed. Closing the connection. The handshake failed due to an unexpected packet format.Server response while making the connection[]. --->System.IO.IOException:The handshake failed due to an unexpected packet format." The event viewer on the server logs this error: The IMAP4 service failed to connect using SSL or TLS encryption. It seems the PlainTextLogin setting has not disabled SSL. Can anyone see where I may have gone wrong? thanks, jcrow EDIT: I can telnet to port 143 on the Exchange Serve - * OK The Microsoft Exchange IMAP4 service is ready. It seems very unstable though. I can run commands to view folders but get kicked out after 15 or 20 seconds. I still cannot connect Outlook 2003 via IMAP and my application server cannot connect either.

HA! Rebooted the Exchange server and it runs fine! Admittedly the server hasn't been rebooted for a while. I still get an error running the command: Test-ImapConnectivity -MailboxCredential:(Get-Credential domain\user) "Authentication failed. Unable to read data from the transport connection." but a test email is successfully sent to the mailbox.

Hi Do you have anything update on your issue? I talk with my colleague and we think it is just test command problem. If you IMAP works well, you neednt worry about this error information.Terence Yu TechNet Community Support