Tìm kiếm hỗ trợ

Tránh các lừa đảo về hỗ trợ. Chúng tôi sẽ không bao giờ yêu cầu bạn gọi hoặc nhắn tin đến số điện thoại hoặc chia sẻ thông tin cá nhân. Vui lòng báo cáo hoạt động đáng ngờ bằng cách sử dụng tùy chọn "Báo cáo lạm dụng".

Tìm hiểu thêm

Bug with Office 365 POP Oauth2 method?

  • 4 trả lời
  • 2 gặp vấn đề này
  • 5 lượt xem
  • Trả lời mới nhất được viết bởi bufferflow

more options

Trying to move from normal authentication for Office 365 POP account to OAUTH2, and the window that opens to authenticate is rendered with a bunch of bugs. Any idea if this is Thunderbird or Office 365's problem? Or how to resolve?

Trying to move from normal authentication for Office 365 POP account to OAUTH2, and the window that opens to authenticate is rendered with a bunch of bugs. Any idea if this is Thunderbird or Office 365's problem? Or how to resolve?

Tất cả các câu trả lời (4)

more options

My image upload didn't work, see here: https://imgur.com/a/5L0Y1we

more options

It is usually ok to post image on comment after creating the question. If it fails - it's usually due to a bad gateway issue - refresh the page and then try again.


Have you set up to allow cookies in Thunderbird? If no then make sure it is set up.

  • Select 'Menu app icon' > 'Preferences' > 'Privacy & Security '

Under 'Web Content'

  • Select 'Accept cookies from sites'

You mention 'bugs' in the view

Is that the first view you see when it opens? Is that what you see after entering password and clicking on Sign In ? Image below.

more options

Yes, we are accepting all cookies.

Other than the black boxes added to obscure identifiable information this is exactly what we get. Missing text/labels, no buttons to proceed. We then tried OWL plugin to set up as an Exchange account and the authentication for that also opens in a similar window with missing labels and controls on the form.

This is running on latest automatic update of Thunderbird as of today.

more options

Had the same problem, found a solution [https://support.mozilla.org/en-US/que.../1392072] by user "Tussilago". Here is what solved it for me: "It was enough to remove "general.useragent.override" entry in the Config Editor in Settings and restart Thunderbird."