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

[noreply at bugs.horde.org]

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              | Unconfirmed
+State              | Feedback
-Priority           | 2. Medium
+Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


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

Can't reproduce.

Now there is something funny going on with **IMP** - in that it seems  
to be sending arrival sorts when date sorting is explicitly selected:

C: 3 UID SORT RETURN (ALL COUNT) (ARRIVAL) US-ASCII ALL
S: * ESEARCH (TAG "3") UID ALL  
37309,44536,46010:46011,46472,46720,46800,46816 COUNT 8
S: 3 OK Sort completed (0.000 secs).

It looks like an issue where the explicit sort is not overriding the  
default date sort set in prefs.

But unless someone can prove otherwise, this doesn't seem to be an  
issue within Horde_Imap_Client.  At a minimum I will need an IMAP log  
showing a problem.



To further debug this issue, we need details of the IMP -> IMAP/POP  
communication.

To enable debugging, see instructions contained in  
imp/config/backends.php (the 'debug' config parameter).

Debugging should not be enabled on a production server,   Attach/post  
only the portion of the log that directly deals with the problem  
reported (it may be simplest to clear the log file and then perform  
the event that causes the error).