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 010B7429E5A
\r
6 for <notmuch@notmuchmail.org>; Sun, 29 Jan 2012 15:37:11 -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 K++R30ODmEJB for <notmuch@notmuchmail.org>;
\r
17 Sun, 29 Jan 2012 15:37:10 -0800 (PST)
\r
18 Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23])
\r
19 by olra.theworths.org (Postfix) with SMTP id DF245429E59
\r
20 for <notmuch@notmuchmail.org>; Sun, 29 Jan 2012 15:37:09 -0800 (PST)
\r
21 Received: (qmail invoked by alias); 29 Jan 2012 23:37:08 -0000
\r
22 Received: from p54BE4D91.dip.t-dialin.net (EHLO shi.workgroup) [84.190.77.145]
\r
23 by mail.gmx.net (mp071) with SMTP; 30 Jan 2012 00:37:08 +0100
\r
24 X-Authenticated: #19296480
\r
25 X-Provags-ID: V01U2FsdGVkX18UvQQtU2kU8SSivHgppYytjBUD56WUOQ0/VQRARP
\r
27 Received: from grfz by shi.workgroup with local (Exim 4.77)
\r
28 (envelope-from <error4me@gmx.de>)
\r
29 id 1RreIn-0008Fm-Qi; Mon, 30 Jan 2012 00:36:53 +0100
\r
30 Date: Mon, 30 Jan 2012 00:36:33 +0100
\r
31 From: Gregor Zattler <telegraph@gmx.net>
\r
32 To: notmuch <notmuch@notmuchmail.org>
\r
33 Subject: Re: Bug?: notmuch-search-show-thread shows several threads; only one
\r
34 containing matching messages
\r
35 Message-ID: <20120129233633.GA11460@shi.workgroup>
\r
36 Mail-Followup-To: notmuch <notmuch@notmuchmail.org>
\r
37 References: <20120126004024.GA13704@shi.workgroup>
\r
38 <20120126011903.GA1176@mit.edu>
\r
39 <8762fzry7k.fsf@servo.finestructure.net>
\r
40 <20120126124450.GB30209@shi.workgroup> <87mx9aioxm.fsf@nikula.org>
\r
42 Content-Type: text/plain; charset=us-ascii
\r
43 Content-Disposition: inline
\r
44 In-Reply-To: <87mx9aioxm.fsf@nikula.org>
\r
45 User-Agent: Mutt/1.5.21 (2010-09-15)
\r
47 X-BeenThere: notmuch@notmuchmail.org
\r
48 X-Mailman-Version: 2.1.13
\r
50 List-Id: "Use and development of the notmuch mail system."
\r
51 <notmuch.notmuchmail.org>
\r
52 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
53 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
54 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
55 List-Post: <mailto:notmuch@notmuchmail.org>
\r
56 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
57 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
58 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
59 X-List-Received-Date: Sun, 29 Jan 2012 23:37:11 -0000
\r
61 Hi Jani, notmuch developers,
\r
63 executive summary: notmuch almangamates several e-mail threads
\r
64 into one notmuch-thread, I consider this a bug:
\r
66 * Jani Nikula <jani@nikula.org> [26. Jan. 2012]:
\r
67 > On Thu, 26 Jan 2012 13:44:50 +0100, Gregor Zattler <telegraph@gmx.net> wrote:
\r
68 >> * Jameson Graef Rollins <jrollins@finestructure.net> [25. Jan. 2012]:
\r
69 >>> On Wed, 25 Jan 2012 20:19:03 -0500, Austin Clements <amdragon@MIT.EDU> wrote:
\r
70 >>>> One very common cause of this is someone using "reply" to get an
\r
71 >>>> initial set of recipients, but then replacing the entire message and
\r
72 >>>> subject (presumably without realizing that the mail is still tracking
\r
73 >>>> what it was a reply to). This can also happen if someone
\r
74 >>>> intentionally replies to multiple messages (though few mail clients
\r
75 >>>> support this), or if there was a message ID collision.
\r
77 >>> This is a very common occurrence for me as well. I would put money down
\r
78 >>> that this is what you're seeing.
\r
80 >> I thought about this too and this is why I checked for any
\r
81 >> occurrence of Message-IDs in the other emails:
\r
83 >> |> I isolated the thread I was interested in,
\r
84 >> |> extracted the message ids of its messages and greped the rest of
\r
85 >> |> the messages for this message ids: no matches.[2] Therefore no of
\r
86 >> |> the rests messages are part of the thread I was interested in
\r
88 >> perhaps there was a logic error in how I did this:
\r
90 >> |> [2] grep -I "^Message-Id:" /tmp/thread-I-m-interested-in.mbox |sed -e "s/Message-Id: <//I" -e "s/>$//" >really.mid
\r
91 >> |> grep -I -F really.mid rest.mbox
\r
93 >> /tmp/thread-I-m-interested-in.mbox is a mbox with messages
\r
94 >> I'minterested in, the "real" ones. really.mid is a list of
\r
95 >> Message-IDs of these "real" emails. rest.mbox is a mbox with the
\r
96 >> other emails, Emacs showed in his notmuch show buffer but are
\r
99 >> Since there is no match I concluded, the threads are not linked.
\r
100 >> Perhaps I made a mistake. I'l retest it and report again. But
\r
101 >> right now I don't have the time to do this.
\r
103 I re-did it. This time I used the Emacs interface, searched for
\r
104 folder:orgmode date 64 bit 32
\r
105 and in the notmuch-search -buffer I used notmuch-search-stash-thread-id to
\r
106 get the internal thread-number. I then did a
\r
108 notmuch show --format=mbox thread:00000000000108e0 >thread.mbox
\r
110 opened this mbox with mutt, saved the one thread about dates
\r
111 before 1970 in one maildir
\r
112 `date64bit32-I-am-interested-in.mailbox' and the rest in a
\r
113 maildir `other-e-mails.mailbox'.
\r
115 I produced a list of all Message-Ids of the interesting thread by
\r
118 rgrep -E -i "^Message-Id:[[:space:]]" date64bit32-I-am-interested-in.mailbox|egrep -o "[^<]+@[^>]+" >date64bit32-I-am-interested-in.mid
\r
120 and searched for this strings in the other e-mails:
\r
122 rgrep -F date64bit32-I-am-interested-in.mid other-e-mails.mailbox
\r
126 I also did it the other way around:
\r
128 rgrep -E -i "^Message-Id:[[:space:]]" other-e-mails.mailbox|egrep -o "[^<]+@[^>]+" >other-e-mails.mid
\r
130 rgrep -F other-e-mails.mid date64bit32-I-am-interested-in.mailbox
\r
134 (I spared me the hassle to search for the Message-Ids in correct
\r
135 headers only, there are simply no hits anywhere in this other e-mails.
\r
137 Thus I conclude that notmuch amalgamates different e-mail-threads
\r
138 into one as represented by one thread-id.
\r
140 I consider this a bug.
\r
142 If anybody is interested I can email her/him the mbox file with
\r
143 the relevant thread (minus privacy relevant headers / 300 KiB gzipped).
\r
145 > Do you have an mbox file in the maildir indexed by notmuch? That seems
\r
148 I don't think so: I rgreped for files with more than 1 line
\r
149 beginning with "Message-Id". I got 38 hits. I looked at all of
\r
150 them, they are no mbox files (at least no valid ones) but e-mails
\r
151 with other e-mails attached, or cited or in one case a
\r
152 multipart/mixed message with plain text part and html part.
\r
154 Nonetheless I isolated all Message-Ids from these 38 files,
\r
155 eliminated some html artefacts and greped for this in
\r
156 date64bit32-I-am-interested-in.mailbox and other-e-mails.mailbox:
\r
157 No hits with either file. I also did it the other way around:
\r
158 Searching for the Message-ids of the two sets in the 38 potential
\r
159 mbox files: No hit.
\r
163 -... --- .-. . -.. ..--.. ...-.-
\r