Search Support

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

Red flame suddenly appeared next to all messages

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.

Chosen solution

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

Read this answer in context 👍 1

All Replies (3)

more options

Suluhisho teule

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.

Modified by christ1

more options

The 105.0b2 Beta update solved the problem.