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

Deleted messages are no longer marked as read

  • 2 replies
  • 1 has this problem
  • 45 views
  • Paskiausią atsakymą parašė marwer

Hi all

After upgrading to 115 (Linux amd64), messages are no longer marked as read when I delete them before they are marked as read (either automatically or manually). I have (and have had for many years) set "When I delete a message" to "Move it to this folder" -> Trash on (Name of my IMAP account). Before the upgrade, messages were moved to the Trash AND automatically marked as read when I deleted them. Now, they are moved to the selected Trash folder, but left unread, and the Trash folder gets displayed in bold, together with a number counting unread messages in it.

Is there a way to get the old behaviour back?

Thanks and best regards /m

Hi all After upgrading to 115 (Linux amd64), messages are no longer marked as read when I delete them before they are marked as read (either automatically or manually). I have (and have had for many years) set "When I delete a message" to "Move it to this folder" -> Trash on (Name of my IMAP account). Before the upgrade, messages were moved to the Trash AND automatically marked as read when I deleted them. Now, they are moved to the selected Trash folder, but left unread, and the Trash folder gets displayed in bold, together with a number counting unread messages in it. Is there a way to get the old behaviour back? Thanks and best regards /m

Modified by marwer

Chosen solution

I'm not seeing this behavior.

Two things to try: 1. Change the setting to something else. restart Thunderbird, then change the setting back. 2. Help > Troubleshoot Mode

Skaityti atsakymą kartu su kontekstu 👍 1

All Replies (2)

Chosen Solution

I'm not seeing this behavior.

Two things to try: 1. Change the setting to something else. restart Thunderbird, then change the setting back. 2. Help > Troubleshoot Mode

Ah, yes. There was an extension that needed upgrading which seems to have caused this. When the problem did not occur in troubleshooting mode, it became clear that the problem had to be with a plugin. After updating it, everything is back to normal now. Thanks for the pointer!