본 사이트는 여러분의 사용자 경험을 개선하기 위해 유지 보수를 진행하는 동안 기능이 제한됩니다. 도움말로 문제가 해결되지 않고 질문을 하고 싶다면 Twitter의 @FirefoxSupport 및 Reddit의 /r/firefox 채널을 활용하세요.

Mozilla 도움말 검색

고객 지원 사기를 피하세요. 저희는 여러분께 절대로 전화를 걸거나 문자를 보내거나 개인 정보를 공유하도록 요청하지 않습니다. "악용 사례 신고"옵션을 사용하여 의심스러운 활동을 신고해 주세요.

자세히 살펴보기

Thunderbird 102.7.1 : office365 acc stopped working after upgrade

  • 1 답장
  • 2 이 문제를 만남
  • 1 보기
  • 최종 답변자: christ1

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?

모든 댓글 (1)

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.