[Tickets #12139] Re: Sort by message date broken starting with horde_imap_client 2.7.0

noreply at bugs.horde.org noreply at bugs.horde.org
Tue Mar 26 00:01:46 UTC 2013


DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/12139
------------------------------------------------------------------------------
  Ticket             | 12139
  Updated By         | Michael Slusarz <slusarz at horde.org>
  Summary            | Sort by message date broken starting with
                     | horde_imap_client 2.7.0
  Queue              | Horde Framework Packages
  Version            | Git master
  Type               | Bug
  State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2013-03-25 18:01) wrote:

Unfortunately, those IMAP logs are useless because:
1. They weren't output by IMP.
2. You are sorting two different mailbox states (one has 782 messages  
in it, one has 785 messages).

I still think what you are seeing is the result of a problem in IMP -  
namely that it was impossible to switch to the non-default datesort in  
dynamic view (it would just display the same as the default datesort).  
  This has been fixed for IMP 6.0.5.

If IMP was truly sending the correct sort type for message date  
searches, you should see something like:

C: 5 UID FETCH [...] (INTERNALDATE ENVELOPE)

However, your IMAP logs both show identical sort FETCHs:

UID FETCH [...] (INTERNALDATE)

which to me tells me that the calling application (IMP) is at fault.   
Although I am not sure why going back to 2.6.0 would fix since no sort  
changes were made between 2.6.0 -> 2.7.0 (unless you are using  
caching, which would explain the behavior).





More information about the bugs mailing list