Pesquisar no apoio

Evite burlas no apoio. Nunca iremos solicitar que telefone ou envie uma mensagem de texto para um número de telefone ou que partilhe informações pessoais. Por favor, reporte atividades suspeitas utilizando a opção "Reportar abuso".

Saber mais

Saved search properties on 52.2.0 doesn't remember accounts

  • 5 respostas
  • 4 têm este problema
  • 20 visualizações
  • Última resposta por chaosxian

more options

Local Inbox saved search folders forgets settings in 52.2.0

I have 4 folders to search chosen for Local Inbox. These are the individual inbox folder from 4 email accounts. This way I can monitor all my Inbox email at one place. After upgrading to 52.2.0, two of the folders became unchecked (both are gmail accounts). After rechecking them and then closing/reopening TBird the chosen search folders were missing the 2 accounts again.

Local Inbox saved search folders forgets settings in 52.2.0 I have 4 folders to search chosen for Local Inbox. These are the individual inbox folder from 4 email accounts. This way I can monitor all my Inbox email at one place. After upgrading to 52.2.0, two of the folders became unchecked (both are gmail accounts). After rechecking them and then closing/reopening TBird the chosen search folders were missing the 2 accounts again.

Todas as respostas (5)

more options

Was Thunderbird FULLY closed? Can you try again with a reboot after setting the mailboxes and before re-opening?

more options

Yes, TBird was fully closed (I checked w/Task Manager). I did not try the reboot though. I'll do that with the next release. For now I have reverted to 51.1.1 and all is good.

more options

Version 52.2.1 is now available

more options

Wayne Mery said

Version 52.2.1 is now available

I'll give it a try. Thanks!

FWIW, a related problem to the OP is when I attempted to add back the missing Inbox folders, sometimes the account folders I was seeking did not appear in the folder selection window. To resolve that (temporarily) I had to exit/restart TBird.

more options

52.2.1 seems to have solved the issue I reported. Thank you.