Return-Path: <xuwang762@gmail.com>
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 D075A6DE09FB
 for <notmuch@notmuchmail.org>; Sat, 12 Sep 2015 21:03:24 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at cworth.org
X-Spam-Flag: NO
X-Spam-Score: -0.566
X-Spam-Level: 
X-Spam-Status: No, score=-0.566 tagged_above=-999 required=5
 tests=[AWL=-0.015, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
 DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25,
 FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001,
 SPF_PASS=-0.001] 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 znL2C1M3W3iG for <notmuch@notmuchmail.org>;
 Sat, 12 Sep 2015 21:03:23 -0700 (PDT)
Received: from mail-oi0-f44.google.com (mail-oi0-f44.google.com
 [209.85.218.44])
 by arlo.cworth.org (Postfix) with ESMTPS id 128E56DE0275
 for <notmuch@notmuchmail.org>; Sat, 12 Sep 2015 21:03:23 -0700 (PDT)
Received: by oixx17 with SMTP id x17so61715974oix.0
 for <notmuch@notmuchmail.org>; Sat, 12 Sep 2015 21:03:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:date:message-id:subject:from:to:content-type;
 bh=AIfUzangb83s2+PDrmdomuhdgXeYnj/nBRXayoe8eSA=;
 b=q5mWAfxkaHm0Vgyfy0wMmUdZBdHIoH84pxFFyNhvtoz2Jk2fKOWaabF9w5Gu8EDNPc
 mHnudYYZznmkfEpjPAXjcKu9C8VCLawxboqIJeXK9v1g4WxJLSh5m99xAHDjrDA+K4Ty
 2dcf9XPkFmF8/aUgE1TFXBIGBWemQIG09Mw1TPUPMLf67M9tyip/Ygi/juk5Wegil2Ls
 TceG878CnwdSdGThV5OVQ5MxNazAg5ZnS0M5BM+9AiGsQqYEbGRGkZaJPVF4ehZMmN9j
 63UfI6sN8b4Mze0V2vSbJXvimUS5fYIPdOMy7201VNbPTnkwA2c6VQB841PwYHRrbdv0
 V3OA==
MIME-Version: 1.0
X-Received: by 10.202.64.3 with SMTP id n3mr5296710oia.53.1442117001005; Sat,
 12 Sep 2015 21:03:21 -0700 (PDT)
Received: by 10.202.212.204 with HTTP; Sat, 12 Sep 2015 21:03:20 -0700 (PDT)
Date: Sun, 13 Sep 2015 00:03:20 -0400
Message-ID:
 <CAJhTkNh7_hXDLsAGyD7nwkXV4ca6ymkLtFG945USvfqK4ZJEdQ@mail.gmail.com>
Subject: Possible some threads are not complete due to bug?
From: Xu Wang <xuwang762@gmail.com>
To: notmuch@notmuchmail.org
Content-Type: text/plain; charset=UTF-8
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, 13 Sep 2015 04:03:24 -0000

Hi,

Sometimes I need to do:

$ notmuch search --output=threads "id:MYMSGID"
thread:000000000000a125
$ notmuch search --output=messages "thread:000000000000a125"

In theory, this should output the message that responded to message ID
"MYMSGID". Sometimes it works. But sometimes it does not work. That
is, there exists an email where I am sure (I checked the raw email)
that there is a header
In-Reply-To: <MYMSGID>
but that email does not show when I do the two commands above.
Indeed, that mail belongs to a different thread ID.

I am just curious if the above is due to:

1. My missing of understanding of how notmuch deals with threads
2. A bug or missing feature in notmuch causes some threads to be incomplete

By the way, my goal is to use Suvayu's script to check if a message
was responded to.

Kind regards,

Xu