I went back and looked at the old code to see what the change was.
It looks like this is due to a bug fix. In 1.4.2, if it couldn't
find any authentication mechanisms, it just blindly went forward
without authenticating, even though you asked it to authenticate.
In 1.4.3, it fails if there are no matching authentication mechanisms
and you asked it to authenticate.
Apparently the Exchange server is allowing mail to be sent without
authenticating. If that's the intention, the application should
*not* be passing a username and password to the connect method, and
should *not* be setting the mail.smtp.auth property to true.
Michael Schmiedgen wrote on 1/28/14, 1:43 AM:
> Hi Bill,
>
> thanks for your reply. Can you add me to CC, I am not subscribed
> to the list.
>
>> it was built in. That difference sometimes caused failures in 1.4.3. Have
>> you tried 1.5.1?
>
> I tried all versions down to the one that worked.
>
>> Is the client configured to use SSL? If not, the server may not be
>> advertising
>> any authentication mechanisms.
>
> No, SSL ist not used there.
>
>> You probably need to see the JavaMail debug output (protocol trace) to see
>> exactly what's failing.
>
> Ok, I will try to get a debug log and let you know.
>
> Thanks,
> Michael
>