Tickets :: Comment on [#8936] Clean up date/arrival/sequence sorting

* Your Email Address
* Spam protection	Enter the letters below: .__ __ \ /. .. . [__)/ ` >< \|\/\|\|\/\| \| \\__./ \\| \|\| \|
Comment	> Date sort = date in message > Arrival sort = internal imap date of message > sequence sort = straight numeric sort of sequence numbers (order in > which messages were added to the mailbox) > > Sequence sort needs to be default because it is the only reasonable > sort that can be done without parsing headers across all IMAP servers > > Arrival sort in IMP 4.x referred to sequence sort - arrival sort was > never defined in RFC 3501 but it makes sense that it is the arrival > order into the mailbox. Additionally, arrival/sequence sort (at > least in IMP) had the sequence numbers which clearly indicates the > sort was being done on sequence numbers (not that this means anything > to the average user). Then RFC 5256 goes and confuses thing but > defining a SORT ARRIVAL which sorts by internaldate. > > In IMP 5, to clean this up, do the following: > 1.) Rewrite Horde_Imap_Client to handle sequence sort - obtained > doing a SEARCH (not a SORT on imap servers that support the latter) > and then doing numeric sorting on the client side. > 2.) IMP defaults to sequence sort for same reason as in IMP 4.x. > 3.) Only display one type of date search in mailbox headings. > Determining whether this does a Header Date or an Internaldate search > is left to a preference, locked by default. By default, resort to > Internaldate (since this tends to be more accurate than the Date > header - see, e.g., Spam headers dated way in the future/past). > 4.) Determine how to allow user to resort back to sequence sort. > Call this sort "no sorting'.
Attachment
Watch this ticket

Saved Queries