1 Return-Path: <xuwang762@gmail.com>
\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 arlo.cworth.org (Postfix) with ESMTP id 5A78B6DE025E
\r
6 for <notmuch@notmuchmail.org>; Sun, 4 Oct 2015 20:52:17 -0700 (PDT)
\r
7 X-Virus-Scanned: Debian amavisd-new at cworth.org
\r
11 X-Spam-Status: No, score=-0.135 tagged_above=-999 required=5
\r
12 tests=[AWL=-0.309, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
\r
13 DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25,
\r
14 FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01,
\r
15 RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_SBL=0.644,
\r
16 URIBL_SBL_A=0.1] autolearn=disabled
\r
17 Received: from arlo.cworth.org ([127.0.0.1])
\r
18 by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024)
\r
19 with ESMTP id bNZUHMc2Ng2c for <notmuch@notmuchmail.org>;
\r
20 Sun, 4 Oct 2015 20:52:15 -0700 (PDT)
\r
21 Received: from mail-ob0-f170.google.com (mail-ob0-f170.google.com
\r
23 by arlo.cworth.org (Postfix) with ESMTPS id 28C8E6DE0173
\r
24 for <notmuch@notmuchmail.org>; Sun, 4 Oct 2015 20:52:15 -0700 (PDT)
\r
25 Received: by obbbh8 with SMTP id bh8so119477357obb.0
\r
26 for <notmuch@notmuchmail.org>; Sun, 04 Oct 2015 20:52:13 -0700 (PDT)
\r
27 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
\r
28 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
\r
30 bh=dTFbIN7FvbRAnWvfWCxg6/UvF/F6fOSNqGO+YbhkKiU=;
\r
31 b=WErtSfnGgeT7FXKFOtjtLuGdfx4NpLk/EBRAUd+GbcgyyMKz1t5DhsIYhdRy/XDEw+
\r
32 RKV790G4WiLX3zvuyllnE3DKYrLgFim7fP6wfLk01V9mhHCNp7lofkLG39Tx4352HCXH
\r
33 DNyHbRyP85PSEgki9LWPE8BaEbD5t/RUODNVI9zQOzsR4105V3czVDzcOQhk9/oBq0PJ
\r
34 oMGBB0Vfae/b4VuFHyxXq1IWysYiuqwrFOOux3A3HDKbT0yQQ+9mu4Uk5K04TZq8t4fW
\r
35 iRTdfhAr8Zup4kbl8qlyvrghLL+Lae02SqFE64cn5GdfdLTEGaGh7RGi7HLJcG+tslOK
\r
38 X-Received: by 10.182.138.40 with SMTP id qn8mr16761131obb.78.1444017133805;
\r
39 Sun, 04 Oct 2015 20:52:13 -0700 (PDT)
\r
40 Received: by 10.202.212.204 with HTTP; Sun, 4 Oct 2015 20:52:13 -0700 (PDT)
\r
41 In-Reply-To: <87oage9a0a.fsf@zancas.localnet>
\r
43 <CAJhTkNh7_hXDLsAGyD7nwkXV4ca6ymkLtFG945USvfqK4ZJEdQ@mail.gmail.com>
\r
44 <87fv2a4ctt.fsf@zancas.localnet>
\r
45 <CAJhTkNgBdnm18UXC95ryJk5w7fJpa7-1LvdugV3S29fL4kxxhQ@mail.gmail.com>
\r
46 <87zj0c3gei.fsf@zancas.localnet>
\r
47 <CAJhTkNhp=mMPsD7hkGKW4eY9WWOuS2pf=x4sDiLnx9ref9JTew@mail.gmail.com>
\r
48 <87oage9a0a.fsf@zancas.localnet>
\r
49 Date: Sun, 4 Oct 2015 23:52:13 -0400
\r
51 <CAJhTkNjbY_Q9w8v5oDFLtUkfP=Hg9F=ozEBCq1bFmA-+_RV8wA@mail.gmail.com>
\r
52 Subject: Re: Possible some threads are not complete due to bug?
\r
53 From: Xu Wang <xuwang762@gmail.com>
\r
54 To: David Bremner <david@tethera.net>
\r
55 Content-Type: text/plain; charset=UTF-8
\r
56 Cc: notmuch@notmuchmail.org
\r
57 X-BeenThere: notmuch@notmuchmail.org
\r
58 X-Mailman-Version: 2.1.18
\r
60 List-Id: "Use and development of the notmuch mail system."
\r
61 <notmuch.notmuchmail.org>
\r
62 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
63 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
64 List-Archive: <http://notmuchmail.org/pipermail/notmuch/>
\r
65 List-Post: <mailto:notmuch@notmuchmail.org>
\r
66 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
67 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
68 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
69 X-List-Received-Date: Mon, 05 Oct 2015 03:52:17 -0000
\r
71 On Sun, Oct 4, 2015 at 6:57 AM, David Bremner <david@tethera.net> wrote:
\r
72 > Xu Wang <xuwang762@gmail.com> writes:
\r
75 >> $ notmuch search --output=threads "id:MYMSGID"
\r
76 >> thread:000000000000a125
\r
77 >> $ notmuch search --output=messages "thread:000000000000a125"
\r
80 >> # I know that MYMSGIDREPLY did respond to that message. I have it in
\r
81 >> my mutt mailbox and it shows the down-right arrow signifying this. I
\r
82 >> inspect the headers and there is indeed a header in MYMSGIDREPLY that
\r
83 >> says "In-Reply-To: <MYMSGID>". I then do...
\r
84 >> $ notmuch search --output=threads "id:MYMSGIDREPLY"
\r
85 >> thread:000000000000c125
\r
86 >> $ notmuch search --output=messages "thread:000000000000c125"
\r
90 > If the thread-id's are accurate, then it looks like the two messages are
\r
91 > not in the same thread according to notmuch (it's easy to be fooled
\r
92 > because the thread-ids are so similar). I can't really explain how
\r
93 > those messages might have ended up in different threads.
\r
95 > - One potential issue is that if message ids are extra long or badly
\r
96 > formed, then notmuch might make up a new message id. In that case your
\r
97 > thread-id search wouldn't work at all.
\r
99 > - If there are actually multiple (unrelated) files with message-id
\r
100 > MYMSGIDREPLY, then the indexed one might not have the in-reply-to
\r
101 > header. But in this case you could tell by
\r
103 > notmuch show id:MYMSGIDREPLY
\r
107 > notmuch search --output=files id:MSGIDREPLY
\r
109 > In order for the thread-ids to change when you run "notmuch new", I
\r
110 > _think_ that there has to be a third message in the thread disovered.
\r
112 > So it's a mystery. If it happens again with public messages, it would be
\r
113 > worth sharing the messages (as attachements) with the list, just in case
\r
114 > there is something in the headers that explains it.
\r
117 OK I will be careful to document if I find a repeatable example and
\r
118 share with the list. I would like to help in any possible way that I
\r