--- /dev/null
+Return-Path: <xuwang762@gmail.com>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+ by arlo.cworth.org (Postfix) with ESMTP id 369EA6DE015B\r
+ for <notmuch@notmuchmail.org>; Sat, 2 Jul 2016 17:28:52 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at cworth.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -0.595\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-0.595 tagged_above=-999 required=5 tests=[AWL=0.166,\r
+ DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1,\r
+ FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7,\r
+ RCVD_IN_MSPIKE_H2=-0.211, SPF_PASS=-0.001] autolearn=disabled\r
+Received: from arlo.cworth.org ([127.0.0.1])\r
+ by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024)\r
+ with ESMTP id snCjiCoeqSWw for <notmuch@notmuchmail.org>;\r
+ Sat, 2 Jul 2016 17:28:44 -0700 (PDT)\r
+Received: from mail-oi0-f47.google.com (mail-oi0-f47.google.com\r
+ [209.85.218.47])\r
+ by arlo.cworth.org (Postfix) with ESMTPS id EAE966DE0032\r
+ for <notmuch@notmuchmail.org>; Sat, 2 Jul 2016 17:28:43 -0700 (PDT)\r
+Received: by mail-oi0-f47.google.com with SMTP id f189so155789629oig.3\r
+ for <notmuch@notmuchmail.org>; Sat, 02 Jul 2016 17:28:43 -0700 (PDT)\r
+DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;\r
+ h=mime-version:from:date:message-id:subject:to;\r
+ bh=KVbLeJOsUH0xnpVRI8svq+SC6pzjlsFbDaSxV6doIPM=;\r
+ b=JF3yFAYiFJaAVLY2Jat6Sl39zbGLF3P7Nc5Vlosf73PUWCNV1uyAl/YV5i6vV77pZM\r
+ 5jSO9OuAbFs38Td2Y/ikASLasr1vnXoQh+u92xgP6L/AM8Z8fTU9eiuIYY5wLRA92KT3\r
+ Qc9JkrTcIVsTVNUzPb4pkqpDc4ycWTZrAgDzTe7NnpEK4pT3riVHzr89NpzMyK2yBIr5\r
+ zAm1aFksidFjXpQwlH7vzO8oSIsCPiMV9EQAclo7RTESlpS2Pv4vSwTAnJ+FctA3URb7\r
+ pcdzbXxoh2+zW1bjg68k6ET9mnBFwvTuvPjHxTC8dbmNyz9omBQSuBhCtZU2MHZ7HY5H\r
+ ynIQ==\r
+X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;\r
+ d=1e100.net; s=20130820;\r
+ h=x-gm-message-state:mime-version:from:date:message-id:subject:to;\r
+ bh=KVbLeJOsUH0xnpVRI8svq+SC6pzjlsFbDaSxV6doIPM=;\r
+ b=YbNO8F7s2O/nY2T4kiKoTgHdkbHT6EUMNklfnPnpavnIRACGIeNJMXlNN/7bkicCD+\r
+ Eb91KToCRPvmoym9okQWSBC7dY3mJd0KAZhfwIdwlDkRCAECTmLKVaCDnlK5jHEYQYaD\r
+ nzmmGOdQqkg/hAesgY4wju8B58Rr1PBIba6gFxsiVWT/Me+wytNQJMTxLt1INMfmbAHX\r
+ mktIDMXIpLsBd+jXlGNHBv0mEiSGdygWV3evrWNK9m/08q52vEErrdHp5KimmgJT/6OX\r
+ ciQ6y4Cqi+RlZ7tsSCiYmKK/liDGCl0g4KTbqrSCuo5vJ2L8AbpPxEcanfJPDkeaoXi/\r
+ KuWQ==\r
+X-Gm-Message-State: ALyK8tKmYPRVxE89fVMauz4FKbLkEf8EL0r/dQi9P9V+6VajRNcLeFtNZaqRtyUgY6zX5p6xdizGtDyIIHJm8Q==\r
+X-Received: by 10.202.102.35 with SMTP id a35mr3213358oic.40.1467505721827;\r
+ Sat, 02 Jul 2016 17:28:41 -0700 (PDT)\r
+MIME-Version: 1.0\r
+Received: by 10.202.212.67 with HTTP; Sat, 2 Jul 2016 17:28:41 -0700 (PDT)\r
+From: Xu Wang <xuwang762@gmail.com>\r
+Date: Sat, 2 Jul 2016 20:28:41 -0400\r
+Message-ID:\r
+ <CAJhTkNiWvED4+7kAEWxWOD2PLyskG27vTfSbmZhJFUJcoBqXag@mail.gmail.com>\r
+Subject: ask notmuch to find back "reply-to's"\r
+To: notmuch@notmuchmail.org\r
+Content-Type: text/plain; charset=UTF-8\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.20\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+ <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <https://notmuchmail.org/mailman/options/notmuch>,\r
+ <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
+List-Archive: <http://notmuchmail.org/pipermail/notmuch/>\r
+List-Post: <mailto:notmuch@notmuchmail.org>\r
+List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
+List-Subscribe: <https://notmuchmail.org/mailman/listinfo/notmuch>,\r
+ <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Sun, 03 Jul 2016 00:28:52 -0000\r
+\r
+Hello all,\r
+\r
+I have a situation where sometimes I sync a later message. For\r
+example, the following happens on times:\r
+\r
+1a. sync message 1.\r
+1b. not much new\r
+2a. sync message 3 (which replied to message 2)\r
+2b. not much new\r
+3. sync message 2 (which replied to message 1)\r
+3b. not much new\r
+\r
+This happens because of my workflow of offlineimap. It takes a long\r
+time to sync some folders so often I prefer to skip, but sometimes\r
+they contain replies.\r
+\r
+When I do that, notmuch does not correctly construct the linkages. I\r
+think this is understandable and I blame my workflow more than\r
+notmuch. notmuch wants to be as fast as possible so when it processes\r
+message 2 in step 3b, it does not check message 3 because it already\r
+checked message 3 in 2b so I think it skips it. Do I have correct\r
+understanding of the situation?\r
+\r
+Is there a config setting that I can put to ask notmuch to look both\r
+ways (even at cost of spending more time)? i.e. I want notmuch in step\r
+3b to search through all previous messages to see if they replied to\r
+it.\r
+\r
+Kind regards,\r
+\r
+Xu\r