搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

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