Hmm. It seems that this not a bug (or flea), after all. The server advertises the "SASL-IR" capability, which means that it should be ready to accept an initital response as optional argument to the AUTHENTICATE command, according to http://tools.ietf.org/html/draft- siemborski-imap-sasl-initial-response-06
Therefore, it seems that mutt is completely right to send the authentication message as it does. Okay, this is getting curiouser and curiouser... The server does indeed accept the initial response argument, but not from mutt. If I copy the authentication string sent by mutt from the debug log, and paste it into an openssl session, it works. In mutt, it doesn't. Now I am somewhat at my wit's end. What could possibly cause the server to accept that string from openssl, but not from mutt? Timing issues? Line terminator? Mere prejudice? Is there some sort of heisenbug in mutt after all? Any help is appreciated. -- mutt fails to log in to IMAP server using TLS https://bugs.launchpad.net/bugs/137473 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
