Re: Bug?: notmuch-search-show-thread shows several threads; only one containing match...

diff --git a/02/95ddf95409a1c02f669a6356134bb3616a9f6f b/02/95ddf95409a1c02f669a6356134bb3616a9f6f
new file mode 100644 (file)
index 0000000..b9494c6
--- /dev/null
+++ b/02/95ddf95409a1c02f669a6356134bb3616a9f6f
@@ -0,0 +1,86 @@
+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 olra.theworths.org (Postfix) with ESMTP id 6497C431FBD\r
+       for <notmuch@notmuchmail.org>; Sun, 26 Jan 2014 15:44:02 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: 0\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none]\r
+       autolearn=disabled\r
+Received: from olra.theworths.org ([127.0.0.1])\r
+       by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
+       with ESMTP id PL5+xOS7jf2c for <notmuch@notmuchmail.org>;\r
+       Sun, 26 Jan 2014 15:43:58 -0800 (PST)\r
+Received: from yantan.tethera.net (yantan.tethera.net [199.188.72.155])\r
+       (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits))\r
+       (No client certificate requested)\r
+       by olra.theworths.org (Postfix) with ESMTPS id 2EF9E431FBC\r
+       for <notmuch@notmuchmail.org>; Sun, 26 Jan 2014 15:43:58 -0800 (PST)\r
+Received: from remotemail by yantan.tethera.net with local (Exim 4.80)\r
+       (envelope-from <david@tethera.net>)\r
+       id 1W7ZMo-0002wt-VK; Sun, 26 Jan 2014 19:43:54 -0400\r
+Received: (nullmailer pid 16602 invoked by uid 1000); Sun, 26 Jan 2014\r
+       23:43:47 -0000\r
+From: David Bremner <david@tethera.net>\r
+To: Gregor Zattler <telegraph@gmx.net>, notmuch <notmuch@notmuchmail.org>\r
+Subject: Re: Bug?: notmuch-search-show-thread shows several threads; only one\r
+       containing matching messages\r
+In-Reply-To: <20140126212604.GC10844@boo.workgroup>\r
+References: <8762fzry7k.fsf@servo.finestructure.net>\r
+       <20120126124450.GB30209@shi.workgroup> <87mx9avbc1.fsf@praet.org>\r
+       <20120129234213.GB11460@shi.workgroup> <87zkd5655g.fsf@praet.org>\r
+       <20120130190425.GB13521@shi.workgroup> <878vkoev95.fsf@qmul.ac.uk>\r
+       <20120130223416.GA26239@shi.workgroup> <874nvcekjk.fsf@qmul.ac.uk>\r
+       <87lhy5pko1.fsf@zancas.localnet> <20140126212604.GC10844@boo.workgroup>\r
+User-Agent: Notmuch/0.17+49~gaa57e9d (http://notmuchmail.org) Emacs/24.3.1\r
+       (x86_64-pc-linux-gnu)\r
+Date: Sun, 26 Jan 2014 19:43:47 -0400\r
+Message-ID: <87r47ul364.fsf@zancas.localnet>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.13\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, 26 Jan 2014 23:44:02 -0000\r
+\r
+Gregor Zattler <telegraph@gmx.net> writes:\r
+\r
+> Today I produced another mbox with the very same command but with\r
+> a now larger email corpus freshly indexed with a fresh notmuch.\r
+> The mbox contains (according to mutt) 507 messages in 34 threads.\r
+> One of them is the thread I searched for.\r
+>\r
+> I grepped for the 7 subjects within the 34 subjects and only 5\r
+> showed up.\r
+\r
+I don't know what you mean here. Grepped where? in the raw messages?\r
+\r
+> If somebody want's to dig into this: I can provide the two\r
+> mboxes. \r
+>\r
+> Disclaimer: Many of the emails which arrived before the problem\r
+> report are not the exact same than then, because since the I\r
+> mangled them with a script.  This should have not changed the\r
+> threading but I cannot be 100% sure.  But if it's important for\r
+> further investigation I'm probably able to reproduce the status\r
+> quo of the email corpus then from my backups.\r
+\r
+If it's currently not working then I guess your current corpus should be\r
+fine. It would probably help to restate what exactly is wrong. There was\r
+a lot of discussion, and the concrete problem I saw identified (in\r
+id:874nvcekjk.fsf@qmul.ac.uk ) was that certain malformed In-reply-to\r
+headers were causing unrelated threads to merge.\r
+\r
+d\r