1 Return-Path: <pieter@praet.org>
\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 4D62E431FB6
\r
6 for <notmuch@notmuchmail.org>; Sat, 16 Apr 2011 08:27:16 -0700 (PDT)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none]
\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 9PkHdmb5GC5Y for <notmuch@notmuchmail.org>;
\r
16 Sat, 16 Apr 2011 08:27:12 -0700 (PDT)
\r
17 Received: from mail-wy0-f181.google.com (mail-wy0-f181.google.com
\r
18 [74.125.82.181]) (using TLSv1 with cipher RC4-SHA (128/128 bits))
\r
19 (No client certificate requested)
\r
20 by olra.theworths.org (Postfix) with ESMTPS id 0C60C431FB5
\r
21 for <notmuch@notmuchmail.org>; Sat, 16 Apr 2011 08:27:11 -0700 (PDT)
\r
22 Received: by wyi11 with SMTP id 11so4049005wyi.26
\r
23 for <notmuch@notmuchmail.org>; Sat, 16 Apr 2011 08:27:09 -0700 (PDT)
\r
24 Received: by 10.216.24.92 with SMTP id w70mr731423wew.43.1302967626912;
\r
25 Sat, 16 Apr 2011 08:27:06 -0700 (PDT)
\r
26 Received: from localhost (99.28-240-81.adsl-dyn.isp.belgacom.be
\r
27 [81.240.28.99]) by mx.google.com with ESMTPS id
\r
28 s40sm1778241weq.28.2011.04.16.08.27.03 (version=TLSv1/SSLv3 cipher=OTHER);
\r
29 Sat, 16 Apr 2011 08:27:05 -0700 (PDT)
\r
30 From: Pieter Praet <pieter@praet.org>
\r
31 To: Jameson Rollins <jrollins@finestructure.net>,
\r
32 notmuch <notmuch@notmuchmail.org>
\r
33 Subject: Re: signed/encrypted tagging in crypto branch
\r
34 In-Reply-To: <87bp1o83ij.fsf@servo.finestructure.net>
\r
35 References: <4CF15D67.1070904@fifthhorseman.net>
\r
36 <87aak08fu8.fsf@servo.finestructure.net>
\r
37 <87fwsf9mip.fsf@servo.finestructure.net>
\r
38 <87tygl29vu.fsf@servo.finestructure.net>
\r
39 <87oc5yi9us.fsf@zancas.localnet>
\r
40 <87d3mdvjwz.fsf@bookbinder.fernseed.info>
\r
41 <87k4gk70ng.fsf@SSpaeth.de>
\r
42 <87sjv8i7v6.fsf@irigaray.ross.mayfirst.org>
\r
43 <87sjv86mp9.fsf@servo.finestructure.net>
\r
44 <4D6BF0AA.3070706@fifthhorseman.net>
\r
45 <874o7o6ih5.fsf@servo.finestructure.net>
\r
46 <4D6C00C7.9000705@fifthhorseman.net>
\r
47 <8739n75zdb.fsf@servo.finestructure.net>
\r
48 <87hbbno7ia.fsf@raven.defaultvalue.org>
\r
49 <87pqqb4ium.fsf@servo.finestructure.net>
\r
50 <878vwuvupl.fsf@servo.finestructure.net>
\r
51 <87bp1o83ij.fsf@servo.finestructure.net>
\r
52 User-Agent: Notmuch/0.5-86-g4875299 (http://notmuchmail.org) Emacs/23.1.50.1
\r
53 (x86_64-pc-linux-gnu)
\r
54 Date: Sat, 16 Apr 2011 17:27:02 +0200
\r
56 <877haub4jd.fsf@A7GMS.i-did-not-set--mail-host-address--so-tickle-me>
\r
58 Content-Type: text/plain; charset=us-ascii
\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: Sat, 16 Apr 2011 15:27:16 -0000
\r
73 On Sun, 06 Mar 2011 11:15:00 -0800, Jameson Rollins <jrollins@finestructure.net> wrote:
\r
74 > On Sat, 05 Mar 2011 00:26:46 -0800, Jameson Rollins <jrollins@finestructure.net> wrote:
\r
75 > > Hey, folks. I just pushed a couple of patches to my "crypto" branch [0]
\r
76 > > that add support for auto-tagging of multipart/signed and
\r
77 > > multipart/encrypted messages with the "signed" and "encrypted" tags
\r
78 > > respectively. Only new messages are thus tagged, so a database rebuild
\r
79 > > is required to auto-tag old messages.
\r
81 > So I realized last night, what now seems obvious, that restoring tags
\r
82 > after a notmuch new will override any initial auto tagging. This means
\r
83 > that doing a database rebuild will *not* crypto tag all your old mail if
\r
84 > you then restore tags from a tag dump afterwords.
\r
86 > I'm not sure if there's anything that can be done about this. I think
\r
87 > we either have to have a way to merge tags, or the signed and encrypted
\r
88 > indicators need to exist in a different field in the database. Tags
\r
89 > allow more flexibility in the UIs, but maybe we could just tag based on
\r
90 > a the new database field somehow?
\r
92 > It's not such a big deal that we only get "signed" and "encrypted" from
\r
93 > here forward, but it would be nice to re-tag old messages this way. I
\r
94 > can imagine that something like this will come up again in the future,
\r
95 > and it would be nice if we had a solution. I'm open to suggestions.
\r
98 Non-text part: application/pgp-signature
\r
99 > _______________________________________________
\r
100 > notmuch mailing list
\r
101 > notmuch@notmuchmail.org
\r
102 > http://notmuchmail.org/mailman/listinfo/notmuch
\r
105 As long as we're talking solely about "signed" and "encrypted" (so no
\r
106 verification-wise information whatsoever), I'd definitely vote for a
\r
107 dedicated database field.
\r
109 It's absolutely immutable metadata, embedded in the message content.
\r
111 No point in using tags for that, though it's not mutually exclusive:
\r
112 "notmuch tag +signed -- is:signed" (or whatever, knock yourself out)
\r
114 If folders -which DO change, although rarely- got one, so should crypto.
\r
117 ...but that's just my (insufficiently) humble opinion.
\r
projects / notmuch-archives.git / blob