Exchange 2013, IMAP4 not working - aCIK NO LOGIN failed.


We have here Exchange 2013 and will connect some mailboxes with IMAP4, but ...

[PS] C:\Windows\system32>test-imapconnectivity -ClientAccessServer:irrsee -MailboxCredential(Get-Credential innovations\
hilfe) | fl

RunspaceId                  : 29a1553a-f775-45e8-9942-ad6adf77c86e
LocalSite                   : Standardname-des-ersten-Standorts
SecureAccess                : False
VirtualDirectoryName        :
Url                         :
UrlType                     : Unknown
Port                        : 993
ConnectionType              : Ssl
ClientAccessServerShortName : IRRSEE
LocalSiteShortName          : Standardname-des-ersten-Standorts
ClientAccessServer          : IRRSEE.innovations.local
Scenario                    : IMAP4-Verbindung testen
ScenarioDescription         : Stellen Sie mit dem Server eine Verbindung mithilfe des IMAP4-Protokolls her, suchen Sie
                              nach der Testnachricht, und löschen Sie diese zusammen mit allen Nachrichten, die älter
                              als 24 Stunden sind.
PerformanceCounterName      : ImapConnectivity-Latency
Result                      : Fehler
Error                       : IMAP Fehler: aCIK NO LOGIN failed.

UserName                    : hilfe
StartTime                   : 18.06.2013 09:42:29
Latency                     : 00:00:00.1563271
EventType                   : Error
LatencyInMillisecondsString :
Identity                    :
IsValid                     : True
ObjectState                 : New

If i use another user it works, if i create a new user same as above. If i connect from thunderbird ... same problem - it didn't work ...

Any idea?
Who is Participating?
kv0sConnect With a Mentor Author Commented:
No solution, problem solved another day - but didn't know why.
Sanjay SantokiCommented:

May I know how you are trying to connect IMAP from email client? By design it will not allow you to use normal IMAP you have to use IMAP over SSL (TCP 993). Although as an Admin you can change it to allow plaintext authentication as well and need to modify binding of IMAP protocol accordingly.

Sanjay Santoki
kv0sAuthor Commented:
Hello Sanjay.

Yes - i test it from an E-Mail Client and use the Exchange-Shell cmdlet (test-imapconnectivity -ClientAccessServer:irrsee -MailboxCredential(Get-Credential innovations\
hilfe) | fl).

For the user "ko" it works, other users not. Is there anything to configure in the userprofiles so they can use IMAP or POP3?

It isn't a problem with SSL or not. It works with the user "ko" but not with others.
kv0sAuthor Commented:
Solved, but didn't know why.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.