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

diff --git a/74/d1fb98d028824b277135b02b47b51855a8ba73 b/74/d1fb98d028824b277135b02b47b51855a8ba73
new file mode 100644 (file)
index 0000000..1749c7c
--- /dev/null
+++ b/74/d1fb98d028824b277135b02b47b51855a8ba73
@@ -0,0 +1,110 @@
+Return-Path: <error4me@gmx.de>\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 3F7A6431FBD\r
+       for <notmuch@notmuchmail.org>; Sun, 26 Jan 2014 17:54:00 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: 0.001\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=0.001 tagged_above=-999 required=5\r
+       tests=[FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001]\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 hSrdw7EuwDqv for <notmuch@notmuchmail.org>;\r
+       Sun, 26 Jan 2014 17:53:52 -0800 (PST)\r
+Received: from mout.gmx.net (mout.gmx.net [212.227.15.19])\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 CF9B7431FBC\r
+       for <notmuch@notmuchmail.org>; Sun, 26 Jan 2014 17:53:51 -0800 (PST)\r
+Received: from boo.workgroup ([87.187.157.204]) by mail.gmx.com (mrgmx001)\r
+       with ESMTPSA (Nemesis) id 0McDl1-1VpFO30hVP-00JcBr for\r
+       <notmuch@notmuchmail.org>; Mon, 27 Jan 2014 02:48:48 +0100\r
+Received: from grfz by boo.workgroup with local (Exim 4.82)\r
+       (envelope-from <error4me@gmx.de>)\r
+       id 1W7bJa-0008NU-1l; Mon, 27 Jan 2014 02:48:42 +0100\r
+Date: Mon, 27 Jan 2014 02:48:12 +0100\r
+From: Gregor Zattler <telegraph@gmx.net>\r
+To: notmuch <notmuch@notmuchmail.org>\r
+Subject: Re: Bug?: notmuch-search-show-thread shows several threads; only one\r
+       containing matching messages\r
+Message-ID: <20140127014812.GE10844@boo.workgroup>\r
+Mail-Followup-To: notmuch <notmuch@notmuchmail.org>\r
+References: <87mx9avbc1.fsf@praet.org> <20120129234213.GB11460@shi.workgroup>\r
+       <87zkd5655g.fsf@praet.org> <20120130190425.GB13521@shi.workgroup>\r
+       <878vkoev95.fsf@qmul.ac.uk> <20120130223416.GA26239@shi.workgroup>\r
+       <874nvcekjk.fsf@qmul.ac.uk> <87lhy5pko1.fsf@zancas.localnet>\r
+       <20140126212604.GC10844@boo.workgroup>\r
+       <87r47ul364.fsf@zancas.localnet>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain; charset=us-ascii\r
+Content-Disposition: inline\r
+In-Reply-To: <87r47ul364.fsf@zancas.localnet>\r
+User-Agent: Mutt/1.5.21 (2010-09-15)\r
+Sender: error4me@gmx.de\r
+X-Provags-ID: V03:K0:sCwX+AltMkdyAnsIzEFItDMaNYkauo7lUcs/hG94rWNIBpJfn/k\r
+       64K0S7iUsW5XVhp0BLIzsesmTE38arcU4ym9C4XB+gbhJUU1ClMq7Mleq1Z1ZIVSa9rGgeg\r
+       ei1v+I3E193W/syv3Qnidq/37GawMgh7FeLD2jqgm9edT0SfzfqfY0dqKppslcWe6Di6XoW\r
+       wj7ggXK1niTwxpZbVjr9w==\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: Mon, 27 Jan 2014 01:54:00 -0000\r
+\r
+Hi David,\r
+* David Bremner <david@tethera.net> [26. Jan. 2014]:\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
+With mutt I had a view at the collapsed 7 respective 34 threads.\r
+One then sees the very first E-Mails of a thread and among other\r
+information their subjects.\r
+Via editing I produced two lists with subjects and then searched\r
+each of the 7 in the list with the 34.\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
+Yes.  I understood the commit message of the commit you\r
+referenced in the email I answered to, that now notmuch uses\r
+ Reference: headers to do the threading.  I had a quick view at\r
+the References header in the mbox file and none looked\r
+suspicious.\r
+\r
+Ciao, Gregor\r
+-- \r
+ -... --- .-. . -.. ..--.. ...-.-\r