I tried with both a shared user and a regular user. Here's the output sanitized from a shared try.
DEBUG: trying to connect to host "mail.dom.com", port 993, isSSL true
* OK The Microsoft Exchange IMAP4 service is ready.
A0 CAPABILITY
* CAPABILITY IMAP4 IMAP4rev1 AUTH=NTLM AUTH=GSSAPI AUTH=PLAIN UIDPLUS CHILDREN IDLE NAMESPACE LITERAL+
A0 OK CAPABILITY completed.
DEBUG IMAP: AUTH: NTLM
DEBUG IMAP: AUTH: GSSAPI
DEBUG IMAP: AUTH: PLAIN
DEBUG: protocolConnect login, host=mail.dom.com, user=dom\username\alias, password=<non-null> // I tried about every variation of username I could think of. and then some.
DEBUG IMAP: AUTHENTICATE PLAIN command trace suppressed
DEBUG IMAP: AUTHENTICATE PLAIN command result: A1 NO AUTHENTICATE failed.
In particular, while it mentions SMTP in the thread title, it's referencing the the IMAP implementation:
RFC: 3501 http://www.ietf.org/rfc/rfc3501.txt Title: Internet Message Access Protocol – Version 4rev1 Updated by: 4466, 4469, 4551, 5032, 5182 Obsoletes: 2060 Exchange 2010 specific: Implemented by Exchange 2010 (AUTH=PLAIN not supported) |
Other interesting threads:
JavaMail API Reference Implementation: Wiki: Exchange — Project Kenai
The exchange connector has the following settings of interest:
ProtocolName : IMAP4
Name : 1
MaxCommandSize : 10240
ShowHiddenFoldersEnabled : False
UnencryptedOrTLSBindings : {:::143, 0.0.0.0:143}
SSLBindings : {:::993, 0.0.0.0:993}
InternalConnectionSettings : {hostname.dom.com:993:SSL, hostname.dom.com:143:TLS}
LoginType : SecureLogin
EnableGSSAPIAndNTLMAuth : True