[Tickets #10967] Re: Wrong sorting by date in IMP

[bugs at horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/10967
------------------------------------------------------------------------------
  Ticket             | 10967
  Updated By         | cernik at fel.cvut.cz
  Summary            | Wrong sorting by date in IMP
  Queue              | IMP
  Version            | 5.0.17
  Type               | Bug
  State              | Not A Bug
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             | Horde Developers
------------------------------------------------------------------------------


cernik at fel.cvut.cz (2012-05-29 20:42) wrote:

>> I think that you can't rely on UID anymore :(
>
> Of course you can.
>
> *Please* read RFC 3501. The definition of UIDs (Section 2.3.1.1):
>
> ...Unique identifiers are assigned in a strictly ascending fashion  
> in the mailbox; as each message is added to the mailbox it is  
> assigned a higher UID than the message(s) which were added  
> previously...

Yes. It's RFC. I spoke about bug in thunderbird which change uid of  
mails. It takes some mails (not all -  forexample 900 from 2200).

First step, it delete msg.
Second step, it add deleted msg back and msg have new - higher uid.

Is't prohibited by any RFC?

forexample:

-rw------- 1 root root     1966 2012-05-29 10:34:35.000000000 +0200 17034.
-rw------- 1 root root     1755 2012-05-29 10:20:36.000000000 +0200 17033.
-rw------- 1 root root    72072 2012-05-29 09:48:14.000000000 +0200 17032.
-rw------- 1 root root     3190 2012-05-28 23:08:04.000000000 +0200 17031.
-rw------- 1 root root  7058824 2012-05-28 18:56:39.000000000 +0200 17030.
-rw------- 1 root root   909212 2012-05-28 18:20:08.000000000 +0200 17029.
-rw------- 1 root root    60816 2012-05-28 18:03:39.000000000 +0200 17028.
-rw------- 1 root root    51626 2012-05-28 15:56:00.000000000 +0200 17026.
-rw------- 1 root root    52181 2012-05-28 15:04:31.000000000 +0200 16186.
-rw------- 1 root root    59747 2012-05-28 14:41:16.000000000 +0200 16187.
-rw------- 1 root root     2230 2012-05-28 10:19:54.000000000 +0200 16189.
-rw------- 1 root root    80081 2012-05-28 10:17:30.000000000 +0200 16182.
-rw------- 1 root root     4904 2012-05-28 09:58:57.000000000 +0200 16188.
-rw------- 1 root root    54790 2012-05-28 09:32:07.000000000 +0200 16190.
-rw------- 1 root root     3407 2012-05-28 09:09:37.000000000 +0200 16193.
-rw------- 1 root root     2341 2012-05-28 08:59:45.000000000 +0200 16192.
-rw------- 1 root root    42263 2012-05-28 08:52:39.000000000 +0200 16191.
-rw------- 1 root root     5841 2012-05-28 08:22:53.000000000 +0200 16198.
-rw------- 1 root root     3423 2012-05-28 08:13:12.000000000 +0200 16197.
-rw------- 1 root root    16184 2012-05-28 08:00:07.000000000 +0200 16196.
-rw------- 1 root root     7166 2012-05-26 23:19:37.000000000 +0200 16195.
-rw------- 1 root root    11320 2012-05-25 17:01:20.000000000 +0200 16194.
(i set time under time of mails .. in the fact hundreds mails have  
same time but then is hard ilustrate problem)

If you sorting these mails under uid then you get only mess.

Thunderdird and Outlook doesnt have this kind of problem cuz they are  
sorting under time and not under uid. It's not bug in horde algo.  
Horde isnt immune to this kind of problem and change sorting under  
time and not under uid will make horde better - it will make horde  
immunne to thunderbird crap :).  Sorting under time have no hole.  
Under uid obviously have :(.