搜索 | 用户支持

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

详细了解

Keep messages grouped by thread, when the parent has been archived?

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

more options

I am receiving a large number of automated messages that would profit greatly from threading, but they are not threaded, after I archive the parent message, see screenshot.

Is there some way to keep these threads together, after the original message has been archived?

The JIRA of the same thread all have the "In-Reply-To" header and "References" header set to the root message.

Keeping the root messages in my inbox is not viable; There would simply be too many.

I am receiving a large number of automated messages that would profit greatly from threading, but they are not threaded, after I archive the parent message, see screenshot. Is there some way to keep these threads together, after the original message has been archived? The JIRA of the same thread all have the "In-Reply-To" header and "References" header set to the root message. Keeping the root messages in my inbox is not viable; There would simply be too many.
已附加屏幕截图

所有回复 (2)

more options

without the parent the threading is broken as they are all peers, although replies to those would thread.

Right clicking and selecting view in conversation will display the threaded conversation.

There are some hidden preferences for Threading, but I do not know if they will get you what you want. This article basically tells you how to not do what you want, but documents the settings. http://kb.mozillazine.org/Mail.thread_without_re

more options

Matt said

http://kb.mozillazine.org/Mail.thread_without_re

Already tried those; They don't change the behavior.

The issue is mainly that such notification emails heavily clutter the Inbox, so being able to view them as a thread (Ctrl+Shift+O) is a useful feature, but the larger issue is keeping the Inbox organized.

The end result is that active discussions are compacted into a single thread, and hard to find between all the notifications, significantly impacting workflows.