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 713613 - Recognise "R:" as a valid reply prefix
Recognise "R:" as a valid reply prefix
Product: geary
Classification: Other
Component: engine
Other All
: Normal normal
: ---
Assigned To: Geary Maintainers
Geary Maintainers
Depends on: 713319
Reported: 2013-07-08 06:17 UTC by Geary Maintainers
Modified: 2021-07-05 13:24 UTC
See Also:
GNOME target: ---
GNOME version: ---

geary-message-0X4TZW.txt (1.45 KB, text/plain)
2013-07-08 20:44 UTC, Geary Maintainers

Description Charles Lindsay 2013-11-21 20:21:19 UTC

---- Reported by geary-maint@gnome.bugs 2013-07-08 11:17:00 -0700 ----

Original Redmine bug id: 7211
Original URL:
Searchable id: yorba-bug-7211
Original author: Andrea Corbellini
Original description:

For reasons I will never understand, some Italian webmail providers use "R:"
instead of "Re:" for replies and do not include In-Reply-To headers.

This means two things:

1. messages of the same conversation are non grouped correctly;

2. if I don't take action, the subject soon becomes "Re: R: Re: R: Re: R:

So far, I have never found an email client that handles "R:" correctly (except
Gmail, which groups conversations but still prepends "Re:" when replying).
Geary perhaps could be the first client to solve this annoying problem.

Related issues:
related to geary - 5096: Geary sometimes fails to group related messages
into a si... (Open)

---- Additional Comments From geary-maint@gnome.bugs 2013-09-17 15:53:00 -0700 ----

### History



Updated by Andrea Corbellini 5 months ago

  * **Description** updated (diff)



Updated by Jim Nelson 5 months ago

  * **Category** set to _engine_

If they don't use `In-Reply-To`, then they must supply a `References` field
for Geary to organize them into a conversation. Can you verify that is the



Updated by Andrea Corbellini 5 months ago

  * **File** geary-message-0X4TZW.txt added

There's no such field. By the way, I'm attaching the full headers from a
message I received recently.



Updated by Jim Nelson 5 months ago

  * **Tracker** changed from _Bug_ to _Bite-sized_
  * **Target version** set to _0.4.0_

That's ... unfortunate. It means Geary will need improved heuristics (#5096)
to take a reply from this mail service and add it to the right conversation.

We might be able to fix the "R:" problem fairly easily, however, so I'll mark
this as a bite-sized for 0.4. The larger problem of In-Reply-To will have to
wait for #5096.



Updated by Jim Nelson 3 months ago

  * **Keywords** set to _string-change_



Updated by Jim Nelson 2 months ago

  * **Target version** changed from _0.4.0_ to _0.5.0_

--- Bug imported by 2013-11-21 20:21 UTC  ---

This bug was previously known as _bug_ 7211 at
Imported an attachment (id=260748)

Unknown milestone "unknown in product geary. 
   Setting to default milestone for this product, "---".
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.
Resolution set on an open status.
   Dropping resolution 

Comment 1 Federico Bruni 2018-01-16 16:54:27 UTC
I've received emails with "Ris:" in subject, which are correctly threaded in a conversation in Geary as they have both References and Message-Id in the headers.
Comment 2 GNOME Infrastructure Team 2021-07-05 13:24:08 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.