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