From 53272bdc376cd3f2c4572544fdbc4980666ba7b9 Mon Sep 17 00:00:00 2001 From: David Bremner Date: Mon, 27 Jan 2014 19:43:47 +2000 Subject: [PATCH] Re: Bug?: notmuch-search-show-thread shows several threads; only one containing matching messages --- 02/95ddf95409a1c02f669a6356134bb3616a9f6f | 86 +++++++++++++++++++++++ 1 file changed, 86 insertions(+) create mode 100644 02/95ddf95409a1c02f669a6356134bb3616a9f6f diff --git a/02/95ddf95409a1c02f669a6356134bb3616a9f6f b/02/95ddf95409a1c02f669a6356134bb3616a9f6f new file mode 100644 index 000000000..b9494c633 --- /dev/null +++ b/02/95ddf95409a1c02f669a6356134bb3616a9f6f @@ -0,0 +1,86 @@ +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 6497C431FBD + for ; Sun, 26 Jan 2014 15:44:02 -0800 (PST) +X-Virus-Scanned: Debian amavisd-new at olra.theworths.org +X-Spam-Flag: NO +X-Spam-Score: 0 +X-Spam-Level: +X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none] + 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 PL5+xOS7jf2c for ; + Sun, 26 Jan 2014 15:43:58 -0800 (PST) +Received: from yantan.tethera.net (yantan.tethera.net [199.188.72.155]) + (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) + (No client certificate requested) + by olra.theworths.org (Postfix) with ESMTPS id 2EF9E431FBC + for ; Sun, 26 Jan 2014 15:43:58 -0800 (PST) +Received: from remotemail by yantan.tethera.net with local (Exim 4.80) + (envelope-from ) + id 1W7ZMo-0002wt-VK; Sun, 26 Jan 2014 19:43:54 -0400 +Received: (nullmailer pid 16602 invoked by uid 1000); Sun, 26 Jan 2014 + 23:43:47 -0000 +From: David Bremner +To: Gregor Zattler , notmuch +Subject: Re: Bug?: notmuch-search-show-thread shows several threads; only one + containing matching messages +In-Reply-To: <20140126212604.GC10844@boo.workgroup> +References: <8762fzry7k.fsf@servo.finestructure.net> + <20120126124450.GB30209@shi.workgroup> <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> +User-Agent: Notmuch/0.17+49~gaa57e9d (http://notmuchmail.org) Emacs/24.3.1 + (x86_64-pc-linux-gnu) +Date: Sun, 26 Jan 2014 19:43:47 -0400 +Message-ID: <87r47ul364.fsf@zancas.localnet> +MIME-Version: 1.0 +Content-Type: text/plain +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: Sun, 26 Jan 2014 23:44:02 -0000 + +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? + +> 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. + +d -- 2.26.2