Return-Path: X-Original-To: notmuch@notmuchmail.org Delivered-To: notmuch@notmuchmail.org Received: from localhost (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id A73E5431FBC for ; Wed, 13 Jan 2010 17:37:52 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: -1.822 X-Spam-Level: X-Spam-Status: No, score=-1.822 tagged_above=-999 required=5 tests=[ALL_TRUSTED=-1.8, AWL=-0.023, BAYES_50=0.001] autolearn=ham Received: from olra.theworths.org ([127.0.0.1]) by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ivSHd7rWAHe2; Wed, 13 Jan 2010 17:37:52 -0800 (PST) Received: from yoom.home.cworth.org (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id 07699431FAE; Wed, 13 Jan 2010 17:37:52 -0800 (PST) Received: by yoom.home.cworth.org (Postfix, from userid 1000) id B13FB254090; Wed, 13 Jan 2010 17:37:51 -0800 (PST) From: Carl Worth To: Scott Morrison , mailtags discussion list In-Reply-To: References: <20100111221909.GA30299@lapse.rw.madduck.net> <20100113012404.GA570@lapse.rw.madduck.net> Date: Wed, 13 Jan 2010 17:37:51 -0800 Message-ID: <87fx69fouo.fsf@yoom.home.cworth.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" Cc: notmuch discussion list Subject: Re: [notmuch] Idea for storing tags X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.13 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: Thu, 14 Jan 2010 01:37:52 -0000 --=-=-= Content-Transfer-Encoding: quoted-printable On Wed, 13 Jan 2010 00:39:14 -0500, Scott Morrison wrote: > > Maybe a better approach would be content addressing (see below). >=20 > Content hashing -- good Idea (& not something that has hit me before) > -- better than Message-Id as I believe there are still some MUA /MTAs > that allow messages without message ids. The only potential issue > with this is that it is critical then to preserve the message source > against encoding changes though that shouldn't be too hard to avoid. Another problem with content-based naming for messages is that most of the messages in my mail store that I consider duplicates don't actually have identical content. (One is sent directly to me via CC and the other is sent by the mailing-list software *after* appending a footer to the message.) That said, notmuch already does use a sha-1 sum as the message identifier for any message that does not have a valid Message-ID header. So there's definitely a place for this. =2DCarl --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iD8DBQFLTnVv6JDdNq8qSWgRAgxEAKCR7kf3N38d3EmMOApkjdJ0Bx2VYgCgjU0P 6YCckJU5Ai6jSL44RVeQtRM= =ojb5 -----END PGP SIGNATURE----- --=-=-=--