Bugzilla Bug 62968

msmtp 1.2.3 fixes a minor bug when used with GNU SASL ("sasl" USE flag on
Gentoo): prior versions expected support for both NTLM and DIGEST-MD5 in
libgsasl without checking for it. Gentoo's libgsasl (and Debian's, too) is
build without NTLM. This can lead to false decisions when automatically
choosing an authentication mechanism.
Version 1.2.3 does not expect any mechanisms to be present: it checks (at
runtime) what's available and uses that.

Reproducible: Always
Steps to Reproduce:
1. Build msmtp with "sasl" USE flag
2. Use an SMTP server that supports NTLM authentication, but not CRAM-MD5 or
DIGEST-MD5 (these are probably very rare)
3. Let msmtp choose an authentication mechanism (this is the default)

(This is a theoretical case; I don't have access to an SMTP server of this
kind. Furthermore, an easy workaround is to manually choose the authentication
mechanism.)

Actual Results:  
msmtp chooses the NTLM authentication mechanism though libgsasl does not 
support it. Authentication fails. 

Expected Results:  
msmtp should choose an authentication mechanism that both libgsasl and the 
SMTP server support.

1.2.3 in CVS now. Thanks a lot for reporting this, it will save someone with
exotic smtp server a headache or two. :)
As a side note, would recommend removing previous msmtp ebuilds from portage
because of this bug?