Closed Bug 1380648 Opened 8 years ago Closed 8 years ago

One email is filed as a reply to another email in the conversation tree, although they are not related

Categories

(Thunderbird :: Folder and Message Lists, defect)

52 Branch
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: Daniel.Gerigk, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36 Steps to reproduce: I received two emails that are not at all related. Actual results: One of the two emails is incorrectly filed as a reply to the other one in the conversation tree, although there is no relation whatsoever between them. This can potentially lead to serious confusion, as it leads to some emails being hidden down the conversation tree of other emails. If you regularly collapse your conversation trees, then you risk overseeing some of your emails. Whenever Thunderbird is in doubt whether one email is a reply to another one, it should not assume that they are. Expected results: None of the two emails should be misinterpreted as a reply to the other.
By "conversation tree" you mean the "thread pane"? Or are you referring to the add-on Conversations? In general an e-mail can be displayed in the wrong thread if the internal references are incorrect. Can you please look at the message source (View > Message Source) and report the References of the incorrectly filed message as well as other messages in the same thread.
I do mean the "thread pane". It is a fresh install of Thunderbird, without any add-ons (except Lighning, which was preinstalled). What precisely do you mean by "references"? I did a text search on the term "refe" in the source of the mails, but did not find any occurrence.
What is also strange is that if I save the mails on my hard disk, and then import them, they are properly separated, i.e. none is regarded as a reply of the other one.
This is the source code of the first mail, slightly anonymized: Date: Thu, 13 Jul 2017 00:37:09 +0200 From: ___ ___ <___.___@gmx.de> To: ___@gmx.de Subject: ___ User-Agent: K-9 Mail for Android Message-ID: <2B7E2392-6146-44B8-A36D-60D37A71E616@gmx.de> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----LT7KIJLO0QE6ZAJ3DKIJAPTRUAFJBR" Content-Transfer-Encoding: 7bit X-Antivirus: Avast (VPS 170712-10, 12.07.2017), Inbound message X-Antivirus-Status: Clean ------LT7KIJLO0QE6ZAJ3DKIJAPTRUAFJBR Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable ___ --=20 Diese Nachricht wurde von meinem Android-Ger=C3=A4t mit K-9 Mail gesendet= =2E ------LT7KIJLO0QE6ZAJ3DKIJAPTRUAFJBR Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable ___<br> -- <br> Diese Nachricht wurde von meinem Android-Ger=C3=A4t mit K-9 Mail gesendet= =2E ------LT7KIJLO0QE6ZAJ3DKIJAPTRUAFJBR--
And this is the mail that is incorrectly classified as a reply to the first one: Return-Path: <m-4q1oxpr7yvw3z3km7658udr6pq93yplehix6elo2iawp0y3oiamt9ncz8fh@bounce.linkedin.com> Received: from maile-gc.linkedin.com ([108.174.0.195]) by mx-ha.gmx.net (mxgmx117 [212.227.17.5]) with ESMTPS (Nemesis) id 1MlePK-1dvsnX3KE6-00ijLX for <___.___@gmx.de>; Tue, 11 Jul 2017 09:23:42 +0200 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linkedin.com; s=proddkim1024; t=1499757820; bh=bZF6cfwYz/vA/I74nB51DIZ8oxk6bRQR19qQ06qqVCE=; h=From:Subject:MIME-Version:Content-Type:To:Date:X-LinkedIn-Class: X-LinkedIn-Template:X-LinkedIn-fbl; b=MrY/hiENZO7rSomwNA6S5InQffHxNHX3QSBJgH385vK9YaaNGD+VmwDmUACYLYs71 UfaAH+88rZb3q00p8zTaEVx/B6VajLf8VBz5ymQQ9t/WqpUVGUA9TWQGmCTj3xQJuJ S1YMdBHTRXFiQhO8NgcwPHbeU0aVgIekTENqpEsk= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=maile.linkedin.com; s=proddkim1024; t=1499757820; bh=bZF6cfwYz/vA/I74nB51DIZ8oxk6bRQR19qQ06qqVCE=; h=From:Subject:MIME-Version:Content-Type:To:Date:X-LinkedIn-Class: X-LinkedIn-Template:X-LinkedIn-fbl; b=V1/jD+QJt2ZQEHZfirHe5zyu9MlG0A00mfIRqhb1do+mbfErVVpviNxKQhTyvyJjQ UsmDFobq19wlNZkq6nyG3YGgAc6QQVfpVhg4yU7o5v1ofrhuhxEP4JTVgagXHKsuhN 0PFy1P42KTU7pIuXbhyUZXr1B5fzlNdFNXs4isJI= From: LinkedIn <notifications-noreply@linkedin.com> Message-ID: <816866129.3293929.1499757820132.JavaMail.app@lor1-app5274.prod.linkedin.com> Subject: ___ MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_3293927_496975332.1499757820129" To: ___ ___ <___.___@gmx.de> Date: Tue, 11 Jul 2017 07:23:40 +0000 (UTC) X-LinkedIn-Class: EMAIL-DEFAULT X-LinkedIn-Template: what_you_missed_v2 X-LinkedIn-fbl: m2-at002sg2524obapwwwfmwjksq7mbteklzsrxypf3048pd2czpjlprqwmwa2o6sgztq8hwv008cfpnjbydohfjtfyl7cx2sbz3na05h X-LinkedIn-Id: 6uwu6z-j4yyxqz4-m List-Unsubscribe: <___> Require-Recipient-Valid-Since: ___.___@gmx.de; Sat, 4 Apr 2015 19:59:13 +0000 Envelope-To: ___.___@gmx.de> X-GMX-Antispam: 0 (Mail was not recognized as spam); Detail=V3; X-GMX-Antivirus: 0 (no virus found) X-UI-Filterresults: notjunk:1;V01:K0:TIcFt+JOKBU=:MNmEv8a1ue0AbbTxTPyZ2Q4DnM Eqr/N0gPiwKWde16E1iHQS1YOENRK/FQOLBq907LsvdoiSEnMLJOpD4sqgODwKSmg+kUscnGw dIVJX7W3Mml9J+Qmud1otN5cDIuq6V4zshppAo3V6FLtI/x/G3VifSHEBXT/QE13520lvOpcR vHfWAnC+bhU+JqrjOGvIpJv6WiCIuwCXOg9MUagJVAYPxS4gPqzmKQh9fOdxC1lfHPu0KNa2L AUp39U5HY2r+ZKB69COWmZjfYGPioDC0QG4xfLnHZFttxZVOQV4GWQiNPi4gOf0Ow8ZYvEVf6 0vOUdQSu1U1x8LFA6d2iUwMqZGM6uG1usUMHSVaHpH8FXOESsrQB93Do+n2VuQLZFTAFoI7G9 MIy2mz2qPIwXJ3UKzbn9pRft2lHEjKreWb4XN2gzAkKZ3QlArcPQJthAkPNtreEW/YUEPwlna VCAdcvwifaNd3IlZMfJnc9tHhvkdKqtX+1KZ0Jc4i0GwrI1GomFPGke9jxPMCAB2qvloFHaZD 7p+HVsY277kEcZ1OskuXWI0k0YY6zcYNRxtiwqlk4j8MqTuYK3QKdTIgqVh0Gts2W+lZ5pk6c SZprV7sLGkgeNOfeL/BNBsYjFSF5XzHV4B60Q6PwAEqYc/7m+YzzPTQ3PNvtTv9joeD5xqT5m Fzfi9fLYTxwGcFkdOpyqYVpYTFPv5mDbWI8TuhjmZOpuKGbxCoR69LDE50EtGBTjzclen+I7X NpNxspnqWioxuXOQDUW/CsfouQYP9QafE888b6+QvitXBcOoWBGLa9RwSC94pyBqd1uda4HuU N8bessdxf536552fRgDl+LZp43OT1/341AGzFX9R94dGVvafDkJxzNsk8PuCJpFvUeEPkjN3F zzkIVWrB/2FaEeHefwvP+MXb61k5BPocAnbNcj8fKdh75uHp6eb/BDVsvDxs8oe0cwf/UzY5X m4hekseRDvr41nuZG9Zh6/hSsB0HYd+VL24M3910TKHLaCCjCgWKPwTBPWx+4t5rZT7idbwSO 8VM3eE9paQYOlMBUnX8R4VygRnz03vMrlaMN/6d6mv624zXWy/ppflAysab7Q9FuRReikF+47 AT2ZU1XE075Yiae2r64GefOh4A3uJrLDrZYJ7dGfC+lDXDwNZ3pFJPJ0sKPcWPkKaAK4YXpD5 MTwndZUgA4biZgojRYasstcgAM6860NO+8i+PHHvK6iSze3Fx+3tKXTXzkcSWHe1T4/wIpbzS 4tv3ElI3UD266ubL7Te8sWG220qmvV6g8aQdebfwY7nIr7JohdMpoV3A+y5j08WZImKPnk+DM VFF5RcY+LbdkPbaSGC54Sff5g3tsQl/o3qlrs4i9Zku7i6FVS3SGpeqrzue3b4udl+ex6NVf0 QmpycH0PkyQKT9IKsyNj3lvzuPWYhmhcixZX8K9jNdy1g4siFP0TgGpSJZnk11j5dUk7R9Esk hmS8k1Kbd/7KiaY7c2wJjOsf4XpXVHjrDcR3OQ256SrGPnL5o64Aq7pngS0qOfa6PveF0b5aB yCJjk3HmhSXII9eTDQWR6ExJlb2AZwDQt0fEcOMaOFZpX1T80hBeol3bMcNmVtjr14at4+v8d sLec+oUOQuVO+QMBAFJYhCm8pHFQZX/JpGIDF0DgAU0eumsuKZurhJUwHry1iLXJ+hH4Bwu8Y 2TtY8LS7+p3iiVAbCsLOj1TEwY1nua6I4lw8In3qoy9HksAIDeLgZGlq+p16Te56Mk= X-Antivirus: Avast (VPS 170713-6, 13.07.2017), Inbound message X-Antivirus-Status: Clean ------=_Part_3293927_496975332.1499757820129 Content-Type: text/plain;charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-ID: text-body ___ See what's new >=20 ___ =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =C2=A9 2017 LinkedIn Ireland Unlimited Company. LinkedIn, the LinkedIn logo= , and InMail are registered trademarks of LinkedIn Corporation in the Unite= d States and/or other countries. All rights reserved. You are receiving Activity You Missed emails. Unsubscribe here: https://www= .linkedin.com/e/v2?e=3D6uwu6z-j4yyxqz4-m&t=3Dlun&midToken=3DAQFPp_f7RAPu-g&= tracking=3Deml-gro-wym-unsub&ek=3Dwhat_you_missed_v2&loid=3DAQF8ss6xmQBUwgA= AAV0wiDislEfNxbPZeIwmjiLqAQgtFrJy3KdUkO_m1eT0I246R7RWkZ6CjJ1Bdpal3ZMvBk4&ei= d=3D6uwu6z-j4yyxqz4-m This email was intended for ___ ___ (___).=20 Learn why we included this: https://www.linkedin.com/e/v2?e=3D6uwu6z-j4yyxq= z4-m&lipi=3Durn%3Ali%3Apage%3Aemail_what_you_missed_v2%3BTrth48PYTES7mzoMTW= C8yQ%3D%3D&a=3DcustomerServiceUrl&midToken=3DAQFPp_f7RAPu-g&ek=3Dwhat_you_m= issed_v2&articleId=3D4788 ------=_Part_3293927_496975332.1499757820129 Content-Type: text/html;charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-ID: html-body <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.= w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns=3D"http://www.w3= .org/1999/xhtml" style=3D"-webkit-text-size-adjust:none;"> ___ </html> ------=_Part_3293927_496975332.1499757820129--
Thanks for looking into this! Thunderbird rocks!
I forgot to mention: the first mail in this specific case was >outgoing<. But I did also observe this phenomenon in cases where both mails were incoming.
Perhaps one thing might be relevant: in a conversation thread, I sometimes delete some of the mails within the thread to keep the tree small. Sometimes I even delete all mails in a tree except the most recent reply. Could this lead to Thunderbird getting confused?
References: is an e-mail header that you can see in the message source, for example, every BMO mail has: References: <bug-1380648-176914@https.bugzilla.mozilla.org/> In the messages you published, I can't see any such headers. Given that the threading is correct when you import (comment #3), it would be best if you could provide me with the mailbox that shows the problem. As this will contain personal details, Zip up the mailbox file and send it to me as attachment in a private message (view my profile to see the e-mail address). I will try to look into the issue when I find the time. Have you tried repairing the mailbox? Right-click, Properties, "Repair Folder".
I forgot to mention that the mails are actually in a GMX account, if that matters, not in the "local folder" of Thunderbird. Repairing the folder worked. But of course, that can not be the solution of the problem.
(In reply to Daniel from comment #10) > Repairing the folder worked. But of course, that can not be the solution of > the problem. That *is* the solution of the problem. We can't track down any small glitch which you have now eliminated by repairing the folder. Sorry.
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Resolution: --- → INVALID
But this problem occurs regularly, and is not just cosmetical. It diminishes my trust in Thunderbird to organize my mails properly. Actually, I would say this problem is even moderately critical.
OK, when you have a reproducible case, we can reopen the bug, no problem. It makes a little harder that the folder in question is an IMAP folder, but I guess you could still zip up the local copy.
It's impossible for me to reproduce this bug actively, because I have no idea what causes it; but it does occur from time to time. Of course, I could turn off the "thread tree" feature, but if possible I would like to keep using it. I did zip up my local Thunderbird profile, but your mail server did not let it through.
You need to log in before you can comment on or make changes to this bug.