1 Return-Path: <error4me@gmx.de>
\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 3F7A6431FBD
\r
6 for <notmuch@notmuchmail.org>; Sun, 26 Jan 2014 17:54:00 -0800 (PST)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=0.001 tagged_above=-999 required=5
\r
12 tests=[FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001]
\r
14 Received: from olra.theworths.org ([127.0.0.1])
\r
15 by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)
\r
16 with ESMTP id hSrdw7EuwDqv for <notmuch@notmuchmail.org>;
\r
17 Sun, 26 Jan 2014 17:53:52 -0800 (PST)
\r
18 Received: from mout.gmx.net (mout.gmx.net [212.227.15.19])
\r
19 (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits))
\r
20 (No client certificate requested)
\r
21 by olra.theworths.org (Postfix) with ESMTPS id CF9B7431FBC
\r
22 for <notmuch@notmuchmail.org>; Sun, 26 Jan 2014 17:53:51 -0800 (PST)
\r
23 Received: from boo.workgroup ([87.187.157.204]) by mail.gmx.com (mrgmx001)
\r
24 with ESMTPSA (Nemesis) id 0McDl1-1VpFO30hVP-00JcBr for
\r
25 <notmuch@notmuchmail.org>; Mon, 27 Jan 2014 02:48:48 +0100
\r
26 Received: from grfz by boo.workgroup with local (Exim 4.82)
\r
27 (envelope-from <error4me@gmx.de>)
\r
28 id 1W7bJa-0008NU-1l; Mon, 27 Jan 2014 02:48:42 +0100
\r
29 Date: Mon, 27 Jan 2014 02:48:12 +0100
\r
30 From: Gregor Zattler <telegraph@gmx.net>
\r
31 To: notmuch <notmuch@notmuchmail.org>
\r
32 Subject: Re: Bug?: notmuch-search-show-thread shows several threads; only one
\r
33 containing matching messages
\r
34 Message-ID: <20140127014812.GE10844@boo.workgroup>
\r
35 Mail-Followup-To: notmuch <notmuch@notmuchmail.org>
\r
36 References: <87mx9avbc1.fsf@praet.org> <20120129234213.GB11460@shi.workgroup>
\r
37 <87zkd5655g.fsf@praet.org> <20120130190425.GB13521@shi.workgroup>
\r
38 <878vkoev95.fsf@qmul.ac.uk> <20120130223416.GA26239@shi.workgroup>
\r
39 <874nvcekjk.fsf@qmul.ac.uk> <87lhy5pko1.fsf@zancas.localnet>
\r
40 <20140126212604.GC10844@boo.workgroup>
\r
41 <87r47ul364.fsf@zancas.localnet>
\r
43 Content-Type: text/plain; charset=us-ascii
\r
44 Content-Disposition: inline
\r
45 In-Reply-To: <87r47ul364.fsf@zancas.localnet>
\r
46 User-Agent: Mutt/1.5.21 (2010-09-15)
\r
47 Sender: error4me@gmx.de
\r
48 X-Provags-ID: V03:K0:sCwX+AltMkdyAnsIzEFItDMaNYkauo7lUcs/hG94rWNIBpJfn/k
\r
49 64K0S7iUsW5XVhp0BLIzsesmTE38arcU4ym9C4XB+gbhJUU1ClMq7Mleq1Z1ZIVSa9rGgeg
\r
50 ei1v+I3E193W/syv3Qnidq/37GawMgh7FeLD2jqgm9edT0SfzfqfY0dqKppslcWe6Di6XoW
\r
51 wj7ggXK1niTwxpZbVjr9w==
\r
52 X-BeenThere: notmuch@notmuchmail.org
\r
53 X-Mailman-Version: 2.1.13
\r
55 List-Id: "Use and development of the notmuch mail system."
\r
56 <notmuch.notmuchmail.org>
\r
57 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
58 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
59 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
60 List-Post: <mailto:notmuch@notmuchmail.org>
\r
61 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
62 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
63 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
64 X-List-Received-Date: Mon, 27 Jan 2014 01:54:00 -0000
\r
67 * David Bremner <david@tethera.net> [26. Jan. 2014]:
\r
68 > Gregor Zattler <telegraph@gmx.net> writes:
\r
70 >> Today I produced another mbox with the very same command but with
\r
71 >> a now larger email corpus freshly indexed with a fresh notmuch.
\r
72 >> The mbox contains (according to mutt) 507 messages in 34 threads.
\r
73 >> One of them is the thread I searched for.
\r
75 >> I grepped for the 7 subjects within the 34 subjects and only 5
\r
78 > I don't know what you mean here. Grepped where? in the raw messages?
\r
80 With mutt I had a view at the collapsed 7 respective 34 threads.
\r
81 One then sees the very first E-Mails of a thread and among other
\r
82 information their subjects.
\r
83 Via editing I produced two lists with subjects and then searched
\r
84 each of the 7 in the list with the 34.
\r
86 >> If somebody want's to dig into this: I can provide the two
\r
89 >> Disclaimer: Many of the emails which arrived before the problem
\r
90 >> report are not the exact same than then, because since the I
\r
91 >> mangled them with a script. This should have not changed the
\r
92 >> threading but I cannot be 100% sure. But if it's important for
\r
93 >> further investigation I'm probably able to reproduce the status
\r
94 >> quo of the email corpus then from my backups.
\r
96 > If it's currently not working then I guess your current corpus should be
\r
97 > fine. It would probably help to restate what exactly is wrong. There was
\r
98 > a lot of discussion, and the concrete problem I saw identified (in
\r
99 > id:874nvcekjk.fsf@qmul.ac.uk ) was that certain malformed In-reply-to
\r
100 > headers were causing unrelated threads to merge.
\r
102 Yes. I understood the commit message of the commit you
\r
103 referenced in the email I answered to, that now notmuch uses
\r
104 Reference: headers to do the threading. I had a quick view at
\r
105 the References header in the mbox file and none looked
\r
110 -... --- .-. . -.. ..--.. ...-.-
\r