1 Return-Path: <jani@nikula.org>
\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 8C4BC431FAF
\r
6 for <notmuch@notmuchmail.org>; Thu, 26 Jan 2012 05:16:57 -0800 (PST)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=-0.7 tagged_above=-999 required=5
\r
12 tests=[RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled
\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 J3HEG4D9F+BR for <notmuch@notmuchmail.org>;
\r
16 Thu, 26 Jan 2012 05:16:57 -0800 (PST)
\r
17 Received: from mail-qy0-f181.google.com (mail-qy0-f181.google.com
\r
18 [209.85.216.181]) (using TLSv1 with cipher RC4-SHA (128/128 bits))
\r
19 (No client certificate requested)
\r
20 by olra.theworths.org (Postfix) with ESMTPS id EAB85431FAE
\r
21 for <notmuch@notmuchmail.org>; Thu, 26 Jan 2012 05:16:56 -0800 (PST)
\r
22 Received: by qcpx40 with SMTP id x40so327225qcp.26
\r
23 for <notmuch@notmuchmail.org>; Thu, 26 Jan 2012 05:16:56 -0800 (PST)
\r
24 Received: by 10.229.106.151 with SMTP id x23mr667982qco.111.1327583816331;
\r
25 Thu, 26 Jan 2012 05:16:56 -0800 (PST)
\r
26 Received: from localhost (nikula.org. [92.243.24.172])
\r
27 by mx.google.com with ESMTPS id s18sm8475663qaz.15.2012.01.26.05.16.54
\r
28 (version=SSLv3 cipher=OTHER); Thu, 26 Jan 2012 05:16:55 -0800 (PST)
\r
29 From: Jani Nikula <jani@nikula.org>
\r
30 To: Gregor Zattler <telegraph@gmx.net>, notmuch <notmuch@notmuchmail.org>
\r
31 Subject: Re: Bug?: notmuch-search-show-thread shows several threads;
\r
32 only one containing matching messages
\r
33 In-Reply-To: <20120126124450.GB30209@shi.workgroup>
\r
34 References: <20120126004024.GA13704@shi.workgroup>
\r
35 <20120126011903.GA1176@mit.edu>
\r
36 <8762fzry7k.fsf@servo.finestructure.net>
\r
37 <20120126124450.GB30209@shi.workgroup>
\r
38 User-Agent: Notmuch/0.10.2+187~g43d4f26 (http://notmuchmail.org) Emacs/23.1.1
\r
40 Date: Thu, 26 Jan 2012 13:16:53 +0000
\r
41 Message-ID: <87mx9aioxm.fsf@nikula.org>
\r
43 Content-Type: text/plain; charset=us-ascii
\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: Thu, 26 Jan 2012 13:16:57 -0000
\r
58 On Thu, 26 Jan 2012 13:44:50 +0100, Gregor Zattler <telegraph@gmx.net> wrote:
\r
60 > * Jameson Graef Rollins <jrollins@finestructure.net> [25. Jan. 2012]:
\r
61 > > On Wed, 25 Jan 2012 20:19:03 -0500, Austin Clements <amdragon@MIT.EDU> wrote:
\r
62 > >> One very common cause of this is someone using "reply" to get an
\r
63 > >> initial set of recipients, but then replacing the entire message and
\r
64 > >> subject (presumably without realizing that the mail is still tracking
\r
65 > >> what it was a reply to). This can also happen if someone
\r
66 > >> intentionally replies to multiple messages (though few mail clients
\r
67 > >> support this), or if there was a message ID collision.
\r
69 > > This is a very common occurrence for me as well. I would put money down
\r
70 > > that this is what you're seeing.
\r
72 > I thought about this too and this is why I checked for any
\r
73 > occurrence of Message-IDs in the other emails:
\r
75 > |> I isolated the thread I was interested in,
\r
76 > |> extracted the message ids of its messages and greped the rest of
\r
77 > |> the messages for this message ids: no matches.[2] Therefore no of
\r
78 > |> the rests messages are part of the thread I was interested in
\r
80 > perhaps there was a logic error in how I did this:
\r
82 > |> [2] grep -I "^Message-Id:" /tmp/thread-I-m-interested-in.mbox |sed -e "s/Message-Id: <//I" -e "s/>$//" >really.mid
\r
83 > |> grep -I -F really.mid rest.mbox
\r
86 > /tmp/thread-I-m-interested-in.mbox is a mbox with messages
\r
87 > I'minterested in, the "real" ones. really.mid is a list of
\r
88 > Message-IDs of these "real" emails. rest.mbox is a mbox with the
\r
89 > other emails, Emacs showed in his notmuch show buffer but are
\r
92 > Since there is no match I concluded, the threads are not linked.
\r
93 > Perhaps I made a mistake. I'l retest it and report again. But
\r
94 > right now I don't have the time to do this.
\r
96 Do you have an mbox file in the maildir indexed by notmuch? That seems
\r