On Fri, 6 May 2022 13:04:50 -0700 "Kevin J. McCarthy" wrote:
However, in the mean time I've pushed a commit up to branch
'kevin/gsasl-smtp-plain-workarounds' on gitlab:
I've merged this branch into stable, and it will be a part of 2.2.5
sometime in the next few weeks.
Antonio if this
On Fri, 6 May 2022 11:18:39 -0700 "Kevin J. McCarthy" wrote:
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.
I'm still interested to hear if 'set smtp_authenticators=login' works
On Fri, 06 May 2022 12:03:27 +0200 Vaclav Ovsik 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
Package: mutt
Version: 2.2.3-2
Severity: normal
Dear Maintainer,
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:19] Mutt/2.2.3 (2022-04-12) debugging at level 7
…
[2022-05-06 10:33:37] Looking
4 matches
Mail list logo
