Summary | Threaded sort by newest mail |
Queue | IMP |
Queue Version | Git master |
Type | Enhancement |
State | Duplicate |
Priority | 1. Low |
Owners | |
Requester | o+horde (at) immerda (dot) ch |
Created | 09/17/2014 (3943 days ago) |
Due | |
Updated | 09/19/2014 (3941 days ago) |
Assigned | |
Resolved | 09/19/2014 (3941 days ago) |
Milestone | |
Patch | No |
Especially since what you suggest is not a recognized form of
threading. At least one that can be performed on the server.
http://tools.ietf.org/html/rfc5256#section-3
least part of it. See request 3278
request here could be implemented independently.
its not about the collapsing, but just about the order of threads.
State ⇒ Duplicate
least part of it. See request 3278
Priority ⇒ 1. Low
Patch ⇒ No
Milestone ⇒
Queue ⇒ IMP
Summary ⇒ Threaded sort by newest mail
Type ⇒ Enhancement
State ⇒ New
It would be nice to also support ordering them by the newest message
(as most other clients do).
e.g. instead of:
thread 1 jan 3
thread 2 jan 4
thread 2 jan 2
thread 3 jan 1
i would like to see:
thread 2 jan 4
thread 2 jan 2
thread 1 jan 3
thread 3 jan 1