Thunderbird IMAP responded: User is authenticated but not connected

Anonymous
2022-12-27T12:29:12+00:00

Since yesterday, my Thunderbird client cannot connect to the outlook.office365.com IMAP server and other users at my university are also having this problem. I have deleted the stored token and redone the connection procedure but it does not work. I get two error messages:

The current operation on 'inbox' did not succeed. The mail server for account ... (IMAP) responded: User is authenticated but not connected.

Server outlook.office365.com has disconnected. The server may have gone down or there may be a network problem.

This does not work on any platform: Windows, Linux or Macos. Via the browser, we can access the emails but it is a workaround because it does not support openPGP. We need Thunderbird

Outlook | Web | Outlook.com | Account management, security, and privacy

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
Anonymous
2022-12-28T22:03:29+00:00

Hi Glenn,

Which version of Thunderbird are you using.

I have 102.6.1 which is the latest one. Can you try updating it if its not and then check.

Also under Thunderbird --> Click on the gear icon on the bottom left bar --> General --> Config Editor --> Show All

Type network.dns.dis in the search field

Select the very first option and click on the toggle arrow on the right, make it true

Close and reopen Thunderbird.. See if this helps

Let me know how it goes

Was this answer helpful?

300+ people found this answer helpful.
0 comments
Answer accepted by question author
Anonymous
2022-12-28T21:34:14+00:00

Yes, it is worked for me too!

I just disabled ipv6 netwotking in thunderbird advanced configuration editor (network.dns.disableIPv6 = true)

and it is works again like a charm!

Was this answer helpful?

100+ people found this answer helpful.
0 comments

131 additional answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2022-12-29T16:46:09+00:00

    This is awsome feedback gentlemen! I spent over 8 hours going through various articles and blogs trying different setting changes in Thunderbird and on O365, and nothing worked UNTIL this recommended solution.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  2. Anonymous
    2022-12-29T17:05:40+00:00

    The workaround (network.dns.disableIPv6 = true) is indeed effective for O365, but the effect is global for all TB accounts.

    I can now no longer access another account that I can reach over IPv6 only.

    This needs to be fixed on the server side, not in the client.

    Was this answer helpful?

    5 people found this answer helpful.
    0 comments
  3. Anonymous
    2022-12-29T17:18:53+00:00

    i do not think we know yet precisely who is to blame. microsoft might have made an erroneous change to their settings, but it is also possible that thunderbird is mishandling a completely valid change by microsoft, and this problem might be happening now because this could be the first time that code path in thunderbird was seriously exercised. the correct fix might be on microsoft's side, or it might be on thunderbird's side. without a deeper understanding it is hard to say.

    we can of course request that microsoft revert whatever change they might have made on the grounds that it causes difficulty when using thunderbird.

    best wishes,

    joe

    [it has been pointed out below that the fact that non-thunderbird apps are also having problems seems to make it more likely the blame would be with microsoft. this is no doubt correct. there is the slim possibility that a bunch of apps are all misimplementing something related to ipv6, but that seems improbable. i withdraw my point above.]

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments