Outlook Oauth2 - Cannot connect to server. (Command: NAMESPACE; response: #4# [BAD, User is authenticated but not connected.])

41

The error was quite reliable for me. It seems like Microsoft fixed it. Yay!

42

I meant unreliable in the sense that it depends on the connection (and not only whether dns is in ipv4 or ipv6).
Anyhow, great to hear that it is also working again for others.

1 Like
43

Yes. I hope this isn’t a temporary fluke.

I mentioned that I was able to reliably reproduce it in the past because I am more confident that it working for me now means it is actually fixed for everyone instead of just fixed for me ;-).

Anyway, I hope that some of the IT administrators who filed tickets with Microsoft report back with Microsoft’s responses to them on the thread on answers.microsoft.com.

1 Like
44

Mine only works if I have the DNS IPV4 setup but I will take it for now

45

Thunderbird also posted in the Fediverse that their users are having the same problem.

They linked to a really long thread: Redirecting

Ref: Thunderbird: "PSA: We're aware of an issue affecting #Thunderbi…" - Mastodon

1 Like
46

Working again. I cleared cache on my Android. Can’t change to IPV4 only.

1 Like
47

Same problem with Evolution.
The auto fill-in does not work right anymore.
I had to remove my accountsettings in my computer.

I did it manually:

At the end that worked.