From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by arlo.cworth.org (Postfix) with ESMTP id 62A7F6DE019C for ; Wed, 2 Aug 2017 16:35:53 -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 gdhC5dAcE3g0 for ; Wed, 2 Aug 2017 16:35:52 -0700 (PDT) Received: from che.mayfirst.org (che.mayfirst.org [162.247.75.118]) by arlo.cworth.org (Postfix) with ESMTP id 7EA796DE00E8 for ; Wed, 2 Aug 2017 16:35:52 -0700 (PDT) Received: from fifthhorseman.net (unknown [38.109.115.130]) by che.mayfirst.org (Postfix) with ESMTPSA id 71F27F999 for ; Wed, 2 Aug 2017 19:35:49 -0400 (EDT) Received: by fifthhorseman.net (Postfix, from userid 1000) id F386D209FF; Wed, 2 Aug 2017 19:35:47 -0400 (EDT) From: Daniel Kahn Gillmor To: Notmuch Mail Subject: associating a property with a subpart of a message Date: Wed, 02 Aug 2017 19:35:45 -0400 Message-ID: <87wp6lbl0u.fsf@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.23 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: Wed, 02 Aug 2017 23:35:53 -0000 --=-=-= Content-Type: text/plain hey folks-- I have some message properties i'd like to cache in notmuch that strictly apply to specific subparts of the message. (e.g. session keys for an encrypted part, signature verification status of a signed part) let's assume that for any given copy of a message, we have a reliable "address" scheme for a part (e.g. "1.2.1.1"). However, this becomes confusing with multiple copies of a given message. It's possible that one copy of the message has one MIME structure, but mangling (by MTAs, mailing lists, etc) result in a different MIME structure in another copy. For cryptographic properties, it might be nice to associate a subpart with a particular cryptographic digest of the subpart itself. Alternately, from a filesystem perspective, maybe it would be better to label the subpart based on the underlying physical file, and the subpart's "address". Are there other options? If you wanted to associate a message property with a subpart of a given message in a way that was reliable, especially in this new era of multiple copies of a message, how would you do it? --dkg --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEOCdgUepHf6PklTkyFJitxsGSMjcFAlmCYdEACgkQFJitxsGS Mjc0yg/+J8D02oCUW17KK791ol3Hx3GfVFNUeZ/PHEwJ26kV7glv8inp0KEMwySg /N1t1PgoRrZju5jFHBPL7PBty8sZIhAZ4rILNM6VIgn2cG5Vi9C2P9dBMI/e/AYc KNbHZlalN2GWbla5rpW7MwtdOi4litlEYjSHFrzJIwTypVm4ZA61fpu2pYOHJTpZ cHRfbsYmbqBfrJoyjhzEY4VOdImTXSldYLH/8uELD3RuT50pOpI6hKsy8QoEUMWh adwfGLD5mn5qRn7u/pT2lF1WqavCj9rTs6IZHDNGwx1jgzi6B27a8sRIQNpoWjJK 6PGYtcXA/MmVWE8lJahyTdPIcvyklFN87RN+xdI0EMQVx7Ru2nGm8UZy2fM4cTNm 67Z1U42czYOzT1gbljjOGkEIEmZXyum3tynqXODBFoy7VNwGZ85mNkIgtGGK+plp E3E40JTprDP/cjr//TYxnuXAGpH1cyts9CbVadIDJbATEF4zZZsMjl7lt2lsDh1t FaSCVjksdMaoIfD9KRIsi8mkq3MBmV9GcIm9FdfenpLf2qV/oRHOZZnGthp88pWJ 4OBi4gtpxNm96JW5V12R7h1abBgEOncxUJ/+a5XvOVu3K3AQ7gYWsmWR3+VCKxnE 7M6KXlsGkMX/HJDFlIDCaUrVf7YHb52xH4mbG7JcqNd8xcppKIU= =OK11 -----END PGP SIGNATURE----- --=-=-=--