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

Thread ini telah diarkib. Sila tanya soalan baru jika anda perlu bantuan.

Thunderbird 102.7.1 : office365 acc stopped working after upgrade

  • 1 balasan
  • 2 ada masalah ini
  • 2 paparan
  • Balasan terakhir oleh christ1

Free82
Free82
more options

Today, I updated the system (including thunderbird) on my KDE Neon machine (Ubuntu Linux with KDE).

Before the update, I normally received e-mails from my (company) O365 SMTP/Oauth2 account.

After the update, it simingly forgot the password as it opened a company webpage asking for credentials (Oauth2 thing). The password is accepted, the popup closes - but then the TB says "authentication failure when connecting to server outlook.office365.com") and it opens popup again.

It happened on both of my machines right after updating to 102.7.1.

Details:

M$ O365 acc: IMAP using SSL/TLS and OAuth2 TB version: 102.7.1+build1.2-0ubuntu0.22.04.1~mt1

Any ideas on how to fix that?

Today, I updated the system (including thunderbird) on my KDE Neon machine (Ubuntu Linux with KDE). Before the update, I normally received e-mails from my (company) O365 SMTP/Oauth2 account. After the update, it simingly forgot the password as it opened a company webpage asking for credentials (Oauth2 thing). The password is accepted, the popup closes - but then the TB says "authentication failure when connecting to server outlook.office365.com") and it opens popup again. It happened on both of my machines right after updating to 102.7.1. Details: M$ O365 acc: IMAP using SSL/TLS and OAuth2 TB version: 102.7.1+build1.2-0ubuntu0.22.04.1~mt1 Any ideas on how to fix that?

All Replies (1)

christ1
christ1
  • Top 25 Contributor
more options

There is no official 102.7.1 version of Thunderbird. There is only a release candidate for 102.7.1, which never made it to release status. Presumably this is what you got from Ubuntu, and you should complain to them.

The current release version is 102.7.0, but this is broken as well. So your best bet is to downgrade to 102.6.1 for the time being, or wait until an official 102.7.1 version with a fix will be released, possibly in about a week.