When using the inbox as todo list ordered by date (admittedly could be a Linux kernel developer specific thing to do) -- it's very annoying when people reply to an old thread with new work. It makes the issue appear as the oldest (based on date, sorting by thread date has its own perils of de-prioritizing active discussions). It'd be amazing if we had a flag or tag which would force a message to start a new tree/thread.
Hi, you can probably get the behavior you want by defining an Action that would more or less grep - v ^In-Reply-To and ^References. Potentially add a custom shortcut to call the action easily. HTH
Thanks! I tried this: sed -i '/^In-Reply-To:/d;/^References:/d' .claws-mail/imapcache/... which had a curious effect of moving the thread down in the list but it's still not broken (there are replies to the message I removed references from, which I presume still carry the References headers).
Hi. I am struggling with the same issue. Someone replies to a thread that was started years ago, and that new message will stay way up (down) in the message list until read/processed. I also keep messages "unread" as a todo reminder, but scrolling over several km of message list to get from one TODO item to the next is not very practical. I have decided to create a sub-folder of my inbox called "ThreadAttic" and move the first N messages of a thread there, so it gets split. After reloading, the remaining thread is now at a more sensible date. Another solution that occurred to me was adding an option in the settings of the Message List, to sort on the date of the latest message in the thread, instead of sorting on the the first message in the thread. This way, old threads with new messages will always stay "near". Should I file a new bug for this?
(In reply to david from comment #3) Use /View/sort/by thread date