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

diff --git a/0a/33b11809da40b54ee3d4046d5524cc89fbec73 b/0a/33b11809da40b54ee3d4046d5524cc89fbec73
new file mode 100644 (file)
index 0000000..9a3c234
--- /dev/null
+++ b/0a/33b11809da40b54ee3d4046d5524cc89fbec73
@@ -0,0 +1,104 @@
+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 A42576DE1B2E\r
+ for <notmuch@notmuchmail.org>; Sun, 20 Sep 2015 07:34:01 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at cworth.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -0.203\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-0.203 tagged_above=-999 required=5\r
+ tests=[AWL=-0.377, 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 8m4wpxN10yDz for <notmuch@notmuchmail.org>;\r
+ Sun, 20 Sep 2015 07:33:59 -0700 (PDT)\r
+Received: from mail-ob0-f180.google.com (mail-ob0-f180.google.com\r
+ [209.85.214.180])\r
+ by arlo.cworth.org (Postfix) with ESMTPS id 3DADC6DE1B2C\r
+ for <notmuch@notmuchmail.org>; Sun, 20 Sep 2015 07:33:59 -0700 (PDT)\r
+Received: by obbda8 with SMTP id da8so66829142obb.1\r
+ for <notmuch@notmuchmail.org>; Sun, 20 Sep 2015 07:33:58 -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=l0lMVYsW5Fb9WxSpbCuAo3EUAIeIeIGK5faO7IQtE3I=;\r
+ b=z6y/fjxoS45cXI6aLsfLqlZKepUapAYuvk7w+SgO4QcUbwLqPgWIm4z7NazbM2y0av\r
+ amrJuIEVrHyOCqlNqZAkqUUr1no9Hp8oNQuhxmy+7Ka9LgQYC1SI2TPSb3Mc4H7Fu5eu\r
+ 75Kzpaw9Q7NMi9fKnrb9CAbGab9IjxWDHCye0e3D5NZqAXg4aXciADvAN8auNLwj+m7E\r
+ 7YF7wU4mVQwOm+4mIWekRJ6sxwkqbe/I/gphmbMa47txVP9YjaQ56pl0GgKcboYQY/dM\r
+ 8pApEU6VRMxtY1oWZbrkNon2dNk+ZzoykQDS6IMuPZEUnne3dIE30WRTKYT0GZ3nnpst\r
+ fCgw==\r
+MIME-Version: 1.0\r
+X-Received: by 10.182.158.164 with SMTP id wv4mr9403505obb.78.1442759638163;\r
+ Sun, 20 Sep 2015 07:33:58 -0700 (PDT)\r
+Received: by 10.202.212.204 with HTTP; Sun, 20 Sep 2015 07:33:58 -0700 (PDT)\r
+In-Reply-To: <87fv2a4ctt.fsf@zancas.localnet>\r
+References:\r
+ <CAJhTkNh7_hXDLsAGyD7nwkXV4ca6ymkLtFG945USvfqK4ZJEdQ@mail.gmail.com>\r
+ <87fv2a4ctt.fsf@zancas.localnet>\r
+Date: Sun, 20 Sep 2015 10:33:58 -0400\r
+Message-ID:\r
+ <CAJhTkNgBdnm18UXC95ryJk5w7fJpa7-1LvdugV3S29fL4kxxhQ@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: Sun, 20 Sep 2015 14:34:01 -0000\r
+\r
+On Sat, Sep 19, 2015 at 12:02 PM, David Bremner <david@tethera.net> wrote:\r
+> Xu Wang <xuwang762@gmail.com> writes:\r
+>\r
+>> Sometimes I need to do:\r
+>>\r
+>> $ notmuch search --output=threads "id:MYMSGID"\r
+>> thread:000000000000a125\r
+>> $ notmuch search --output=messages "thread:000000000000a125"\r
+>>\r
+>> In theory, this should output the message that responded to message ID\r
+>> "MYMSGID". Sometimes it works. But sometimes it does not work. That\r
+>> is, there exists an email where I am sure (I checked the raw email)\r
+>> that there is a header\r
+>> In-Reply-To: <MYMSGID>\r
+>> but that email does not show when I do the two commands above.\r
+>\r
+> I'm not 100% sure what you mean by "does not show". Do you mean that the\r
+> output from the second command is empty? or does not contain MYMSGID?\r
+\r
+That was poor formatting on my part. It only was outputting the id I\r
+put into the first command. So it only showed\r
+id:MYMSGID\r
+\r
+>> Indeed, that mail belongs to a different thread ID.\r
+>\r
+> How can you tell that the mail belongs to a different thread?\r
+\r
+Because when I do a notmuch search for that message by message ID with\r
+--output=threads, it gives a different thread ID.\r
+\r
+> Isn't that what your first command tells you?\r
+Well yes, but I wanted to confirm that that is indeed the reason. I\r
+have heard in someone saying that debugging is process of confirming\r
+things that should be true.\r
+\r
+Kind regards,\r
+\r
+Xu\r