From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id BC440431FB6 for ; Thu, 14 Apr 2011 00:48:40 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: 0.01 X-Spam-Level: X-Spam-Status: No, score=0.01 tagged_above=-999 required=5 tests=[T_MIME_NO_TEXT=0.01] autolearn=disabled 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 XR23qScrKitW for ; Thu, 14 Apr 2011 00:48:40 -0700 (PDT) Received: from tesla.chaoflow.net (tesla.chaoflow.net [188.40.54.22]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by olra.theworths.org (Postfix) with ESMTPS id CAEB2431FB5 for ; Thu, 14 Apr 2011 00:48:39 -0700 (PDT) Received: from eve.chaoflow.net (p5DE96241.dip.t-dialin.net [93.233.98.65]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: flo@chaoflow.net) by tesla.chaoflow.net (Postfix) with ESMTPSA id 465AC71E; Thu, 14 Apr 2011 09:48:38 +0200 (CEST) Received: by eve.chaoflow.net (Postfix, from userid 1000) id EA350B3A; Thu, 14 Apr 2011 07:48:37 +0000 (Local time zone must be set--see zic manual page) From: Florian Friesdorf To: Jameson Rollins , notmuch Subject: Re: signed/encrypted tagging in crypto branch In-Reply-To: <87bp1o83ij.fsf@servo.finestructure.net> References: <4CF15D67.1070904@fifthhorseman.net> <87aak08fu8.fsf@servo.finestructure.net> <87fwsf9mip.fsf@servo.finestructure.net> <87tygl29vu.fsf@servo.finestructure.net> <87oc5yi9us.fsf@zancas.localnet> <87d3mdvjwz.fsf@bookbinder.fernseed.info> <87k4gk70ng.fsf@SSpaeth.de> <87sjv8i7v6.fsf@irigaray.ross.mayfirst.org> <87sjv86mp9.fsf@servo.finestructure.net> <4D6BF0AA.3070706@fifthhorseman.net> <874o7o6ih5.fsf@servo.finestructure.net> <4D6C00C7.9000705@fifthhorseman.net> <8739n75zdb.fsf@servo.finestructure.net> <87hbbno7ia.fsf@raven.defaultvalue.org> <87pqqb4ium.fsf@servo.finestructure.net> <878vwuvupl.fsf@servo.finestructure.net> <87bp1o83ij.fsf@servo.finestructure.net> User-Agent: Notmuch/0.5 (http://notmuchmail.org) Emacs/23.3.1 (x86_64-unknown-linux-gnu) Date: Thu, 14 Apr 2011 09:48:37 +0200 Message-ID: <877hax8e96.fsf@eve.chaoflow.net> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" X-Virus-Scanned: clamav-milter 0.96.5 at tesla X-Virus-Status: Clean 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 Apr 2011 07:48:40 -0000 --=-=-= Content-Transfer-Encoding: quoted-printable I am also using the crypto branch and am very satisfied with it - thank you! There are some issues, but I will further debug before bothering you. On Sun, 06 Mar 2011 11:15:00 -0800, Jameson Rollins wrote: > On Sat, 05 Mar 2011 00:26:46 -0800, Jameson Rollins wrote: > > Hey, folks. I just pushed a couple of patches to my "crypto" branch [0] > > that add support for auto-tagging of multipart/signed and > > multipart/encrypted messages with the "signed" and "encrypted" tags > > respectively. Only new messages are thus tagged, so a database rebuild > > is required to auto-tag old messages. >=20 > So I realized last night, what now seems obvious, that restoring tags > after a notmuch new will override any initial auto tagging. This means > that doing a database rebuild will *not* crypto tag all your old mail if > you then restore tags from a tag dump afterwords. >=20 > I'm not sure if there's anything that can be done about this. I think > we either have to have a way to merge tags, or the signed and encrypted > indicators need to exist in a different field in the database. Tags > allow more flexibility in the UIs, but maybe we could just tag based on > a the new database field somehow? >=20 > It's not such a big deal that we only get "signed" and "encrypted" from > here forward, but it would be nice to re-tag old messages this way. I > can imagine that something like this will come up again in the future, > and it would be nice if we had a solution. I'm open to suggestions. Is there a solution for retagging or selective tag merging already? =2D-=20 Florian Friesdorf GPG FPR: 7A13 5EEE 1421 9FC2 108D BAAF 38F8 99A3 0C45 F083 Jabber/XMPP: flo@chaoflow.net IRC: chaoflow on freenode,ircnet,blafasel,OFTC --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (GNU/Linux) iQIcBAEBAgAGBQJNpqbVAAoJEDj4maMMRfCDU0IQALXxfVMWjW/yJ8DtYlrfpze+ tKRm3DDoshiHSdNFw1RJ2pyDtISwiS0R27/dIBmU9atJuURX48vgNnwXIwSTLKS2 f2mtyV7JDAF2P2SYlUAQHa5JrvmwDT/KJNaFFCNGONK9uEbyxPciEe57KHb1lGz6 p2D1bFWJuw+oTWCUoTX0KbKOCGioQvmkKVLCZcOW0DV6TWDtlRvLeAdMNm9Pli1a PKW0RgA6eboy2ZJRIfcNYRS/arzvV2jn/17U2ngpOg2IJbh+3drcViVO89Ssih2p HmPjW+KZ7v5Egg3sO1xNltmXeFeHMFnW2vUDw3RekhSZAn3bJu74jSMQZldkMs5v u248v6zeYkvA/WnTd2JB9dWoYqBU2PorBcBT+M+rG3Em7kodgMFJxQKJmAyoLtfb 360hsIy4UXjmLAXmHVgrEq19uIvXtdnsiJyja7IKVWzq77/SN0dkKr03hczv86GT U3Hzdlv0NqrLRDjkk5+MF5AVStHaXAteX669+IfvPQELu/4VPq9UMwK2/N7DjDfn Bor2WC6sTTptBLL4Bv2mFOfPddJXv7ykRYlvmbttAksPaWC44tC+psZ9HSIxmRLH sW43wWzbEIlUiliZ/QYGf0sRXStG/dpREc80V7++J3arUJFGAMmAgvfsiHZVQAYI znBOkVMTLfWeppPwG35H =VZvo -----END PGP SIGNATURE----- --=-=-=--