1797951 - Can no longer access to microsoft office 365 messages if preference network.dns.disableIPv6 = false (works if true)

Status: RESOLVED INVALID

(Thunderbird :: General, defect)

Description

[rv.bocquet]

Attachment: Capture.PNG

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:106.0) Gecko/20100101 Firefox/106.0

Steps to reproduce:

First : thunderbird stopped accessing my office messages and kept asking for the password (two - three weeks ago) ==> I did nothing !
Second : I erased and tried to re-create an office account into thunderbird manually or automatically

Actual results:

best case thunderbird answers : (see attached file)

Expected results:

Connextion to office 365 message server.

Note : I am running Thunderbird 102.4.0 on Windows 10 pro 21H2. I have the same issue on a linux machine. I can access my office 365 messages on my android phone.

Comment 1

[rv.bocquet]

Note : I am running Thunderbird 102.4.0 on Windows 10 pro 21H2. I have the same issue on a linux machine. I can access my office 365 messages on my android phone.
I also check with the account administrator for a potential account desactivation. First, he told me no, second, I have no problem with my phone.

Thanks,

Regards,

Comment 2

[Magnus Melin [:mkmelin] (away, back Aug 4)]

Did you use OAuth2 authentication? They are force-rolling it out to users

Comment 3

[rv.bocquet]

Thanks for the return.
Answer is no. I got tricked into this "reinforced security trick" some time ago and discoverted TB does not support it.
Regards,

Comment 4

[Magnus Melin [:mkmelin] (away, back Aug 4)]

It is supported, and like I wrote, they are force-rolling it out.

Comment 5

[rv.bocquet]

Sorry about it, I think I am getting confused between gmail authentification and office 365. Ages ago, I accepted to change gmail authentification system and ended up with being unable to use TB as a mailer and had to go back to the original situation.
I will check with my customer IT guy if office 365 is using OAuth2.
Thanks,

Comment 6

[Thomas D. (:thomas8)]

From :mkmelin:

Microsoft are force rolling out deprecation of normal password, so you have to switch to "Authentication Method: OAuth2" in the Server Settings.

https://techcommunity.microsoft.com/t5/exchange-team-blog/basic-authentication-deprecation-in-exchange-online-september/ba-p/3609437

Comment 7

[rv.bocquet]

Attachment: Capture 02.PNG

Comment 8

[rv.bocquet]

This parameter was already set (see hardcopy). I checked again, it still does not work.

Comment 9

[Magnus Melin [:mkmelin] (away, back Aug 4)]

It is possible your admin turned off IMAP access.
In general O365 access is working.

Comment 10

[rv.bocquet]

Am I the only unlucky one ?

Comment 11

[rv.bocquet]

By the way, my mobile phone accesses office (using gmail mailer) in IMAP mode.

Comment 12

[ralph.phd]

There are more instances of this being reported / discussed here:
https://support.mozilla.org/en-US/questions/1399126

Comment 13

[Pierre Beaujean]

Hello, the same is happening here on my university address.

The last email I got was from the 25th of December, and since then, I get this annoying error "User authenticated but not connected" (which is somehow funny, I must say). I used the same settings as above, so SSL/TLS and OAuth2. What I tried was to remove all password for this account, which results in prompting me the university connection panel as usual, but it did not fix the issue.

Another funny result is that I still can send email (so SMTP is fine), but I simply cannot see the content of the folders (so ... IMAP is broken on their side?)

Comment 14

[Pierre Beaujean]

Attachment: Screenshot from 2022-12-29 13-50-39.png

Note that everything is fine using https://testconnectivity.microsoft.com/tests/O365Imap/input . This thing is even able to list my folder ;)

Comment 15

[ralph.phd]

Apparently, this is IPv6 related; disabling it in TB resolved the problem for me:

1. Menu > Settings > Gear > Config Editor
2. Toggle network.dns.disableIPv6 to true

Comment 16

[Pierre Beaujean]

Well, I don't know how you found this out, but it is indeed the solution for me :)

Many thanks and happy new year!

Comment 17

[Kenneth Hoste]

(In reply to ralph.phd from comment #15)

Apparently, this is IPv6 related; disabling it in TB resolved the problem for me:

1. Menu > Settings > Gear > Config Editor
2. Toggle network.dns.disableIPv6 to true

That's... amazing. Helped for me as well.

Comment 18

[Thomas D. (:thomas8)]

(In reply to ralph.phd from comment #15)

Apparently, this is IPv6 related; disabling it in TB resolved the problem for me:

Wow, thanks much ralph.phd - how did you find that?
If network.dns.disableIPv6 = true can fix this (as several users confirmed), that may provide clues for devs what to look for when trying to fix this.

Confirming based on several user reports.

Comment 19

[ralph.phd]

(In reply to Thomas D. (:thomas8) [PTO 23-Dec to 3-Jan] from comment #18)

(In reply to ralph.phd from comment #15)

Apparently, this is IPv6 related; disabling it in TB resolved the problem for me:

Wow, thanks much ralph.phd - how did you find that?
If network.dns.disableIPv6 = true can fix this (as several users confirmed), that may provide clues for devs what to look for when trying to fix this.

Confirming based on several user reports.

Just to give credit to the right person(s): I found this in a post by thomas289 on the mozilla help forum (https://support.mozilla.org/en-US/questions/1399126#answer-1556623), which pointed to another discussion on the Microsoft board (https://learn.microsoft.com/en-us/answers/questions/1144723/office365-email-imap-user-is-authenticated-but-not.html), and then just extracted the relevant bits to share here. It takes a village ... ;)

Comment 20

[Magnus Melin [:mkmelin] (away, back Aug 4)]

Closing, as this was some problem on Microsoft's side. It seems to have gone away fortunately.