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 5FFB06DE02CC for ; Sun, 22 May 2016 07:29:19 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: -0.012 X-Spam-Level: X-Spam-Status: No, score=-0.012 tagged_above=-999 required=5 tests=[AWL=-0.001, 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 mkrq_l7gw-HA for ; Sun, 22 May 2016 07:29:11 -0700 (PDT) Received: from fethera.tethera.net (fethera.tethera.net [198.245.60.197]) by arlo.cworth.org (Postfix) with ESMTPS id 65DF86DE0231 for ; Sun, 22 May 2016 07:29:10 -0700 (PDT) Received: from remotemail by fethera.tethera.net with local (Exim 4.84) (envelope-from ) id 1b4UNH-00050Z-MC for notmuch@notmuchmail.org; Sun, 22 May 2016 10:28:59 -0400 Received: (nullmailer pid 5511 invoked by uid 1000); Sun, 22 May 2016 14:29:06 -0000 From: David Bremner To: notmuch@notmuchmail.org Subject: RFC: message property API Date: Sun, 22 May 2016 11:28:57 -0300 Message-Id: <1463927339-5441-1-git-send-email-david@tethera.net> X-Mailer: git-send-email 2.8.1 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: Sun, 22 May 2016 14:29:19 -0000 People (or maybe just dkg) have proposed various bits of user metadata to attach to messages - references to be added or blacklisted - encryption related key material Since such metadata would be not-reproducible from the message files, it would be "precious" and need a backup/restore path. This is a prototype of a library API to support that. Some things to note: - This is tested on top of my libconfig [1] series, but I think there is no logical dependency - there are no docs, see the tests - this is just the low level api; it would need to be extended in a similar way to the libconfig series to dump and restore metadata. This might require modifying/extending the API to dump all properties for a message. That should be a relatively small change. - it also be useful to be able delete all (key,value) pairs with a given key. - this should really go through the existing caching mechanism used by e.g. tags, or at least not invalidate that cache. [1] id:1463135893-7471-6-git-send-email-david@tethera.net