Return-Path: <david@tethera.net>
X-Original-To: notmuch@notmuchmail.org
Delivered-To: notmuch@notmuchmail.org
Received: from localhost (localhost [127.0.0.1])
 by arlo.cworth.org (Postfix) with ESMTP id ED2186DE19B7
 for <notmuch@notmuchmail.org>; Sun,  4 Oct 2015 03:59:22 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at cworth.org
X-Spam-Flag: NO
X-Spam-Score: 0.104
X-Spam-Level: 
X-Spam-Status: No, score=0.104 tagged_above=-999 required=5 tests=[AWL=0.104]
 autolearn=disabled
Received: from arlo.cworth.org ([127.0.0.1])
 by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id StwmbIPFxSQt for <notmuch@notmuchmail.org>;
 Sun,  4 Oct 2015 03:59:18 -0700 (PDT)
Received: from gitolite.debian.net (gitolite.debian.net [87.98.215.224])
 by arlo.cworth.org (Postfix) with ESMTPS id DCC3D6DE19AA
 for <notmuch@notmuchmail.org>; Sun,  4 Oct 2015 03:59:17 -0700 (PDT)
Received: from remotemail by gitolite.debian.net with local (Exim 4.80)
 (envelope-from <david@tethera.net>)
 id 1ZigzA-0002DM-Is; Sun, 04 Oct 2015 10:57:44 +0000
Received: (nullmailer pid 8932 invoked by uid 1000); Sun, 04 Oct 2015
 10:57:25 -0000
From: David Bremner <david@tethera.net>
To: Xu Wang <xuwang762@gmail.com>
Subject: Re: Possible some threads are not complete due to bug?
In-Reply-To:
 <CAJhTkNhp=mMPsD7hkGKW4eY9WWOuS2pf=x4sDiLnx9ref9JTew@mail.gmail.com>
References:
 <CAJhTkNh7_hXDLsAGyD7nwkXV4ca6ymkLtFG945USvfqK4ZJEdQ@mail.gmail.com>
 <87fv2a4ctt.fsf@zancas.localnet>
 <CAJhTkNgBdnm18UXC95ryJk5w7fJpa7-1LvdugV3S29fL4kxxhQ@mail.gmail.com>
 <87zj0c3gei.fsf@zancas.localnet>
 <CAJhTkNhp=mMPsD7hkGKW4eY9WWOuS2pf=x4sDiLnx9ref9JTew@mail.gmail.com>
User-Agent: Notmuch/0.20.2+93~g33c8777 (http://notmuchmail.org) Emacs/24.5.1
 (x86_64-pc-linux-gnu)
Date: Sun, 04 Oct 2015 07:57:25 -0300
Message-ID: <87oage9a0a.fsf@zancas.localnet>
MIME-Version: 1.0
Content-Type: text/plain
Cc: notmuch@notmuchmail.org
X-BeenThere: notmuch@notmuchmail.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: "Use and development of the notmuch mail system."
 <notmuch.notmuchmail.org>
List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
List-Archive: <http://notmuchmail.org/pipermail/notmuch/>
List-Post: <mailto:notmuch@notmuchmail.org>
List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Oct 2015 10:59:23 -0000

Xu Wang <xuwang762@gmail.com> writes:

>
> $ notmuch search --output=threads "id:MYMSGID"
> thread:000000000000a125
> $ notmuch search --output=messages "thread:000000000000a125"
> id:MYMSGID
> $
> # I know that MYMSGIDREPLY did respond to that message. I have it in
> my mutt mailbox and it shows the down-right arrow signifying this. I
> inspect the headers and there is indeed a header in MYMSGIDREPLY that
> says "In-Reply-To: <MYMSGID>". I then do...
> $ notmuch search --output=threads "id:MYMSGIDREPLY"
> thread:000000000000c125
> $ notmuch search --output=messages "thread:000000000000c125"
> id:MYMSGIDREPLY
> $

If the thread-id's are accurate, then it looks like the two messages are
not in the same thread according to notmuch (it's easy to be fooled
because the thread-ids are so similar).  I can't really explain how
those messages might have ended up in different threads. 

  - One potential issue is that if message ids are extra long or badly
  formed, then notmuch might make up a new message id. In that case your
  thread-id search wouldn't work at all.

  - If there are actually multiple (unrelated) files with message-id
    MYMSGIDREPLY, then the indexed one might not have the in-reply-to
    header. But in this case you could tell by

    notmuch show id:MYMSGIDREPLY

    and/or

    notmuch search --output=files id:MSGIDREPLY

In order for the thread-ids to change when you run "notmuch new", I
_think_ that there has to be a third message in the thread disovered.

So it's a mystery. If it happens again with public messages, it would be
worth sharing the messages (as attachements) with the list, just in case
there is something in the headers that explains it.