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 777988 - Reply listed before the mail it replied to
Reply listed before the mail it replied to
Product: geary
Classification: Other
Component: conversations
Other Linux
: Normal enhancement
: ---
Assigned To: Geary Maintainers
Geary Maintainers
Depends on: 792388
Reported: 2017-01-31 15:04 UTC by Thomas Leberbauer
Modified: 2021-07-05 13:28 UTC
See Also:
GNOME target: ---
GNOME version: ---

Description Thomas Leberbauer 2017-01-31 15:04:14 UTC
A mail I sent (Date: Tue, 31 Jan 2017 15:23:24) appears below the reply (Date: Tue, 31 Jan 2017 15:23:07) I got to it. 

Geary should use the headers Message-ID and In-Reply-To (, if available, to order mails correctly. The Date header isn't reliable enough.
Comment 1 Michael Gratton 2018-01-09 23:50:27 UTC
Hmm, this is a good idea, thanks for the suggestion.
Comment 2 Michael Gratton 2018-01-09 23:56:28 UTC
This comment from Bug 713319 might be worth looking into:

> Updated by Tiago Quelhas 11 months ago
> JWZ's algorithm [1] is worth taking a look for this, as it is the _de facto_
> message threading algorithm for MUAs. It threads primarily based on References
> /In-Reply-To headers, but also includes a fallback heuristic based on subject
> lines. Obviously, Geary doesn't really need to know the nesting order of
> messages within a conversation, so the full algorithm isn't required; but we
> could use the part concerned with identifying which messages belong to the
> same conversation.
> [1]
Comment 3 GNOME Infrastructure Team 2021-07-05 13:28:30 UTC
GNOME is going to shut down in favor of
As part of that, we are mass-closing older open tickets in
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version, then please follow
and create a new ticket at

Thank you for your understanding and your help.