Avatar for Username

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

This thread was archived. Please ask a new question if you need help.

BUG: Inbox lists mails (correctly) marked as spam

  • 2 replies
  • 1 has this problem
  • 5 views
  • Last reply by Andi

Andi
Andi
more options

I use v102.0b5 (64-bit) on Mac OS 10.14.6 and have now deactivated automatic updates, because my user experience on Thunderbird has degraded over the past weeks.

One problem: Suddenly my inbox lists mails correctly marked as spam: The flame (to signify spam) is shown in the list.

The expected behavior (which was applied until the last version) is of course that Thunderbird must move those mails marked as spam (my spam filter is well-trained and the markings mostly correct) into the junk folder.

How can I make this happen? Thank you for your help!

I use v102.0b5 (64-bit) on Mac OS 10.14.6 and have now deactivated automatic updates, because my user experience on Thunderbird has degraded over the past weeks. One problem: Suddenly my inbox lists mails correctly marked as spam: The flame (to signify spam) is shown in the list. The expected behavior (which was applied until the last version) is of course that Thunderbird must move those mails marked as spam (my spam filter is well-trained and the markings mostly correct) into the junk folder. How can I make this happen? Thank you for your help!

All Replies (2)

Matt
Matt
  • Moderator
  • Top 10 Contributor
more options

The beta mailing list is here https://thunderbird.topicbox.com/groups/beta

My guess is your anti virus does not recognise the beta version and as a result is scanning all the files when they change resulting in failed moves of mail into those files and out of them.

You might also try restarting in troubleshoot mode and see if it may be an addon that is the issue.

Andi
Andi Question owner
more options

Thank you for your quick reply!

For now (without changing the version) this problem has resolved itself. I don't know why. It seems that the automatic update was somehow responsible for this.

Modified by Andi