搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

Unified inbox view doesn't show messages

more options

Until updating Thunderbird to 52.7.0 I had the unified Inbox working fine for my 4 email accounts. Now, when I start the app it will show a blank message window.

When I select View | Folders | All everything is there.

When I go back and select View | Folders | Unified the folders collapse and show a single Inbox - which is empty. Clicking on each mailbox's name shows the messages on its pane all right.

What can I try to do about it, please?

Thank you!

Until updating Thunderbird to 52.7.0 I had the unified Inbox working fine for my 4 email accounts. Now, when I start the app it will show a blank message window. When I select View | Folders | All everything is there. When I go back and select View | Folders | Unified the folders collapse and show a single Inbox - which is empty. Clicking on each mailbox's name shows the messages on its pane all right. What can I try to do about it, please? Thank you!

被選擇的解決方法

It is solved and by an easy fix that somehow was lost when updating Thunderbird.

Using "Properties" on the menu for the Inbox, then selecting "Folder to search" to match the 4 inboxes for the 4 accounts I have, then choosing the option "Match all messages".

There was no inbox chosen, and the last option was selected as "Match all of the following", reason why my unified view had no messages showing.

I still don't understand why this has occured by itself after the update but at least now it's back.

從原來的回覆中察看解決方案 👍 0

所有回覆 (1)

more options

選擇的解決方法

It is solved and by an easy fix that somehow was lost when updating Thunderbird.

Using "Properties" on the menu for the Inbox, then selecting "Folder to search" to match the 4 inboxes for the 4 accounts I have, then choosing the option "Match all messages".

There was no inbox chosen, and the last option was selected as "Match all of the following", reason why my unified view had no messages showing.

I still don't understand why this has occured by itself after the update but at least now it's back.