1.4.3 added NTLM authentication support. Normally I would expect an Exchange
server to support NTLM, which would sometimes cause the client to fail if the
authentication information was incorrect for NTLM. But that doesn't seem to
be what's happening here.
In 1.4.3, the NTLM support required an additional library. In later releases
it was built in. That difference sometimes caused failures in 1.4.3. Have
you tried 1.5.1?
Is the client configured to use SSL? If not, the server may not be advertising
any authentication mechanisms.
You probably need to see the JavaMail debug output (protocol trace) to see
exactly what's failing.
Michael Schmiedgen wrote on 1/27/14, 8:41 AM:
> Hi List,
>
> a customer uses MS-Exchange and with JavaMail after 1.4.2 Release
> he gets the following Exception:
>
> Unable to connect to SMTP Transport. MessagingException: No authentication
> mechanisms supported by both server and client
> javax.mail.AuthenticationFailedException: No authentication mechanisms supported
> by both server and client
> at com.sun.mail.smtp.SMTPTransport.authenticate(SMTPTransport.java:769)
> at com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:687)
> at javax.mail.Service.connect(Service.java:345)
> at javax.mail.Service.connect(Service.java:226)
>
> Unfortunally I don't have access to this machine and I don't know
> the Exchange configuration. Anyone got a clue where this regression
> sneaked in after 1.4.2?
>
> Thanks
> Michael
>