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

diff --git a/73/fa97f20b5c218fb388f1573693e9ff47519cef b/73/fa97f20b5c218fb388f1573693e9ff47519cef
new file mode 100644 (file)
index 0000000..9b6e6d2
--- /dev/null
+++ b/73/fa97f20b5c218fb388f1573693e9ff47519cef
@@ -0,0 +1,123 @@
+Return-Path: <xuwang762@gmail.com>\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 5A78B6DE025E\r
+ for <notmuch@notmuchmail.org>; Sun,  4 Oct 2015 20:52:17 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at cworth.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -0.135\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-0.135 tagged_above=-999 required=5\r
+ tests=[AWL=-0.309, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,\r
+ DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25,\r
+ FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01,\r
+ RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_SBL=0.644,\r
+ URIBL_SBL_A=0.1] 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 bNZUHMc2Ng2c for <notmuch@notmuchmail.org>;\r
+ Sun,  4 Oct 2015 20:52:15 -0700 (PDT)\r
+Received: from mail-ob0-f170.google.com (mail-ob0-f170.google.com\r
+ [209.85.214.170])\r
+ by arlo.cworth.org (Postfix) with ESMTPS id 28C8E6DE0173\r
+ for <notmuch@notmuchmail.org>; Sun,  4 Oct 2015 20:52:15 -0700 (PDT)\r
+Received: by obbbh8 with SMTP id bh8so119477357obb.0\r
+ for <notmuch@notmuchmail.org>; Sun, 04 Oct 2015 20:52:13 -0700 (PDT)\r
+DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;\r
+ h=mime-version:in-reply-to:references:date:message-id:subject:from:to\r
+ :cc:content-type;\r
+ bh=dTFbIN7FvbRAnWvfWCxg6/UvF/F6fOSNqGO+YbhkKiU=;\r
+ b=WErtSfnGgeT7FXKFOtjtLuGdfx4NpLk/EBRAUd+GbcgyyMKz1t5DhsIYhdRy/XDEw+\r
+ RKV790G4WiLX3zvuyllnE3DKYrLgFim7fP6wfLk01V9mhHCNp7lofkLG39Tx4352HCXH\r
+ DNyHbRyP85PSEgki9LWPE8BaEbD5t/RUODNVI9zQOzsR4105V3czVDzcOQhk9/oBq0PJ\r
+ oMGBB0Vfae/b4VuFHyxXq1IWysYiuqwrFOOux3A3HDKbT0yQQ+9mu4Uk5K04TZq8t4fW\r
+ iRTdfhAr8Zup4kbl8qlyvrghLL+Lae02SqFE64cn5GdfdLTEGaGh7RGi7HLJcG+tslOK\r
+ qAFA==\r
+MIME-Version: 1.0\r
+X-Received: by 10.182.138.40 with SMTP id qn8mr16761131obb.78.1444017133805;\r
+ Sun, 04 Oct 2015 20:52:13 -0700 (PDT)\r
+Received: by 10.202.212.204 with HTTP; Sun, 4 Oct 2015 20:52:13 -0700 (PDT)\r
+In-Reply-To: <87oage9a0a.fsf@zancas.localnet>\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
+ <87oage9a0a.fsf@zancas.localnet>\r
+Date: Sun, 4 Oct 2015 23:52:13 -0400\r
+Message-ID:\r
+ <CAJhTkNjbY_Q9w8v5oDFLtUkfP=Hg9F=ozEBCq1bFmA-+_RV8wA@mail.gmail.com>\r
+Subject: Re: Possible some threads are not complete due to bug?\r
+From: Xu Wang <xuwang762@gmail.com>\r
+To: David Bremner <david@tethera.net>\r
+Content-Type: text/plain; charset=UTF-8\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: Mon, 05 Oct 2015 03:52:17 -0000\r
+\r
+On Sun, Oct 4, 2015 at 6:57 AM, David Bremner <david@tethera.net> wrote:\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
+\r
+OK I will be careful to document if I find a repeatable example and\r
+share with the list. I would like to help in any possible way that I\r
+am capable.\r
+\r
+Kind regards,\r
+\r
+Xu\r