On Mon, 2 May 2022 20:35:13 -0700 "Kevin J. McCarthy" <ke...@8t8.us> wrote: > On Mon, 02 May 2022 19:20:29 -0400 ant <a...@anthive.com> 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. sorry for the confusion. > 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_authenticators set. > What happens if you unset that variable, does authentication work in > that case? 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 just did a quick glance at the perl script muttprofile that i use and i see no reference to that variable being set either so i'm not sure where that set is coming from. > What if you explicitly set $smtp_authenticators to "login" > or "plain"? > > 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? > > -Kevin i can send that info via private e-mail if you'd still find that useful? but i think we've got the issue figured out... :) ant
