On Tue, May 03, 2022 at 12:00:44PM -0400, ant wrote:
i don't explicitly set that variable anywhere in any of my mutt
profiles that i know of. unsetting that does allow mutt to send
mail again using the 2.2.3-2 version so that did take care of the
problem. thank you! :)
I'm glad that fixed t
On Mon, 2 May 2022 20:35:13 -0700 "Kevin J. McCarthy" wrote:
> On Mon, 02 May 2022 19:20:29 -0400 ant wrote:
> > Package: mutt
> > Version: 2.2.3-1
>
> Just checking this is for 2.2.3-2.
yes, because of the error i could not e-mail so i downgraded
to 2.2.3-1 so i could get back to working mail
On Mon, 2 May 2022 20:35:13 -0700 "Kevin J. McCarthy" wrote:
I'll try to see if I can duplicate the problem, but I don't have access
to a smtp server supporting cram-md5. Is the server you are using
accessible for me to try (and of course fail) authenticating with?
I've just noticed one funn
On Mon, 02 May 2022 19:20:29 -0400 ant wrote:
Package: mutt
Version: 2.2.3-1
Just checking this is for 2.2.3-2. That update switched to the gsasl
library, which unfortunately needs some bugs worked out with its mutt
implementation. :-(
From the debug log, it looks like you have $smtp_aut
Package: mutt
Version: 2.2.3-1
Severity: important
X-Debbugs-Cc: a...@anthive.com
Dear Maintainer,
recent update to mutt broke sending of mail:
[2022-05-02 19:10:36] Mutt/2.2.3 (2022-04-12) debugging at level 5
[2022-05-02 19:10:36] In mutt_reflow_windows
...
[2022-05-02 19:10:59] 4< 250-AUTH
5 matches
Mail list logo
