1 Return-Path: <david@tethera.net>
\r
2 X-Original-To: notmuch@notmuchmail.org
\r
3 Delivered-To: notmuch@notmuchmail.org
\r
4 Received: from localhost (localhost [127.0.0.1])
\r
5 by olra.theworths.org (Postfix) with ESMTP id 6497C431FBD
\r
6 for <notmuch@notmuchmail.org>; Sun, 26 Jan 2014 15:44:02 -0800 (PST)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none]
\r
13 Received: from olra.theworths.org ([127.0.0.1])
\r
14 by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)
\r
15 with ESMTP id PL5+xOS7jf2c for <notmuch@notmuchmail.org>;
\r
16 Sun, 26 Jan 2014 15:43:58 -0800 (PST)
\r
17 Received: from yantan.tethera.net (yantan.tethera.net [199.188.72.155])
\r
18 (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits))
\r
19 (No client certificate requested)
\r
20 by olra.theworths.org (Postfix) with ESMTPS id 2EF9E431FBC
\r
21 for <notmuch@notmuchmail.org>; Sun, 26 Jan 2014 15:43:58 -0800 (PST)
\r
22 Received: from remotemail by yantan.tethera.net with local (Exim 4.80)
\r
23 (envelope-from <david@tethera.net>)
\r
24 id 1W7ZMo-0002wt-VK; Sun, 26 Jan 2014 19:43:54 -0400
\r
25 Received: (nullmailer pid 16602 invoked by uid 1000); Sun, 26 Jan 2014
\r
27 From: David Bremner <david@tethera.net>
\r
28 To: Gregor Zattler <telegraph@gmx.net>, notmuch <notmuch@notmuchmail.org>
\r
29 Subject: Re: Bug?: notmuch-search-show-thread shows several threads; only one
\r
30 containing matching messages
\r
31 In-Reply-To: <20140126212604.GC10844@boo.workgroup>
\r
32 References: <8762fzry7k.fsf@servo.finestructure.net>
\r
33 <20120126124450.GB30209@shi.workgroup> <87mx9avbc1.fsf@praet.org>
\r
34 <20120129234213.GB11460@shi.workgroup> <87zkd5655g.fsf@praet.org>
\r
35 <20120130190425.GB13521@shi.workgroup> <878vkoev95.fsf@qmul.ac.uk>
\r
36 <20120130223416.GA26239@shi.workgroup> <874nvcekjk.fsf@qmul.ac.uk>
\r
37 <87lhy5pko1.fsf@zancas.localnet> <20140126212604.GC10844@boo.workgroup>
\r
38 User-Agent: Notmuch/0.17+49~gaa57e9d (http://notmuchmail.org) Emacs/24.3.1
\r
39 (x86_64-pc-linux-gnu)
\r
40 Date: Sun, 26 Jan 2014 19:43:47 -0400
\r
41 Message-ID: <87r47ul364.fsf@zancas.localnet>
\r
43 Content-Type: text/plain
\r
44 X-BeenThere: notmuch@notmuchmail.org
\r
45 X-Mailman-Version: 2.1.13
\r
47 List-Id: "Use and development of the notmuch mail system."
\r
48 <notmuch.notmuchmail.org>
\r
49 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
50 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
51 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
52 List-Post: <mailto:notmuch@notmuchmail.org>
\r
53 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
54 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
55 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
56 X-List-Received-Date: Sun, 26 Jan 2014 23:44:02 -0000
\r
58 Gregor Zattler <telegraph@gmx.net> writes:
\r
60 > Today I produced another mbox with the very same command but with
\r
61 > a now larger email corpus freshly indexed with a fresh notmuch.
\r
62 > The mbox contains (according to mutt) 507 messages in 34 threads.
\r
63 > One of them is the thread I searched for.
\r
65 > I grepped for the 7 subjects within the 34 subjects and only 5
\r
68 I don't know what you mean here. Grepped where? in the raw messages?
\r
70 > If somebody want's to dig into this: I can provide the two
\r
73 > Disclaimer: Many of the emails which arrived before the problem
\r
74 > report are not the exact same than then, because since the I
\r
75 > mangled them with a script. This should have not changed the
\r
76 > threading but I cannot be 100% sure. But if it's important for
\r
77 > further investigation I'm probably able to reproduce the status
\r
78 > quo of the email corpus then from my backups.
\r
80 If it's currently not working then I guess your current corpus should be
\r
81 fine. It would probably help to restate what exactly is wrong. There was
\r
82 a lot of discussion, and the concrete problem I saw identified (in
\r
83 id:874nvcekjk.fsf@qmul.ac.uk ) was that certain malformed In-reply-to
\r
84 headers were causing unrelated threads to merge.
\r