1 Return-Path: <m.walters@qmul.ac.uk>
\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 BF35A429E34
\r
6 for <notmuch@notmuchmail.org>; Mon, 30 Jan 2012 17:17:54 -0800 (PST)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=1.401 tagged_above=-999 required=5
\r
12 tests=[DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001,
\r
13 FREEMAIL_REPLY=2.499, NML_ADSP_CUSTOM_MED=1.2, RCVD_IN_DNSWL_MED=-2.3]
\r
15 Received: from olra.theworths.org ([127.0.0.1])
\r
16 by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)
\r
17 with ESMTP id jZPRLSYy+bu2 for <notmuch@notmuchmail.org>;
\r
18 Mon, 30 Jan 2012 17:17:54 -0800 (PST)
\r
19 Received: from mail2.qmul.ac.uk (mail2.qmul.ac.uk [138.37.6.6])
\r
20 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
\r
21 (No client certificate requested)
\r
22 by olra.theworths.org (Postfix) with ESMTPS id C1E5A431FBC
\r
23 for <notmuch@notmuchmail.org>; Mon, 30 Jan 2012 17:17:53 -0800 (PST)
\r
24 Received: from smtp.qmul.ac.uk ([138.37.6.40])
\r
25 by mail2.qmul.ac.uk with esmtp (Exim 4.71)
\r
26 (envelope-from <m.walters@qmul.ac.uk>)
\r
27 id 1Rs2M1-0008HJ-Rb; Tue, 31 Jan 2012 01:17:50 +0000
\r
28 Received: from 94-192-233-223.zone6.bethere.co.uk ([94.192.233.223]
\r
30 by smtp.qmul.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69)
\r
31 (envelope-from <m.walters@qmul.ac.uk>)
\r
32 id 1Rs2M1-0005Rc-E1; Tue, 31 Jan 2012 01:17:49 +0000
\r
33 From: Mark Walters <markwalters1009@gmail.com>
\r
34 To: Gregor Zattler <telegraph@gmx.net>, notmuch <notmuch@notmuchmail.org>
\r
35 Subject: Re: Bug?: notmuch-search-show-thread shows several threads;
\r
36 only one containing matching messages
\r
37 In-Reply-To: <20120130223416.GA26239@shi.workgroup>
\r
38 References: <20120126004024.GA13704@shi.workgroup>
\r
39 <20120126011903.GA1176@mit.edu>
\r
40 <8762fzry7k.fsf@servo.finestructure.net>
\r
41 <20120126124450.GB30209@shi.workgroup> <87mx9avbc1.fsf@praet.org>
\r
42 <20120129234213.GB11460@shi.workgroup> <87zkd5655g.fsf@praet.org>
\r
43 <20120130190425.GB13521@shi.workgroup> <878vkoev95.fsf@qmul.ac.uk>
\r
44 <20120130223416.GA26239@shi.workgroup>
\r
45 User-Agent: Notmuch/0.11+137~g98adc3d (http://notmuchmail.org) Emacs/23.2.1
\r
47 Date: Tue, 31 Jan 2012 01:18:55 +0000
\r
48 Message-ID: <874nvcekjk.fsf@qmul.ac.uk>
\r
50 Content-Type: text/plain; charset=us-ascii
\r
51 X-Sender-Host-Address: 94.192.233.223
\r
52 X-QM-SPAM-Info: Sender has good ham record. :)
\r
53 X-QM-Body-MD5: 6919f6b6598f2a54f2db22f0a2fb9248 (of first 20000 bytes)
\r
54 X-SpamAssassin-Score: -1.2
\r
55 X-SpamAssassin-SpamBar: -
\r
56 X-SpamAssassin-Report: The QM spam filters have analysed this message to
\r
58 spam. We require at least 5.0 points to mark a message as spam.
\r
59 This message scored -1.2 points.
\r
60 Summary of the scoring:
\r
61 * -2.3 RCVD_IN_DNSWL_MED RBL: Sender listed at http://www.dnswl.org/,
\r
63 * [138.37.6.40 listed in list.dnswl.org]
\r
64 * 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail
\r
65 provider * (markwalters1009[at]gmail.com)
\r
66 * -0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay
\r
68 * 1.0 FREEMAIL_REPLY From and body contain different freemails
\r
69 * 0.1 AWL AWL: From: address is in the auto white-list
\r
70 X-QM-Scan-Virus: ClamAV says the message is clean
\r
71 X-BeenThere: notmuch@notmuchmail.org
\r
72 X-Mailman-Version: 2.1.13
\r
74 List-Id: "Use and development of the notmuch mail system."
\r
75 <notmuch.notmuchmail.org>
\r
76 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
77 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
78 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
79 List-Post: <mailto:notmuch@notmuchmail.org>
\r
80 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
81 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
82 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
83 X-List-Received-Date: Tue, 31 Jan 2012 01:17:54 -0000
\r
85 On Mon, 30 Jan 2012 23:34:16 +0100, Gregor Zattler <telegraph@gmx.net> wrote:
\r
87 > * Mark Walters <markwalters1009@gmail.com> [30. Jan. 2012]:
\r
88 > > On Mon, 30 Jan 2012 20:04:25 +0100, Gregor Zattler <telegraph@gmx.net> wrote:
\r
89 > >> * Pieter Praet <pieter@praet.org> [30. Jan. 2012]:
\r
90 > >>> On Mon, 30 Jan 2012 00:42:14 +0100, Gregor Zattler <telegraph@gmx.net> wrote:
\r
91 > >>>> * Pieter Praet <pieter@praet.org> [26. Jan. 2012]:
\r
92 > >>>>> Here's another couple of threads squashed into a single one:
\r
93 > >>>>> - [O] [Use Question] Capture and long lines
\r
94 > >>>>> - id:"BANLkTikoF4tXuNLLufRzNSD6k2ZYs7sUcg@mail.gmail.com"
\r
95 > >>>>> - [O] Worg update
\r
96 > >>>>> - id:"m1wrfiz3ch.fsf@tsdye.com"
\r
97 > >>>>> - [O] Table formula to convert hex to dec
\r
98 > >>>>> - id:"20110724080054.GB16388@x201"
\r
99 > >>>>> - [O] ICS import?
\r
100 > >>>>> - id:"20120125173421.GQ3747@x201"
\r
103 > >>>>> AFAICT, none of them share Message-Id's...
\r
105 > >>>> Do you consider this a bug?
\r
108 > >>> I do. No idea what causes it or how to fix it though... :)
\r
110 > >> First I thougt it' not a severe bug since one see's more not less
\r
111 > >> messages in notmuch show buffer. But later I realised one also
\r
112 > >> sees less not more threads in notmuch search buffer and might not
\r
113 > >> read certain notmuch threads because of "wrong" $Subject: in
\r
114 > >> notmuch search buffer.
\r
116 > > I think notmuch links two messages into the same thread if they have an
\r
117 > > in-reply-to or reference header in common: i.e the messages reference a
\r
118 > > common parent message. (See comment in lib/database.cc "Even before a
\r
119 > > message is added, it's pre-allocated thread ID is useful so that all
\r
120 > > descendant messages that reference this common parent can be recognized
\r
121 > > as belonging to the same thread.")
\r
123 > So in case message a from thread A and message b from B would
\r
124 > name the same Message c in their In-Reoply-To:/References:
\r
125 > headers, while c is not (for some reason) in A or B, notmuch
\r
126 > would assume both threads linked? Makes sense.
\r
128 > > As far as I can see your grep tests haven't checked for that.
\r
132 > > Also, could you email me the mbox you had (I think you said that it was
\r
133 > > a mailing list so all public) and I will take a look?
\r
135 > Sure, I do so off-list because of the size of the attachment.
\r
139 I have looked at this and I think this is not notmuch's fault: I think
\r
140 it is a mua doing strange things:
\r
142 One of the mails has an in-reply-to header which looks like
\r
144 In-reply-to: Message from Carsten Dominik <carsten.dominik@gmail.com> of "Tue, 15 Mar 2011 12:18:51 BST." <17242340-A14F-495A-B144-20C96D52B620@gmail.com>
\r
146 and I think notmuch is taking the carsten.dominik@gmail.com as message
\r
149 A similar in-reply-to header appears in the other thread so notmuch
\r
150 pairs them up. According to http://www.jwz.org/doc/threading.html this
\r
151 form of header is not allowed under RFC2822 but was allowed under the
\r
154 You can see several such messages on the gnu-mailing list site eg
\r
156 ftp://lists.gnu.org/emacs-orgmode/2011-11
\r
158 search for "in-reply-to: M" but they all appear to be from the same
\r
159 person (running mh-e 8.3 nmh under emacs 24)
\r
161 In my collection from the linux kernel mailing list I get some examples
\r
162 of in-reply-to not just being : <msg-id> but it was only about 200 from
\r
163 100,000 messages in the second half of 2010 (the most recent archives I
\r
projects / notmuch-archives.git / blob