Troubleshooting IMAP Connectivity: Unable to authenticate to IMAP server. IMAP command failed: Login failed.



The first step is to check if the Courier IMAP server is accepting connections. Open a terminal window and type:
telnet hostname 143
Replace hostname with the IMAP server's DNS name. This expected results would look like this:
$ telnet imap.example.com 143
If you get the error "no login failed" then you need to check the following;

1. Make sure IMAP Service is running.
2. You should make sure that you are using the correct password and that the mail username is in the format:
3. Make sure there is correct name in your exchange server certificate.

Please check your certificate settings:

Get-ExchangeCertificate | fl

I noticed that the InternalConnectionSettings is pointed to Test2.contoso.com but the X509CertificateName is using Remote.domain.com. If there is a certificate with Test2.contoso.com, please change the X509CertificateName to it to have a try:

Set-IMAPSettings -Identity Test2\1  -X509CertificateName Test2.contoso.com

Then restart Microsoft Exchange IMAP service in Exchange server.


Comments

Post a Comment

Popular posts from this blog

How to prevent sending external e-mail, but allow internal e-mail in Microsoft Exchange Server.

Image
Sometime may be you have internal & external domains configured in your organization and you don't want allow internal users to send emails outside the organization or to the public domains. You can achieve this using Microsoft Exchange Transport rules. Suppose you have all internal users in OU name "InternalMail" create a distribution group in the OU and add all internal users as member. Open up Exchange admin console " https://yourexchangeserver/ecp " and navigate to "mail flow" -> "Rules" Click the + button -> " Restrict messages by sender or recipient " In this example " extblk " is a distribution group. Added two conditions first is " the recipient is located " second is " the sender is a member of " Review the Rule mode is set to "Enforce" and leave other settings default and save the rule. You are done !
Read more

Legacy Windows XP clients must match the Certificate Common Name in Outlook for (RPC over HTTP) Exchange 2013

Image
In this post I am going to discuss these two topics a bit further as this issue will impact many organisations moving to Exchange 2013 for those still running Windows XP (despite the fact it is no longer supported) seeming Exchange 2013 only supports RPC over HTTP or MAPI over HTTP (out of scope for this article). To recap what I wrote about in the previous articles 5 years ago, for RPC over HTTP(s) aka Outlook Anywhere to work on any version of the Outlook Client on the XP, the MSSTD value must match the "Common Name" on the certificate. What am I talking about? Well let me show you... The MSSTD is specified under " Only connect to proxy servers that have this principal name in their certificate " which can be found within Outlook under Account Settings, Open the Account, More Settings, Connection Tab and finally Exchange Proxy Settings. This value must match the "Common Name" of the certificate which in this example is mail.example.com as shown below nex...
Read more