Re: IMAP to my company's server is failing

2023-01-18 Thread Greg Marks
> Until today I could read (in my spare time) my company mails with mutt
> and IMAP. Since today it gives in the debug log:
> 
> ...
> 
> The password is fine and works via OWA365 web access.
>
> ...
>
> I have had:
> 
> set imap_authenticators="login"
> 
> but changing it to:
> 
> set imap_authenticators=plain

Is it possible that you are experiencing the same infuriating (and
still unresolved) problem I described on this mailing list in my
Oct. 25, 2022, post with subject line "in search of OAuth2 tokens
for Microsoft Office 365"?¹

Best regards,
Greg Marks

1. http://lists.mutt.org/pipermail/mutt-users/Week-of-Mon-20221024/003957.html


signature.asc
Description: PGP signature


Re: IMAP to my company's server is failing

2023-01-18 Thread Matthias Apitz
El día miércoles, enero 18, 2023 a las 01:41:16 -0800, Kevin J. McCarthy 
escribió:

> 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> a 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< a 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?

It gives:

mutt -v | grep SASL
-USE_SSL_OPENSSL  +USE_SSL_GNUTLS  +USE_SASL  +USE_GSS  +HAVE_GETADDRINFO  

> Do you have $imap_authenticators set to anything?
> 

I have had:

set imap_authenticators="login"

but changing it to:

set imap_authenticators=plain

gives:

[2023-01-19 06:59:55] Authenticating (PLAIN)...
[2023-01-19 06:59:55] 4> a0001 AUTHENTICATE PLAIN 
YXBpdHptQG9jbGMub3JnAGFwaXR6bUBvY2xjLm9yZwBNb250ZXJvc3NvLTIwMjM=^M
[2023-01-19 07:00:01] 4< a0001 NO AUTHENTICATE failed.
[2023-01-19 07:00:01] IMAP queue drained
[2023-01-19 07:00:01] imap_auth_sasl: plain failed
[2023-01-19 07:00:01] No authenticators available

Thanks for your help anyway

matthias
-- 
Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub


Re: IMAP to my company's server is failing

2023-01-18 Thread Kevin J. McCarthy

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> a 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< a 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


IMAP to my company's server is failing

2023-01-18 Thread Matthias Apitz


Hello,

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> a 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< a OK CAPABILITY completed.
[2023-01-18 19:21:31] IMAP queue drained
[2023-01-18 19:21:31] imap_authenticate: Trying method login
[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.
...

The password is fine and works via OWA365 web access. Can I do something
a part of not reading mails anymore in my spare time? Maybe I should not
do that anyway.

Thanks

matthias

-- 
Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub

Schluß mit dem (Wirtschafts-) Krieg gegen Rußland! Schluß mit den Sanktionen!
Schluß mit der Unterstützung der faschistoiden Regierungskräfte in der Ukraine!
Rußland ist nicht unser Feind, die Regierung der Kriegstreiber ist unser Feind!
Druschba / Дружба mit Rußland statt NATO-Krieg gegen Rußland!