Re: Possible some threads are not complete due to bug?

diff --git a/85/1d64543206b30c55e8da0a9eef9c19d6ed687d b/85/1d64543206b30c55e8da0a9eef9c19d6ed687d
new file mode 100644 (file)
index 0000000..0b3c2ab
--- /dev/null
+++ b/85/1d64543206b30c55e8da0a9eef9c19d6ed687d
@@ -0,0 +1,100 @@
+Return-Path: <david@tethera.net>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+ by arlo.cworth.org (Postfix) with ESMTP id ED2186DE19B7\r
+ for <notmuch@notmuchmail.org>; Sun,  4 Oct 2015 03:59:22 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at cworth.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: 0.104\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=0.104 tagged_above=-999 required=5 tests=[AWL=0.104]\r
+ autolearn=disabled\r
+Received: from arlo.cworth.org ([127.0.0.1])\r
+ by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024)\r
+ with ESMTP id StwmbIPFxSQt for <notmuch@notmuchmail.org>;\r
+ Sun,  4 Oct 2015 03:59:18 -0700 (PDT)\r
+Received: from gitolite.debian.net (gitolite.debian.net [87.98.215.224])\r
+ by arlo.cworth.org (Postfix) with ESMTPS id DCC3D6DE19AA\r
+ for <notmuch@notmuchmail.org>; Sun,  4 Oct 2015 03:59:17 -0700 (PDT)\r
+Received: from remotemail by gitolite.debian.net with local (Exim 4.80)\r
+ (envelope-from <david@tethera.net>)\r
+ id 1ZigzA-0002DM-Is; Sun, 04 Oct 2015 10:57:44 +0000\r
+Received: (nullmailer pid 8932 invoked by uid 1000); Sun, 04 Oct 2015\r
+ 10:57:25 -0000\r
+From: David Bremner <david@tethera.net>\r
+To: Xu Wang <xuwang762@gmail.com>\r
+Subject: Re: Possible some threads are not complete due to bug?\r
+In-Reply-To:\r
+ <CAJhTkNhp=mMPsD7hkGKW4eY9WWOuS2pf=x4sDiLnx9ref9JTew@mail.gmail.com>\r
+References:\r
+ <CAJhTkNh7_hXDLsAGyD7nwkXV4ca6ymkLtFG945USvfqK4ZJEdQ@mail.gmail.com>\r
+ <87fv2a4ctt.fsf@zancas.localnet>\r
+ <CAJhTkNgBdnm18UXC95ryJk5w7fJpa7-1LvdugV3S29fL4kxxhQ@mail.gmail.com>\r
+ <87zj0c3gei.fsf@zancas.localnet>\r
+ <CAJhTkNhp=mMPsD7hkGKW4eY9WWOuS2pf=x4sDiLnx9ref9JTew@mail.gmail.com>\r
+User-Agent: Notmuch/0.20.2+93~g33c8777 (http://notmuchmail.org) Emacs/24.5.1\r
+ (x86_64-pc-linux-gnu)\r
+Date: Sun, 04 Oct 2015 07:57:25 -0300\r
+Message-ID: <87oage9a0a.fsf@zancas.localnet>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain\r
+Cc: notmuch@notmuchmail.org\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.18\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+ <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
+ <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
+List-Archive: <http://notmuchmail.org/pipermail/notmuch/>\r
+List-Post: <mailto:notmuch@notmuchmail.org>\r
+List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
+List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
+ <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Sun, 04 Oct 2015 10:59:23 -0000\r
+\r
+Xu Wang <xuwang762@gmail.com> writes:\r
+\r
+>\r
+> $ notmuch search --output=threads "id:MYMSGID"\r
+> thread:000000000000a125\r
+> $ notmuch search --output=messages "thread:000000000000a125"\r
+> id:MYMSGID\r
+> $\r
+> # I know that MYMSGIDREPLY did respond to that message. I have it in\r
+> my mutt mailbox and it shows the down-right arrow signifying this. I\r
+> inspect the headers and there is indeed a header in MYMSGIDREPLY that\r
+> says "In-Reply-To: <MYMSGID>". I then do...\r
+> $ notmuch search --output=threads "id:MYMSGIDREPLY"\r
+> thread:000000000000c125\r
+> $ notmuch search --output=messages "thread:000000000000c125"\r
+> id:MYMSGIDREPLY\r
+> $\r
+\r
+If the thread-id's are accurate, then it looks like the two messages are\r
+not in the same thread according to notmuch (it's easy to be fooled\r
+because the thread-ids are so similar).  I can't really explain how\r
+those messages might have ended up in different threads. \r
+\r
+  - One potential issue is that if message ids are extra long or badly\r
+  formed, then notmuch might make up a new message id. In that case your\r
+  thread-id search wouldn't work at all.\r
+\r
+  - If there are actually multiple (unrelated) files with message-id\r
+    MYMSGIDREPLY, then the indexed one might not have the in-reply-to\r
+    header. But in this case you could tell by\r
+\r
+    notmuch show id:MYMSGIDREPLY\r
+\r
+    and/or\r
+\r
+    notmuch search --output=files id:MSGIDREPLY\r
+\r
+In order for the thread-ids to change when you run "notmuch new", I\r
+_think_ that there has to be a third message in the thread disovered.\r
+\r
+So it's a mystery. If it happens again with public messages, it would be\r
+worth sharing the messages (as attachements) with the list, just in case\r
+there is something in the headers that explains it.\r
+\r