Ticket #1485936 (closed Feature Requests: fixed)

Opened 15 months ago

Last modified 11 months ago

Sort by order received

Reported by: hippo Owned by:
Priority: 5 Milestone: 0.3.1
Component: Core functionality Version: svn-trunk
Severity: normal Keywords:
Cc:

Description

Is it possible to make clicking on a columns header cycle through three stages? Some of the SPAM I get has fake date headers that result in them being displayed half way down my mailbox. I remember some mail readers having three sort orders:

  • Date ascending
  • Date descending
  • Unsorted (but it's the order the messages are in the mailbox)

Failing that is it possible to add the IMAP server index as a column?

Attachments

sort_on_arrival.diff (3.6 KB) - added by corbosman 15 months ago.
sort on arrival patch

Change History

Changed 15 months ago by corbosman

sort on arrival patch

Changed 15 months ago by corbosman

  • version changed from 0.2.1 to svn-trunk
  • milestone changed from later to 0.3-stable

I have made a patch to make this user-configurable, which you can of course make global by adding it to dont_override. Im hoping this can get added to core.

Personally I think this is a better way to deal with it than having 3 states in the sort column, from a server-side perspective. Sorting on date can have a serious impact on IO on the imap server, so it may be much better to sort on arrival (ie: unsorted). I think that if you allow for 3 states, most people will not choose the unsorted state. By making this a config setting instead most people wont change it. But i understand if people think differently and make this a 3 state column instead.

Changed 15 months ago by corbosman

This patch is unfortunately not complete, i didnt think about database caching (which we dont use). So better not apply it.

Changed 15 months ago by tensor

I like the idea and also hate this spamming date trick. Corbosman, please do not abandon the patch.

Changed 14 months ago by alec

  • milestone changed from 0.3-stable to later

Changed 11 months ago by alec

  • status changed from new to closed
  • resolution set to fixed
  • component changed from User Interface to Core functionality
  • milestone changed from later to 0.3.1

Implemented in r2983.

Note: See TracTickets for help on using tickets.