Pesquisar no site de suporte

Evite golpes de suporte. Nunca pedimos que você ligue ou envie uma mensagem de texto para um número de telefone, ou compartilhe informações pessoais. Denuncie atividades suspeitas usando a opção “Denunciar abuso”.

Saiba mais

Esta discussão foi arquivada. Faça uma nova pergunta se precisa de ajuda.

Red flame suddenly appeared next to all messages

  • 3 respostas
  • 0 tem este problema
  • 32 visualizações
  • Última resposta de Steve Helberg

more options

I use Thunderbird for two email addresses. Suddenly, in the inbox of one of the email addresses, the red flame appeared next to the date of ALL messages. When I click on an individual message, the yellow line appears with the warning "Thunderbird thinks this message is Junk mail". When I click on "Not junk" the yellow line and warning disappear for a second, then reappear. Thunderbird will not let me tell it that the message is not junk. I turned off junk filtering in settings, but the problem persists. How can I clear the red flame next to all the messages and tell Thunderbird the messages are legitimate? The messages in the inbox of the other email address are not marked as junk by Thunderbird.

I use Thunderbird for two email addresses. Suddenly, in the inbox of one of the email addresses, the red flame appeared next to the date of ALL messages. When I click on an individual message, the yellow line appears with the warning "Thunderbird thinks this message is Junk mail". When I click on "Not junk" the yellow line and warning disappear for a second, then reappear. Thunderbird will not let me tell it that the message is not junk. I turned off junk filtering in settings, but the problem persists. How can I clear the red flame next to all the messages and tell Thunderbird the messages are legitimate? The messages in the inbox of the other email address are not marked as junk by Thunderbird.

Solução escolhida

We expect this will be fixed in 102.2.1 shortly. Please post your results after you have updated. Thanks.

Ler esta resposta 👍 1

Todas as respostas (3)

more options

Solução escolhida

We expect this will be fixed in 102.2.1 shortly. Please post your results after you have updated. Thanks.

more options

It is my understanding that this problem only happens in beta, and not in the release version. Quite a few people were complaining about it here. Very few were neither bothered to mention they are actually running a beta, nor which email provider they are using. So I'm wondering whether folks run betas deliberately or accidentally (for whatever reason), and aren't even aware of it. In any case, I'd expect the next beta 105.0 b2 with a fix released shortly as well.

Alterado por christ1 em

more options

The 105.0b2 Beta update solved the problem.