搜尋 Mozilla 技術支援網站

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

了解更多

Thunderbird on MacBook updated last night and now no messages are displayed for any folders

  • 1 回覆
  • 0 有這個問題
  • 4 次檢視
  • 最近回覆由 mevalery

more options

I have many folders for 2 POP accounts. This morning everything looked ok. I quit Thunderbird after it had been running unclosed for a week. Came back home, opened Thunderbird, and there are no messages in any folders. My folder pane looks good. I can email from one POP account to another, Get Messages, and see that I have a new message in the other Inbox because the InBox icon changes. But click on that folder or any folder and there are no messages displayed. I looked in all the directories and the box files are all there and the correct size. Go to the bottom of that Inbox file and there is the new test message I just did. One other thing Thunderbird version 115.8.0, MacOS 11.7.10, and there is a SuperNova symbol that I do not remember seeing before. Thanks

I have many folders for 2 POP accounts. This morning everything looked ok. I quit Thunderbird after it had been running unclosed for a week. Came back home, opened Thunderbird, and there are no messages in any folders. My folder pane looks good. I can email from one POP account to another, Get Messages, and see that I have a new message in the other Inbox because the InBox icon changes. But click on that folder or any folder and there are no messages displayed. I looked in all the directories and the box files are all there and the correct size. Go to the bottom of that Inbox file and there is the new test message I just did. One other thing Thunderbird version 115.8.0, MacOS 11.7.10, and there is a SuperNova symbol that I do not remember seeing before. Thanks

被選擇的解決方法

Manually reinstalled 115.8.0, discarded previous 115.8.0, and problem persisted. I reverted back to 115.7.0, discarded previous 115.8.0, and everything works

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

所有回覆 (1)

more options

選擇的解決方法

Manually reinstalled 115.8.0, discarded previous 115.8.0, and problem persisted. I reverted back to 115.7.0, discarded previous 115.8.0, and everything works