On Mon, Feb 11, 2019, at 9:55 AM, Marvin Gülker wrote:
Am 11. Februar 2019 um 19:47 Uhr +0200 schrieb Danil Smirnov:
What could be a reason of HyperKitty failing to create a thread from chained emails?
For example, see "RECENTLY ACTIVE DISCUSSIONS" on page https://email@example.com/
"Openvpn and Network mapping" discussion displayed as five threads instead of only one...
This looks exactly like the problem I have been experiencing, see https://firstname.lastname@example.org/thread/CX2R7GF2B37PS5MCYHTFYGNLI6O7M7YN/
Any ideas how to improve HyperKitty ability to detect threaded messages?
Sadly, no. Let's hope the problem gets resolved.
Please create a bug report at https://gitlab.com/mailman/hyperkitty/issues with the affected messages.
It would help us recreate the problem if you could attach a raw messages in the issue. I am assuming the messages aren't sensitive since the archive are open. Otherwise, feel free to omit any sensitive information.
I haven't looked at the threading code in HK since a long time, but my impression is that it looks at the 'In-Reply-To' header to figure out if the current email is a response to a previous email that it received.
In some cases, the order of the incoming messages can cause this to break, like when the reply comes in first and the original messages comes in later. I am not sure exactly what is happening here, but looking at the raw messages should help us reproduce and possibly fix the issue.