搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

Deleted messages are no longer marked as read

  • 2 个回答
  • 1 人有此问题
  • 1 次查看
  • 最后回复者为 marwer

more options

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

由marwer于修改

被采纳的解决方案

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

定位到答案原位置 👍 1

所有回复 (2)

more options

选择的解决方案

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

more options

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!