1920476 - 128.2.3esr - Failure to connect to Outlook.Office365 server for startup - if I switch off 'Check for new messages on startup' and only access the server with 'Get messages', then there is no problem.

Status: RESOLVED WORKSFORME

(Thunderbird :: Untriaged, defect)

Description

[john.finney]

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

Steps to reproduce:

After Version 128.2.3esr | Released September 20, 2024 installed, I opened Thunderbird as usual with 'check for new messages on startup' ticked.

Actual results:

Authentication failure.

Expected results:

It should have connected to the server and downloaded messages as usual.

However, if I switch off 'Check for new messages on startup' and only access the server with 'Get messages', then there is no problem.

This problem seems to have been introduced by this recent update.

Comment 1

[Geoff Lankow (:darktrojan) [PTO, back 28/4]]

What version did you have before 128.2.3? If it was 128.2.2, did you have another 128.something before that? You can check by going to Help > Troubleshooting Information and clicking Show Update History. I don't know how that helps (yet) but given the other problems we had with 128.2.2 it might be useful to know.

A possible workaround: open the Config Editor from the Settings tab, and remove the preferences named mail.server.server<X>.oauth2.scope and mail.smtpserver.smtp<Y>.oauth2.scope for account in question. Removing your password for the account and reauthenticating might help too.

Comment 2

[john.finney]

Thanks Geoff.

Update history goes back through 128.2.2 to 128.0.1, and before then to 115.14.0. Hope that might be useful information.

Thanks for the suggested workarounds. I did think of removing passwords and reauthenticating but as just switching off 'Check for new messages on startup'' enabled me to connect with 'get messages' I didn't go that route. I'll continue with this setting as I don't need the new message check on startup facility.

John.

Comment 3

[Magnus Melin [:mkmelin]]

Could be useful for you go to settings | config editor and set mailnews.oauth.loglevel to All. Then compare the output you see in the Error Console (Ctrl+Shift+J)

Comment 4

[Wayne Mery (:wsmwk)]

(In reply to Magnus Melin [:mkmelin] from comment #3)

Could be useful for you go to settings | config editor and set mailnews.oauth.loglevel to All. Then compare the output you see in the Error Console (Ctrl+Shift+J)

Do you still see this?

Comment 5

[john.finney]

The problem is no longer there - I assume it was cleared by an update.

Comment 6

[Wayne Mery (:wsmwk)]

Thanks.