From: Gregor Zattler Date: Mon, 27 Jan 2014 01:48:12 +0000 (+0100) Subject: Re: Bug?: notmuch-search-show-thread shows several threads; only one containing match... X-Git-Url: http://git.tremily.us/?a=commitdiff_plain;h=76e2d4803f0973f872bf5f9b2ce5ad70832c61cc;p=notmuch-archives.git Re: Bug?: notmuch-search-show-thread shows several threads; only one containing matching messages --- diff --git a/74/d1fb98d028824b277135b02b47b51855a8ba73 b/74/d1fb98d028824b277135b02b47b51855a8ba73 new file mode 100644 index 000000000..1749c7c14 --- /dev/null +++ b/74/d1fb98d028824b277135b02b47b51855a8ba73 @@ -0,0 +1,110 @@ +Return-Path: +X-Original-To: notmuch@notmuchmail.org +Delivered-To: notmuch@notmuchmail.org +Received: from localhost (localhost [127.0.0.1]) + by olra.theworths.org (Postfix) with ESMTP id 3F7A6431FBD + for ; Sun, 26 Jan 2014 17:54:00 -0800 (PST) +X-Virus-Scanned: Debian amavisd-new at olra.theworths.org +X-Spam-Flag: NO +X-Spam-Score: 0.001 +X-Spam-Level: +X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 + tests=[FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001] + autolearn=disabled +Received: from olra.theworths.org ([127.0.0.1]) + by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024) + with ESMTP id hSrdw7EuwDqv for ; + Sun, 26 Jan 2014 17:53:52 -0800 (PST) +Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) + (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) + (No client certificate requested) + by olra.theworths.org (Postfix) with ESMTPS id CF9B7431FBC + for ; Sun, 26 Jan 2014 17:53:51 -0800 (PST) +Received: from boo.workgroup ([87.187.157.204]) by mail.gmx.com (mrgmx001) + with ESMTPSA (Nemesis) id 0McDl1-1VpFO30hVP-00JcBr for + ; Mon, 27 Jan 2014 02:48:48 +0100 +Received: from grfz by boo.workgroup with local (Exim 4.82) + (envelope-from ) + id 1W7bJa-0008NU-1l; Mon, 27 Jan 2014 02:48:42 +0100 +Date: Mon, 27 Jan 2014 02:48:12 +0100 +From: Gregor Zattler +To: notmuch +Subject: Re: Bug?: notmuch-search-show-thread shows several threads; only one + containing matching messages +Message-ID: <20140127014812.GE10844@boo.workgroup> +Mail-Followup-To: notmuch +References: <87mx9avbc1.fsf@praet.org> <20120129234213.GB11460@shi.workgroup> + <87zkd5655g.fsf@praet.org> <20120130190425.GB13521@shi.workgroup> + <878vkoev95.fsf@qmul.ac.uk> <20120130223416.GA26239@shi.workgroup> + <874nvcekjk.fsf@qmul.ac.uk> <87lhy5pko1.fsf@zancas.localnet> + <20140126212604.GC10844@boo.workgroup> + <87r47ul364.fsf@zancas.localnet> +MIME-Version: 1.0 +Content-Type: text/plain; charset=us-ascii +Content-Disposition: inline +In-Reply-To: <87r47ul364.fsf@zancas.localnet> +User-Agent: Mutt/1.5.21 (2010-09-15) +Sender: error4me@gmx.de +X-Provags-ID: V03:K0:sCwX+AltMkdyAnsIzEFItDMaNYkauo7lUcs/hG94rWNIBpJfn/k + 64K0S7iUsW5XVhp0BLIzsesmTE38arcU4ym9C4XB+gbhJUU1ClMq7Mleq1Z1ZIVSa9rGgeg + ei1v+I3E193W/syv3Qnidq/37GawMgh7FeLD2jqgm9edT0SfzfqfY0dqKppslcWe6Di6XoW + wj7ggXK1niTwxpZbVjr9w== +X-BeenThere: notmuch@notmuchmail.org +X-Mailman-Version: 2.1.13 +Precedence: list +List-Id: "Use and development of the notmuch mail system." + +List-Unsubscribe: , + +List-Archive: +List-Post: +List-Help: +List-Subscribe: , + +X-List-Received-Date: Mon, 27 Jan 2014 01:54:00 -0000 + +Hi David, +* David Bremner [26. Jan. 2014]: +> Gregor Zattler writes: +> +>> Today I produced another mbox with the very same command but with +>> a now larger email corpus freshly indexed with a fresh notmuch. +>> The mbox contains (according to mutt) 507 messages in 34 threads. +>> One of them is the thread I searched for. +>> +>> I grepped for the 7 subjects within the 34 subjects and only 5 +>> showed up. +> +> I don't know what you mean here. Grepped where? in the raw messages? + +With mutt I had a view at the collapsed 7 respective 34 threads. +One then sees the very first E-Mails of a thread and among other +information their subjects. +Via editing I produced two lists with subjects and then searched +each of the 7 in the list with the 34. + +>> If somebody want's to dig into this: I can provide the two +>> mboxes. +>> +>> Disclaimer: Many of the emails which arrived before the problem +>> report are not the exact same than then, because since the I +>> mangled them with a script. This should have not changed the +>> threading but I cannot be 100% sure. But if it's important for +>> further investigation I'm probably able to reproduce the status +>> quo of the email corpus then from my backups. +> +> If it's currently not working then I guess your current corpus should be +> fine. It would probably help to restate what exactly is wrong. There was +> a lot of discussion, and the concrete problem I saw identified (in +> id:874nvcekjk.fsf@qmul.ac.uk ) was that certain malformed In-reply-to +> headers were causing unrelated threads to merge. + +Yes. I understood the commit message of the commit you +referenced in the email I answered to, that now notmuch uses + Reference: headers to do the threading. I had a quick view at +the References header in the mbox file and none looked +suspicious. + +Ciao, Gregor +-- + -... --- .-. . -.. ..--.. ...-.-