From: Jameson Rollins <jrollins@finestructure.net>
To: notmuch <notmuch@notmuchmail.org>
Subject: Re: signed/encrypted tagging in crypto branch
In-Reply-To: <878vwuvupl.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>
User-Agent: Notmuch/0.5-107-g536e288 (http://notmuchmail.org) Emacs/23.2.1
	(i486-pc-linux-gnu)
Date: Sun, 06 Mar 2011 11:15:00 -0800
Message-ID: <87bp1o83ij.fsf@servo.finestructure.net>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-=";
	micalg=pgp-sha256; protocol="application/pgp-signature"
Precedence: list

--=-=-=

On Sat, 05 Mar 2011 00:26:46 -0800, Jameson Rollins <jrollins@finestructure.net> 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.

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.

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?

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.

jamie.

--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQIcBAEBCAAGBQJNc901AAoJEO00zqvie6q8brEP/RTmlk0DLcb0DKjSeeFbl+R1
lQ/m9apE2Vg0UGxZMQqf/znrdK1uYIcPazbGOeh5y/dZ9MsMCyqtsGW2uXfzK1eS
MW1O15OQXfNd3tGQhKdrNonLO+l4Deoo6jogbuuCE0f0hhs1UePG1cJEMahrippt
o0cyYxwj6MQmY4jMQA7gkrhyh01jIH0mXjbb6FTWuTi32Ac1C8a87MZMvHHwTgpT
7DuK25KkSfOxl5OxqWkIbvWx/zlVjmk0e4Te7KBVAI22KDVEykd4HA1cBRsyDSCE
vcmOqcuo0OVKFNzvd2chlvkIjOBXQMVds6zq1sj86FWYbhqWH1YJJTLHsO9AoEeH
lnd0eKSroMuHvb8qQuNydwsM0r8m1dpd/z2x3Ed1ksnA3foiuuk+zmC2X/bUg7CP
YhlTwsb+x0bpO/UOWznrOYbgaNaO6cYGoBGrTzL9/VnC9SK19GUleKDwhOk3dDw0
/0RAcGgzrJFVjgwo6utupCwldShQibuEZMh05sxObRE0k6Kpy3ds0tn6DQxZ2TGR
BV2qu0NqT6F5TAil8Hd+eUGvCzDpB1qxpNyRzLwTO7rAxe8E9eWEo8j9Zf+rGyM1
gyVjTuq9EOiEYHv75HP2TINRMaxwGmjCOPkSeEDUL3fjpFKQARgSK40vNZbx89QA
iTmV+APqWh3Lk3LX4YiG
=hDgF
-----END PGP SIGNATURE-----
--=-=-=--