Ken Hornstein <[email protected]> wrote:
>> (tls-decrypted) <= 250 AUTH PLAIN LOGIN XOAUTH2 OAUTHBEARER
>> SASL mechanisms supported by server: PLAIN LOGIN XOAUTH2 OAUTHBEARER
>> No SASL mech selected, will pick the best mech supported by SASL library
>> Client supported SASL mechanisms: SCRAM-SHA-512 SCRAM-SHA-384
SCRAM-SHA-256 SCRAM-SHA-224 SCRAM-SHA-1 DIGEST-MD5 EXTERNAL CRAM-MD5 NTLM LOGIN
PLAIN ANONYMOUS
>> SASL security layers disabled due to the use of TLS
>> Chosen sasl mechanism: LOGIN
> The difference between this output and Diego's is that Diego's doesn't
show
> client support for PLAIN. A little odd that it picked LOGIN as a
mechanism,
> but fine, whatever. I hope the SASL log patch I sent him will help.
I usually compile nmh from source code, because fixes/patches/etc.
Maybe the debian package is compiled without the right sasl-dev libraries
included.
Looking into the source code, however, I see:
Build-Depends: debhelper (>= 12.0.0), dh-strip-nondeterminism, libncurses5-dev,
liblockfile-dev (>= 1.01), libsasl2-dev, libdb-dev, flex, libfl-dev,
libssl-dev, libcurl4-openssl-dev, libreadline-dev, libsasl2-modules
I could try again with the nmh package....
... apt-get install nmh. Got me 1.8-RC2.
obiwan-[~](3.3.8) mcr 10022 %/usr/bin/mh/send -snoop drafts/54
but, I didn't get any output from -snoop.
I was asked twice about upgraded to 1.8-RC2...
Confused.
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works | IoT architect [
] [email protected] http://www.sandelman.ca/ | ruby on rails [
