On Wed, Jan 18, 2023 at 08:36:23PM +0100, Matthias Apitz wrote:
Until today I could read (in my spare time) my company mails with mutt and IMAP. Since today it gives in the debug log:... [2023-01-18 19:21:31] 4< * OK The Microsoft Exchange IMAP4 service is ready. [RgBSADMAUAAyADgAMQBDAEEAMAAyADAANAAuAEQARQBVAFAAMgA4ADEALgBQAFIATwBEAC4ATwBVAFQATABPAE8ASwAuAEMATwBNAA==] [2023-01-18 19:21:31] IMAP queue drained [2023-01-18 19:21:31] 4> a0000 CAPABILITY^M [2023-01-18 19:21:31] 4< * CAPABILITY IMAP4 IMAP4rev1 AUTH=PLAIN AUTH=XOAUTH2 SASL-IR UIDPLUS ID UNSELECT CHILDREN IDLE NAMESPACE LITERAL+ [2023-01-18 19:21:31] Handling CAPABILITY [2023-01-18 19:21:31] 4< a0000 OK CAPABILITY completed. [2023-01-18 19:21:31] IMAP queue drained [2023-01-18 19:21:31] imap_authenticate: Trying method login
Is mutt compiled with any kind of SASL support? What does `mutt -v | grep SASL` show? Do you have $imap_authenticators set to anything?
[2023-01-18 19:21:31] SASL local ip: 192.168.178.41;23775, remote ip:xxx.xxx.xxx.xxx;993 [2023-01-18 19:21:31] External SSF: 256 [2023-01-18 19:21:31] External authentication name: x...@xxx.org [2023-01-18 19:21:31] Entrando... [2023-01-18 19:21:31] 4> a0001 LOGIN "x...@xxx.org" "xxx-xxx"^M [2023-01-18 19:21:36] 4< a0001 NO LOGIN failed.
Login generally works, even if not advertised, but you may want to try setting imap_authenticators=plain. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA
signature.asc
Description: PGP signature
