After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 722713 - The conversation is sorted by the Received Date not by the header Date
The conversation is sorted by the Received Date not by the header Date
Status: RESOLVED DUPLICATE of bug 714802
Product: geary
Classification: Other
Component: conversations
0.4.2
Other Linux
: Normal normal
: ---
Assigned To: Geary Maintainers
Geary Maintainers
Depends on:
Blocks:
 
 
Reported: 2014-01-21 16:41 UTC by kurt.haribo
Modified: 2014-01-23 01:40 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description kurt.haribo 2014-01-21 16:41:42 UTC 
The conversation list sort the message by the received date and not by the header Date.

When I move old local messages to my imap account, the old messages appear on the top of the list which is weird.
Comment 1 Jim Nelson 2014-01-23 01:40:09 UTC 
> The conversation list sort the message by the received date and not by the
> header Date.

This is by design, otherwise there are normal situations where a user receives a new message and it doesn't appear at the top of the list.  This caused confusion.

> When I move old local messages to my imap account, the old messages appear on
> the top of the list which is weird.

I believe you're seeing a duplicate of bug #714802.  Another of our users had an email folder with messages copied over from an old account.  The date-received for those messages reflected the order they were copied, not their original sender's date.

We don't believe this to be a widespread problem (but I do wish utilities that move mail from server to server would replicate the IMAP INTERNALDATE, which is exposed in the protocol).  Still, the other ticket remains open so we might consider a future solution.

*** This bug has been marked as a duplicate of bug 714802 ***