Conversations with wrong messages in them

Em is gathering messages into a conversation that are unrelated to that conversation. They have the same subject line but thats all, gmail shows them as 2 separate conversations, there is almost a years time gap between them as well.

eM Client uses header information like Message-ID, In-Reply-To, References as well as Subject to combine messages into a conversation.

Maybe they share some of these headers.

It may also be some corruption in your IMAP message cache. If this is a Gmail account setup in eM Client, right-click on the All Mail folder and choose Properties > Repair.

It would appear that it must be using Microsofts broken Thread-Topic: header field to join these together into one thread. The emails do contain correct References: and In-Reply-To: fields.

Gmail correctly displays them in 2 seperate conversations.
Outlook for Mac also displays these 2 conversations correctly.
Thunderbird incorrectly splits them into 3 conversations - but this is preferable to having them incorrectly conflated.

Having EmClient conflate these 2 seperate conversations is a real pain in the arse as it makes it difficult to find the one of the conversations - its not in the correct place time-wise when browsing for it, nor does it appear to have the correct email recipients on it.
The only solution is to turn conversations off 

The following are snippets of headers of the 5 emails involved:

Thread 1

Msg 1

Delivered-To: hodges.peter@gmail.com
Received: by 10.2.148.143 with SMTP id x15csp2961128jah; Mon, 9 Oct 2017 17:29:50 -0700 (PDT)
Return-Path: <martino@gerkislabs.com>
From: Martin Oxley <martino@gerkislabs.com>
To: “hodges.peter@gmail.com” <hodges.peter@gmail.com>
Subject: RE: Touching Base
Thread-Topic: Touching Base
Thread-Index: AQHTPvZdgy0qJskxNkKNQNBWL/7BK6LcChCA
Date: Tue, 10 Oct 2017 00:29:41 +0000
Message-ID: <SYXPR01MB070362F41D6C89451AB9B2DCCA75…>
References: <CY4PR14MB1494A738CA644D757967B8A59771…>
In-Reply-To: <CY4PR14MB1494A738CA644D757967B8A59771…>

Msg 2

Delivered-To: hodges.peter@gmail.com
Received: by 10.2.148.143 with SMTP id x15csp1245409jah; Wed, 11 Oct 2017 16:27:24 -0700 (PDT)
Return-Path: <martino@gerkislabs.com>
From: Martin Oxley <martino@gerkislabs.com>
To: “hodges.peter@gmail.com” <hodges.peter@gmail.com>
Subject: FW: Touching Base
Thread-Topic: Touching Base
Thread-Index: AQHTQsa1T0IJpfIbekCCV3+/tDZ/pqLfFu4wgAA0cIA=
Date: Wed, 11 Oct 2017 23:27:17 +0000
Message-ID: <SYXPR01MB0703ABCEDCCC15C91DC7E13CCA4A…>
References: <MWHPR14MB110101165F80A2A14D9A8B54974A…> <SYXPR01MB070376AB82B9954B129DA483CA4A…>
In-Reply-To: <SYXPR01MB070376AB82B9954B129DA483CA4A…>

Msg 3

Delivered-To: hodges.peter@gmail.com
Received: by 10.2.148.143 with SMTP id x15csp1973225jah; Sun, 29 Oct 2017 16:12:31 -0700 (PDT)
Return-Path: <martino@gerkislabs.com>
From: Martin Oxley <martino@gerkislabs.com>
To: Stuart Maskell <smaskell@nwtech-services.com>
Subject: FW: Touching Base
Thread-Topic: Touching Base
Thread-Index: AQHTQsa1T0IJpfIbekCCV3+/tDZ/pqLfFu4wgBx53/A=
Date: Sun, 29 Oct 2017 23:12:27 +0000
Message-ID: <SYXPR01MB0703814CFB859FC1E5EAE48ECA58…>
References: <MWHPR14MB110101165F80A2A14D9A8B54974A…> <SYXPR01MB070376AB82B9954B129DA483CA4A…>
In-Reply-To: <SYXPR01MB070376AB82B9954B129DA483CA4A…>

=============================================================

Thread 2

Msg 1

Delivered-To: hodges.peter@gmail.com
Received: by 2002:a81:760e:0:0:0:0:0 with SMTP id r14csp4725386ywc; Mon, 23 Mar 2020 16:22:00 -0700 (PDT)
Return-Path: <allan.h.dawson@gmail.com>
References: <CA+DP06BqpROOOs3jZQriGOUuc9bOcpu8bOyP…>
In-Reply-To: <CA+DP06BqpROOOs3jZQriGOUuc9bOcpu8bOyP…>
From: Allan Dawson <allan.h.dawson@gmail.com>
Date: Tue, 24 Mar 2020 12:19:25 +1300
Message-ID: <CA+DP06AF9kSbsPZEG0EkxbB6b6Wx6NcDCDvQ…>
Subject: Fwd: Touching Base
To: “Martin (aka Muzzle) Oxley” <martino@gerkislabs.com>, Peter Hodges
 <hodges.peter@gmail.com>, “Mike Chisholm (mikejchisholm@gmail.com)”
 <mikejchisholm@gmail.com>
 
Msg 2
 
Delivered-To: hodges.peter@gmail.com
Received: by 2002:a81:760e:0:0:0:0:0 with SMTP id r14csp4737004ywc; Mon, 23 Mar 2020 16:37:11 -0700 (PDT)
Return-Path: <martino@gerkislabs.com>
From: Martin Oxley <martino@gerkislabs.com>
To: Allan Dawson <allan.h.dawson@gmail.com>, Peter Hodges
 <hodges.peter@gmail.com>, “Mike Chisholm (mikejchisholm@gmail.com)”
 <mikejchisholm@gmail.com>
Subject: RE: Touching Base
Thread-Topic: Touching Base
Thread-Index: AQHWAWnd/QcJ0ajZ5kyhVRoacgQKX6hW1Dvg
Date: Mon, 23 Mar 2020 23:37:04 +0000
Message-ID: <SYBPR01MB3306204D616CA6066DB58863CAF0…>
References: <CA+DP06BqpROOOs3jZQriGOUuc9bOcpu8bOyP…>
 <CA+DP06AF9kSbsPZEG0EkxbB6b6Wx6NcDCDvQ…>
In-Reply-To: <CA+DP06AF9kSbsPZEG0EkxbB6b6Wx6NcDCDvQ…>

Sorry post mangled the IDs, but I can supply them if anybody is interested.
I have plenty of examples including another that has gathered 14 seperate conversations (37 emails) spanning 7 years into a single conversation.

This is clearly broken as multiple other mail clients don’t exhibit this behaviour.

What version of eM Client are you using?

7.2.38732.0 recently (about 1 week ago) clean installed.
Have also done a repair to see if that fixed anything - it didn’t.

Thread 2 is definitely a conversation
Msg 2 references Msg 1.

Thread 1 is also a conversation as Msg 1, 2 and 3 all reference the same Thread-topic
Also, Msg 2 and Msg 3 both reference the same message, so they are a conversation

Agreed - the References: and In-Reply-To: fields match up nicely - 2 seperate conversations of 2 msgs and 3 msgs.

Unfortunately EmClient shows them as 1 conversation of 5 msgs.

I hope Emclient isn’t using Thread-topic:  the Thread-topic: / Thread-Index pair should be completely ignored, it was an early attempt by Microsoft to support conversations, but because it doesn’t guarantee a unique Thread-topic per conversation its fundamentally flawed. As far as I can tell most modern clients including Microsofts support References: and In-Reply-To:

If you include the Thread header as well, then they do all make a conversation, but I really don’t know if eM Client uses the Thread header though it appears that it does. That would be something to ask the developers, so if you have a Pro License, you could open a support ticket and ask them.

It is hard to diagnose what exactly happened without the access to the actual messages. However latest betas of eM Client 8 now sync conversation data from Gmail (on Google accounts) so they should now be in a perfect sync between eM Client and Gmail interface. Maybe you can try that. In of the latest beta we added a mechanism that all the older conversations are updated to mirror conversation threads shown on Gmail.

Can reproduce at will now. Just need two gmail accounts X@gmail.com & Y@gmail.com

X sends to Y a new msg subject “test”

X sends to X a new msg subject “test”

X fwds the msg that it just received to Y

Connect EmClient to account Y it will put the 2 msgs in 1 conversation,  gmail will treat them correctly as independent e.g. two conversations.

So Michal commented below that the beta is now correctly showing these for Google accounts. Can you update to the beta by downloading from the Release History and see if there is any difference?

Upgraded to 8.0.1796.0 this appears to have fixed all the conversations - excelllent.

Thanks guys.