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 CC97A6DE0BF6 for ; Tue, 8 Aug 2017 11:03:02 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: 0 X-Spam-Level: X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[AWL=0.011, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 bwINC_XDZtQr for ; Tue, 8 Aug 2017 11:03:01 -0700 (PDT) Received: from fethera.tethera.net (fethera.tethera.net [198.245.60.197]) by arlo.cworth.org (Postfix) with ESMTPS id 611A76DE0ACB for ; Tue, 8 Aug 2017 11:03:01 -0700 (PDT) Received: from remotemail by fethera.tethera.net with local (Exim 4.89) (envelope-from ) id 1df8mv-0004J4-Gn; Tue, 08 Aug 2017 13:59:29 -0400 Received: (nullmailer pid 4502 invoked by uid 1000); Tue, 08 Aug 2017 18:02:56 -0000 From: David Bremner To: Daniel Kahn Gillmor , Notmuch Mail Subject: Re: associating a property with a subpart of a message In-Reply-To: <87wp6lbl0u.fsf@fifthhorseman.net> References: <87wp6lbl0u.fsf@fifthhorseman.net> Date: Tue, 08 Aug 2017 14:02:56 -0400 Message-ID: <87y3qu3pkf.fsf@tethera.net> MIME-Version: 1.0 Content-Type: text/plain 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: Tue, 08 Aug 2017 18:03:03 -0000 Daniel Kahn Gillmor writes: > 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". A hybrid option would be to use a hash of the file + 1.2.1.1. address scheme. My thinking here is a bit vague, but I can imagine such has hash being useful either for content addressible mailstore, or for disambiguating message-id collisions. d