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 4558D431FB6
\r
6 for <notmuch@notmuchmail.org>; Sun, 17 Apr 2011 23:40:53 -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 kGsA8eqtdCNp for <notmuch@notmuchmail.org>;
\r
16 Sun, 17 Apr 2011 23:40:44 -0700 (PDT)
\r
17 Received: from mail-ww0-f45.google.com (mail-ww0-f45.google.com
\r
18 [74.125.82.45]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client
\r
19 certificate requested) by olra.theworths.org (Postfix) with ESMTPS id
\r
20 F3AB6431FB5 for <notmuch@notmuchmail.org>; Sun, 17 Apr 2011 23:40:43 -0700
\r
22 Received: by wwi36 with SMTP id 36so4685036wwi.2
\r
23 for <notmuch@notmuchmail.org>; Sun, 17 Apr 2011 23:40:40 -0700 (PDT)
\r
24 Received: by 10.216.145.131 with SMTP id p3mr4282965wej.82.1303108839906;
\r
25 Sun, 17 Apr 2011 23:40:39 -0700 (PDT)
\r
26 Received: from localhost (6.159-240-81.adsl-dyn.isp.belgacom.be
\r
27 [81.240.159.6]) by mx.google.com with ESMTPS id
\r
28 m2sm2401670wer.13.2011.04.17.23.40.37 (version=TLSv1/SSLv3 cipher=OTHER);
\r
29 Sun, 17 Apr 2011 23:40:38 -0700 (PDT)
\r
30 From: Pieter Praet <pieter@praet.org>
\r
31 To: Tom Prince <tom.prince@ualberta.net>,
\r
32 Florian Friesdorf <flo@chaoflow.net>, notmuch@notmuchmail.org
\r
33 Subject: Re: (auto-)tagging sent messages
\r
34 In-Reply-To: <87k4esjwmj.fsf@hermes.hocat.ca>
\r
35 References: <8739ll8dkv.fsf@eve.chaoflow.net>
\r
36 <87pqomgxr0.fsf@A7GMS.i-did-not-set--mail-host-address--so-tickle-me>
\r
37 <87sjtij8zj.fsf@hermes.hocat.ca>
\r
38 <87bp04ix2n.fsf@A7GMS.i-did-not-set--mail-host-address--so-tickle-me>
\r
39 <87k4esjwmj.fsf@hermes.hocat.ca>
\r
40 User-Agent: Notmuch/0.5-87-g30203d7 (http://notmuchmail.org) Emacs/23.1.50.1
\r
41 (x86_64-pc-linux-gnu)
\r
42 Date: Mon, 18 Apr 2011 08:40:36 +0200
\r
44 <87oc449i57.fsf@A7GMS.i-did-not-set--mail-host-address--so-tickle-me>
\r
46 Content-Type: text/plain; charset=us-ascii
\r
47 X-BeenThere: notmuch@notmuchmail.org
\r
48 X-Mailman-Version: 2.1.13
\r
50 List-Id: "Use and development of the notmuch mail system."
\r
51 <notmuch.notmuchmail.org>
\r
52 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
53 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
54 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
55 List-Post: <mailto:notmuch@notmuchmail.org>
\r
56 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
57 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
58 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
59 X-List-Received-Date: Mon, 18 Apr 2011 06:40:53 -0000
\r
61 On Sun, 17 Apr 2011 19:17:40 -0400, Tom Prince <tom.prince@ualberta.net> wrote:
\r
62 > On 2011-04-17, Pieter Praet wrote:
\r
63 > > On Sat, 16 Apr 2011 15:23:44 -0400, Tom Prince <tom.prince@ualberta.net> wrote:
\r
64 > > > > > Further, for certain mails I sent (like this one ) I would like a
\r
65 > > > > > WAITING tag (or similar) in order to indicate that I am waiting for an
\r
66 > > > > > answer. Currently I set this manually. Could this be achieved through
\r
67 > > > > > some indicators via message mode or similar means? e.g.:
\r
69 > > > > > <#notmuch tag=WAITING> analog to <#secure method=pgpmime mode=sign>
\r
71 > > > > No idea how this works since I don't follow Jameson's crypto branch,
\r
72 > > > > but it's probably not a good idea for this use case since (I presume)
\r
73 > > > > the indicator will become permanently lodged in the content of the
\r
74 > > > > mail, which isn't where highly volatile metadata belongs.
\r
76 > > > I think the idea isn't to save it in the message, but to postprocess the
\r
77 > > > message when sending, remove the marker and add the tag instead.
\r
81 > > Seems like a Catch-22 to me.
\r
83 > > The marker needs to remain there long enough for Notmuch to index and
\r
84 > > tag the message appropriately (which happens long after message-mode has
\r
85 > > left the building) so it's up to Notmuch itself (as opposed to a
\r
86 > > message-mode hook) to do the pre-/postprocessing.
\r
88 > Not if message mode post-processing is hooked up to something like
\r
89 > notmuch-deliver, that indexes and tags the message on send.
\r
93 Hadn't looked into notmuch-deliver yet.
\r
95 Now that I did, I stand corrected, good sir!
\r