Buscar en Ayuda

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

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

  • 1 respuesta
  • 0 tienen este problema
  • 4 visitas
  • Última respuesta de 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

Solución elegida

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

Leer esta respuesta en su contexto 👍 0

Todas las respuestas (1)

more options

Solución elegida

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