This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

This thread was archived. Please ask a new question if you need help.

Thunderbird 115.3.1

me chris se
me chris se
more options

Thunderbird updated itself and now I get error messages pop-ups from Microsoft every other second I keep Thunderbird open.

The error message is wrong which means something is wrong in the new version of thunderbird.

I need a fix since I tried everything by now.

I don't expect an answer/solution but I do hope for it.

Thunderbird updated itself and now I get error messages pop-ups from Microsoft every other second I keep Thunderbird open. The error message is wrong which means something is wrong in the new version of thunderbird. I need a fix since I tried everything by now. I don't expect an answer/solution but I do hope for it.
Attached screenshots

All Replies (2)

Matt
Matt
  • Moderator
  • Top 10 Contributor
more options

Unfortunately I can not read that, English is the best I can do.

Google translate managed this which helped me move on from just noticing references to cookies.

I see the references to cookies and wonder if you are assuming this refers to cookies in your web browser (Firefox 118) and leads you to an erroneous conclusion that the error message is wrong.

Thunderbird has it's own cookie management. This article is about Google oauth, but applies equally to Outlook in regards to the information about allowing cookies. https://support.mozilla.org/kb/automatic-conversion-google-mail-accounts-oauth20

Modified by Matt

me chris se
me chris se Question owner
more options

I now tried to solve the problem by comparing settings with other users.

The problem was that the update changed the authorisation settings from "password" to "OAuth2" and it also changed the server name.

By changing back to "password" and the correct server name this problem was solved.

I did not expect an update to mess with my settings.