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 742568 - Geary groups all Google Voice messages into a single conversation.
Geary groups all Google Voice messages into a single conversation.
Status: RESOLVED DUPLICATE of bug 713319
Product: geary
Classification: Other
Component: conversations
Other Linux
: Normal normal
: ---
Assigned To: Geary Maintainers
Geary Maintainers
Depends on:
Reported: 2015-01-08 04:17 UTC by unlimitedbacon
Modified: 2015-01-22 02:40 UTC
See Also:
GNOME target: ---
GNOME version: ---

Message 1 (2.06 KB, text/plain)
2015-01-10 22:39 UTC, unlimitedbacon
Message 2 (2.05 KB, text/plain)
2015-01-10 22:43 UTC, unlimitedbacon
Message 3 (2.07 KB, text/plain)
2015-01-10 22:44 UTC, unlimitedbacon

Description unlimitedbacon 2015-01-08 04:17:31 UTC
I am using Geary 0.8.3 on Arch Linux. I have Google Voice setup to forward all SMS messages to me as emails. Geary has for some reason decided to group all of these messages into a single gigantic conversation, even though each message comes from a unique address and has a unique subject line. Google generates a new random email address for each phone number it receives an SMS from. 

Example address:

Example subject:

SMS from Dave [(555) 987-6543]
Comment 1 Jim Nelson 2015-01-08 19:55:18 UTC
Geary groups conversations sole by their Message-ID, which is a common way to thread emails together.

In Geary, each email in a conversation has a dropdown menu on the top-right corner.  If you select "View Source", there are some header values that are of interest to Geary:


Could you either attach to this ticket the source of a few of these messages, or at least the above values for each?
Comment 2 unlimitedbacon 2015-01-10 22:39:59 UTC
Created attachment 294249 [details]
Message 1
Comment 3 unlimitedbacon 2015-01-10 22:43:46 UTC
Created attachment 294250 [details]
Message 2
Comment 4 unlimitedbacon 2015-01-10 22:44:50 UTC
Created attachment 294251 [details]
Message 3
Comment 5 unlimitedbacon 2015-01-10 22:45:30 UTC
I have included the source for messages from 3 different people.
Comment 6 Jim Nelson 2015-01-12 23:01:24 UTC
All three have the same References: Message-ID: <>  This causes Geary to group all three into the same conversation.

I don't use Google Voice.  Are there any Settings that allow for you to change how emails are threaded, a setting regarding Message-ID or References?
Comment 7 unlimitedbacon 2015-01-13 02:54:07 UTC
No. Also, I should say that gmail has no trouble separating these conversations.
Comment 8 Jim Nelson 2015-01-13 03:34:02 UTC
> Also, I should say that gmail has no trouble separating these
> conversations.

Well, sure, both are Google products.  If Google didn't want these messages to be grouped into the same thread of discussion, it should assign them different Message-IDs to make the distinction.

Have you looked at these messages in Evolution or Thunderbird?  What do they look like?
Comment 9 unlimitedbacon 2015-01-13 03:49:14 UTC
Thunderbird also fails to group them properly, but its behavior is different from Geary. It has them grouped correctly until sometime in September 2014, and from then on they are grouped into many random conversations.
Comment 10 Jim Nelson 2015-01-22 02:40:09 UTC
Without going too deeply into the minutae of each message and its follow-ups, this is related to bug #713319, which is about adding some intelligence to our conversation sorting algorithm.  Specifically, to look at the Subject and Sender and attempt to discern if a message is part of a conversation even if Message-IDs are missing.

The only issue with this is that Message-IDs are not missing, so to fix it would mean ignoring them and placing more emphasis on these other fields.

I'm marking this as a duplicate of that ticket and adding a note there about this.

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