When threaded view is used and sorting on date, descending, the thread is displayed in wrong order. ascending example: [-] from:<any@any.org> test1 20.30 from:<any2@any2.com> test2 20.40 from:<any3@any3.net> test3 20.50 descending example: [-] from:<any@any.org> test1 20.30 from:<any3@any3.net> test3 20.50 from:<any2@any2.com> test2 20.40
-> enhancement Rationale: Only applies to messages without In-Reply-To is. When sorting plain messages (with In-Reply-To's) thread heads are sorted not, their childs.
Sorting sub-threads would have an horrible impact on performance.
This is an old bug/thread and I think that it should be revisited. Google mail does it, so the impact on performance is not a valid reason to dismiss a perfectly valid request. Claws mail is awesome, but this bug is annoying. I miss many times emails received on threads. Actually I see that an email is but finding it is a nightmare. Why don't you change the date sorting on threaded view by tail instead of head? It would be a simple fix. If the last email in the thread is deleted then the thread is moved to the location of the last email date remained in the queue. Thanks for consideration.