On Fri, 06 May 2022 12:03:27 +0200 Vaclav Ovsik <vaclav.ov...@gmail.com> wrote:
after Mutt upgrade from version 2.1.4-1 to version 2.2.3-2 SASL authentication stopped working.Debug from Mutt version 2.2.3: [...]
[2022-05-06 10:33:39] smtp_auth_gsasl: using mech PLAIN [2022-05-06 10:33:39] Authenticating (PLAIN)... [2022-05-06 10:33:39] 5> AUTH PLAIN^M [2022-05-06 10:33:39] 5< 334 Send base64(login\0login\0password) [2022-05-06 10:33:39] gsasl_step64() failed (8): Base 64 coding error in SASL library
According to my understanding of RFC4954, the "server challenge" 334 response must either be blank (i.e., "334 "), or if there is data it must be base64 encoded.
The Cyrus SASL library also assumes all data from the server will be base64 encoded, but it is smarter and knows it can send an initial response with AUTH PLAIN.
What happens if you set smtp_authenticators=login? Does the server also send plain text in the 334 response?
-Kevin
signature.asc
Description: PGP signature
