搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

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.