1 Return-Path: <jrollins@finestructure.net>
\r
2 X-Original-To: notmuch@notmuchmail.org
\r
3 Delivered-To: notmuch@notmuchmail.org
\r
4 Received: from localhost (localhost [127.0.0.1])
\r
5 by olra.theworths.org (Postfix) with ESMTP id E0FAC431FB6
\r
6 for <notmuch@notmuchmail.org>; Sun, 6 Mar 2011 11:15:07 -0800 (PST)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=0.01 tagged_above=-999 required=5
\r
12 tests=[T_MIME_NO_TEXT=0.01] autolearn=disabled
\r
13 Received: from olra.theworths.org ([127.0.0.1])
\r
14 by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)
\r
15 with ESMTP id kQBzc4KhRDRS for <notmuch@notmuchmail.org>;
\r
16 Sun, 6 Mar 2011 11:15:07 -0800 (PST)
\r
17 Received: from paneer.cc.columbia.edu (paneer.cc.columbia.edu [128.59.29.4])
\r
18 by olra.theworths.org (Postfix) with ESMTP id 214B7431FB5
\r
19 for <notmuch@notmuchmail.org>; Sun, 6 Mar 2011 11:15:07 -0800 (PST)
\r
20 Received: from servo.finestructure.net (cpe-76-89-195-238.socal.res.rr.com
\r
21 [76.89.195.238] (may be forged))
\r
22 (user=jgr2110 author=jrollins@servo.finestructure.net mech=PLAIN
\r
24 by paneer.cc.columbia.edu (8.14.4/8.14.3) with ESMTP id p26JF4GL019725
\r
25 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT)
\r
26 for <notmuch@notmuchmail.org>; Sun, 6 Mar 2011 14:15:06 -0500 (EST)
\r
27 Received: from jrollins by servo.finestructure.net with local (Exim 4.72)
\r
28 (envelope-from <jrollins@finestructure.net>) id 1PwJPz-0004rS-US
\r
29 for notmuch@notmuchmail.org; Sun, 06 Mar 2011 11:15:03 -0800
\r
30 From: Jameson Rollins <jrollins@finestructure.net>
\r
31 To: notmuch <notmuch@notmuchmail.org>
\r
32 Subject: Re: signed/encrypted tagging in crypto branch
\r
33 In-Reply-To: <878vwuvupl.fsf@servo.finestructure.net>
\r
34 References: <4CF15D67.1070904@fifthhorseman.net>
\r
35 <87aak08fu8.fsf@servo.finestructure.net>
\r
36 <87fwsf9mip.fsf@servo.finestructure.net>
\r
37 <87tygl29vu.fsf@servo.finestructure.net>
\r
38 <87oc5yi9us.fsf@zancas.localnet>
\r
39 <87d3mdvjwz.fsf@bookbinder.fernseed.info>
\r
40 <87k4gk70ng.fsf@SSpaeth.de>
\r
41 <87sjv8i7v6.fsf@irigaray.ross.mayfirst.org>
\r
42 <87sjv86mp9.fsf@servo.finestructure.net>
\r
43 <4D6BF0AA.3070706@fifthhorseman.net>
\r
44 <874o7o6ih5.fsf@servo.finestructure.net>
\r
45 <4D6C00C7.9000705@fifthhorseman.net>
\r
46 <8739n75zdb.fsf@servo.finestructure.net>
\r
47 <87hbbno7ia.fsf@raven.defaultvalue.org>
\r
48 <87pqqb4ium.fsf@servo.finestructure.net>
\r
49 <878vwuvupl.fsf@servo.finestructure.net>
\r
50 User-Agent: Notmuch/0.5-107-g536e288 (http://notmuchmail.org) Emacs/23.2.1
\r
52 Date: Sun, 06 Mar 2011 11:15:00 -0800
\r
53 Message-ID: <87bp1o83ij.fsf@servo.finestructure.net>
\r
55 Content-Type: multipart/signed; boundary="=-=-=";
\r
56 micalg=pgp-sha256; protocol="application/pgp-signature"
\r
57 X-No-Spam-Score: Local
\r
58 X-Scanned-By: MIMEDefang 2.68 on 128.59.29.4
\r
59 X-BeenThere: notmuch@notmuchmail.org
\r
60 X-Mailman-Version: 2.1.13
\r
62 List-Id: "Use and development of the notmuch mail system."
\r
63 <notmuch.notmuchmail.org>
\r
64 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
65 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
66 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
67 List-Post: <mailto:notmuch@notmuchmail.org>
\r
68 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
69 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
70 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
71 X-List-Received-Date: Sun, 06 Mar 2011 19:15:08 -0000
\r
75 On Sat, 05 Mar 2011 00:26:46 -0800, Jameson Rollins <jrollins@finestructure.net> wrote:
\r
76 > Hey, folks. I just pushed a couple of patches to my "crypto" branch [0]
\r
77 > that add support for auto-tagging of multipart/signed and
\r
78 > multipart/encrypted messages with the "signed" and "encrypted" tags
\r
79 > respectively. Only new messages are thus tagged, so a database rebuild
\r
80 > is required to auto-tag old messages.
\r
82 So I realized last night, what now seems obvious, that restoring tags
\r
83 after a notmuch new will override any initial auto tagging. This means
\r
84 that doing a database rebuild will *not* crypto tag all your old mail if
\r
85 you then restore tags from a tag dump afterwords.
\r
87 I'm not sure if there's anything that can be done about this. I think
\r
88 we either have to have a way to merge tags, or the signed and encrypted
\r
89 indicators need to exist in a different field in the database. Tags
\r
90 allow more flexibility in the UIs, but maybe we could just tag based on
\r
91 a the new database field somehow?
\r
93 It's not such a big deal that we only get "signed" and "encrypted" from
\r
94 here forward, but it would be nice to re-tag old messages this way. I
\r
95 can imagine that something like this will come up again in the future,
\r
96 and it would be nice if we had a solution. I'm open to suggestions.
\r
101 Content-Type: application/pgp-signature
\r
103 -----BEGIN PGP SIGNATURE-----
\r
104 Version: GnuPG v1.4.11 (GNU/Linux)
\r
106 iQIcBAEBCAAGBQJNc901AAoJEO00zqvie6q8brEP/RTmlk0DLcb0DKjSeeFbl+R1
\r
107 lQ/m9apE2Vg0UGxZMQqf/znrdK1uYIcPazbGOeh5y/dZ9MsMCyqtsGW2uXfzK1eS
\r
108 MW1O15OQXfNd3tGQhKdrNonLO+l4Deoo6jogbuuCE0f0hhs1UePG1cJEMahrippt
\r
109 o0cyYxwj6MQmY4jMQA7gkrhyh01jIH0mXjbb6FTWuTi32Ac1C8a87MZMvHHwTgpT
\r
110 7DuK25KkSfOxl5OxqWkIbvWx/zlVjmk0e4Te7KBVAI22KDVEykd4HA1cBRsyDSCE
\r
111 vcmOqcuo0OVKFNzvd2chlvkIjOBXQMVds6zq1sj86FWYbhqWH1YJJTLHsO9AoEeH
\r
112 lnd0eKSroMuHvb8qQuNydwsM0r8m1dpd/z2x3Ed1ksnA3foiuuk+zmC2X/bUg7CP
\r
113 YhlTwsb+x0bpO/UOWznrOYbgaNaO6cYGoBGrTzL9/VnC9SK19GUleKDwhOk3dDw0
\r
114 /0RAcGgzrJFVjgwo6utupCwldShQibuEZMh05sxObRE0k6Kpy3ds0tn6DQxZ2TGR
\r
115 BV2qu0NqT6F5TAil8Hd+eUGvCzDpB1qxpNyRzLwTO7rAxe8E9eWEo8j9Zf+rGyM1
\r
116 gyVjTuq9EOiEYHv75HP2TINRMaxwGmjCOPkSeEDUL3fjpFKQARgSK40vNZbx89QA
\r
117 iTmV+APqWh3Lk3LX4YiG
\r
119 -----END PGP SIGNATURE-----
\r