Gmail config

[Kevin J. McCarthy]

On Sun, May 01, 2022 at 08:34:22PM -0400, Rob Pyott wrote:
>Here's the debug output from "connecting to smtp" to the end.  Should
>have sent all of it previously.  Thanks --

>[2022-05-01 18:40:05] 5< 250-AUTH LOGIN PLAIN XOAUTH2 PLAIN-CLIENTTOKEN OAUTHBEARER XOAUTH

This shows that the server is offering possible authenticators, 
including LOGIN and PLAIN, so the problem doesn't seem to be on Gmail's 
side.

>[2022-05-01 18:40:05] smtp_authenticate: Trying method login

It looks like you've set $smtp_authenticators.  I'm assuming you 
previously had it unset and were getting the same error, and are trying 
Andrzej's suggestion here.

In any case, "login" is clearly being offered by the server, but:

>[2022-05-01 18:40:05] SASL: No worthy mechs found

The Cyrus SASL library is reporting it can't use it and then:

>[2022-05-01 18:40:05] smtp_auth_sasl: login unavailable

Mutt gives up and tries the next one.

This looks like something is wrong with your Cyrus SASL installation. 
On Debian, for instance, the authentication modules come in a different 
package from the libsasl2 package: libsasl2-modules.  I would check to 
make sure you have at least the standard modules installed on your 
system.

If you can't find out the problem, you could also try compiling Mutt 
with gsasl support instead.  It's new in Mutt 2.2.x, and so isn't well 
tested yet, but might work for you.

-- 
Kevin J. McCarthy
GPG Fingerprint: 8975 A9B3 3AA3 7910 385C  5308 ADEF 7684 8031 6BDA
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.mutt.org/pipermail/mutt-users/attachments/20220501/d0a7fa77/attachment.asc>