Re: How does notmuch track mails?

diff --git a/54/a658c7b9e1699e7961a1c189941d51ca070ec8 b/54/a658c7b9e1699e7961a1c189941d51ca070ec8
new file mode 100644 (file)
index 0000000..e13c82d
--- /dev/null
+++ b/54/a658c7b9e1699e7961a1c189941d51ca070ec8
@@ -0,0 +1,97 @@
+Return-Path: <dkg@fifthhorseman.net>\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 026486DE01C2\r
+ for <notmuch@notmuchmail.org>; Tue,  9 Aug 2016 11:50:15 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at cworth.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -0.052\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-0.052 tagged_above=-999 required=5\r
+ tests=[AWL=-0.052] 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 XpzgwxTuQ3wT for <notmuch@notmuchmail.org>;\r
+ Tue,  9 Aug 2016 11:50:05 -0700 (PDT)\r
+Received: from che.mayfirst.org (che.mayfirst.org [162.247.75.118])\r
+ by arlo.cworth.org (Postfix) with ESMTP id 91E016DE015B\r
+ for <notmuch@notmuchmail.org>; Tue,  9 Aug 2016 11:50:05 -0700 (PDT)\r
+Received: from fifthhorseman.net (unknown [38.109.115.130])\r
+ by che.mayfirst.org (Postfix) with ESMTPSA id D8640F993;\r
+ Tue,  9 Aug 2016 14:50:03 -0400 (EDT)\r
+Received: by fifthhorseman.net (Postfix, from userid 1000)\r
+ id 87340200E2; Tue,  9 Aug 2016 14:34:58 -0400 (EDT)\r
+From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>\r
+To: Matthias Beyer <mail@beyermatthias.de>, notmuch@notmuchmail.org\r
+Subject: Re: How does notmuch track mails?\r
+In-Reply-To: <20160809140223.GH3832@yuu>\r
+References: <20160809140223.GH3832@yuu>\r
+User-Agent: Notmuch/0.22.1+88~g8d09e96 (https://notmuchmail.org) Emacs/24.5.1\r
+ (x86_64-pc-linux-gnu)\r
+Date: Tue, 09 Aug 2016 14:34:50 -0400\r
+Message-ID: <87twetvlit.fsf@alice.fifthhorseman.net>\r
+MIME-Version: 1.0\r
+Content-Type: multipart/signed; boundary="=-=-=";\r
+ micalg=pgp-sha512; protocol="application/pgp-signature"\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: Tue, 09 Aug 2016 18:50:15 -0000\r
+\r
+--=-=-=\r
+Content-Type: text/plain\r
+Content-Transfer-Encoding: quoted-printable\r
+\r
+On Tue 2016-08-09 10:02:23 -0400, Matthias Beyer wrote:\r
+\r
+> I wonder how notmuch tracks mails. Lets assume that we have a big\r
+> Maildir tree - mails move around all the time - how does notmuch\r
+> (re)find them? Is there a unique way to identify an email? As far as I\r
+> know isn't the message id one of them, right?\r
+\r
+notmuch uses message-id to identify individual mails.   this is a nice\r
+simplification, but it leaves open some potentially problematic\r
+situations that we have still never resolved (e.g. matching message-ids\r
+on distinct mail, whether via malice or incompetence).\r
+\r
+notmuch has maildir scanning code that is clever about tracking which\r
+parts of various subtrees have changed recently and avoids having to\r
+re-scan them if they haven't changed (this does require some cooperation\r
+From=20the filesystem -- if you have an absolutely terrible filesystem, i\r
+don't know how notmuch would handle the situation).\r
+\r
+        --dkg\r
+\r
+\r
+--=-=-=\r
+Content-Type: application/pgp-signature; name="signature.asc"\r
+\r
+-----BEGIN PGP SIGNATURE-----\r
+\r
+iQJ8BAEBCgBmBQJXqiJKXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w\r
+ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRFREIyRTc0RjU2RkNGMkI2NzI5N0I3MzUy\r
+NEVDRkY1QUZGNjgzNzBBAAoJECTs/1r/aDcKuH4P/Aoayij5LHKnLfFm17MBtK2i\r
++dLJVhwM0n+58LY/frKYD3KRyR0oXhE1f1zo1FA76mS9vHb35t37IahLuYhOwuNZ\r
+YaXHgMwcvwlAseeYDz1gmCRxyJ1LrcFPGrjXWhWoPpFnbKkQc1rPjocOwudNQiiA\r
+PcXHEowjFduX1OFc6q24AxS5RdfcvwHL4/gMoi4Ufvvir2PGAAoETdsU+vhgBfc6\r
+1fAQwHLXLIqX0MrGzQCqdA0PuLCUp/IlehkbGbZIVxPZuo72GiuNcBFfLO5VR6mr\r
+amdYsN+PvgvUUm7q5YpZKyeXZZbhELALc4Bw6Pc0qbpJLmMqjWKTKQI5Uifggm9a\r
+J1jqloDwzTzgWo/JC+wm4BkjeIVq1he0Sbk43NqFbdHWDle333cMM3Xq3xyXrYOE\r
+ae2AyYoxlnuQnSJoG5kVKiulfOAcGPCS4CUJ2UyDn0YuJV+VuzdP5dJlm3SlZDRv\r
+dVmrGhPCsA+GAy6ptL/KC9TUwSn9XmXe+WiBPFlU1QpLSj+y1Otw1z8nWy1aAPs2\r
++pgps8Pa6Wc57RYyuo+X3NQ9OTZpCxMkRafOb/uFKLAgpOTt9NB+/8FmyMkhnlH4\r
+5kCd+SSACLQY2QY5Y04/owr12JNrFVXxkL+sRxR34APLud5QYuV9nIiQ/Orsw05r\r
+a7hXYnhtZab3PX1mSxRS\r
+=zHYD\r
+-----END PGP SIGNATURE-----\r
+--=-=-=--\r