>TLS negotiation is successful, but I am being thrown the following error: > > >SASL mechanisms supported by server: PLAIN LOGIN XOAUTH2 OAUTHBEARER >User has requested SASL mechanism: PLAIN >Client supported SASL mechanisms: SCRAM-SHA-512 SCRAM-SHA-384 SCRAM-SHA-256 >SCRAM-SHA-224 SCRAM-SHA-1 EXTERNAL CRAM-MD5 ANONYMOUS >SASL security layers disabled due to the use of TLS >(tls-encrypted) => RSET >(tls-decrypted) <= 250 2.0.0 OK >(tls-encrypted) => QUIT >(tls-decrypted) <= 221 2.0.0 Bye >post: problem initializing server; [BHST] SASL client start failed: SASL(-4): >no mechanism available: Unable to find a callback: 2
Do you have a -user switch to send in your .mh_profile? Or a "credentials" entry in your .mh_profile? I admit that the current behavior is perhaps a bit of a mess and has a lot of history and corner cases. I believe it is adequately explains in the "credentials" entry in mh-profile(5), but in short I think doing one of the above should work: - Putting "-user username" as an argument to send (I would do this just from the command line to test). - Putting "file:/path/to/.netrc" in the "credentials:" entry in your .mh_profile I use nmh with fastmail (well, pobox, which owns fastmail now) so it definitely works. --Ken
