Re: (auto-)tagging sent messages

diff --git a/34/349dac98e0486f43453b2eec85165d809b5261 b/34/349dac98e0486f43453b2eec85165d809b5261
new file mode 100644 (file)
index 0000000..69ee453
--- /dev/null
+++ b/34/349dac98e0486f43453b2eec85165d809b5261
@@ -0,0 +1,100 @@
+Return-Path: <pieter@praet.org>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+       by olra.theworths.org (Postfix) with ESMTP id 4558D431FB6\r
+       for <notmuch@notmuchmail.org>; Sun, 17 Apr 2011 23:40:53 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: 0\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none]\r
+       autolearn=disabled\r
+Received: from olra.theworths.org ([127.0.0.1])\r
+       by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
+       with ESMTP id kGsA8eqtdCNp for <notmuch@notmuchmail.org>;\r
+       Sun, 17 Apr 2011 23:40:44 -0700 (PDT)\r
+Received: from mail-ww0-f45.google.com (mail-ww0-f45.google.com\r
+ [74.125.82.45])       (using TLSv1 with cipher RC4-SHA (128/128 bits))        (No client\r
+ certificate requested)        by olra.theworths.org (Postfix) with ESMTPS id\r
+ F3AB6431FB5   for <notmuch@notmuchmail.org>; Sun, 17 Apr 2011 23:40:43 -0700\r
+ (PDT)\r
+Received: by wwi36 with SMTP id 36so4685036wwi.2\r
+       for <notmuch@notmuchmail.org>; Sun, 17 Apr 2011 23:40:40 -0700 (PDT)\r
+Received: by 10.216.145.131 with SMTP id p3mr4282965wej.82.1303108839906;\r
+       Sun, 17 Apr 2011 23:40:39 -0700 (PDT)\r
+Received: from localhost (6.159-240-81.adsl-dyn.isp.belgacom.be\r
+ [81.240.159.6])       by mx.google.com with ESMTPS id\r
+ m2sm2401670wer.13.2011.04.17.23.40.37 (version=TLSv1/SSLv3 cipher=OTHER);\r
+       Sun, 17 Apr 2011 23:40:38 -0700 (PDT)\r
+From: Pieter Praet <pieter@praet.org>\r
+To: Tom Prince <tom.prince@ualberta.net>,\r
+ Florian Friesdorf <flo@chaoflow.net>, notmuch@notmuchmail.org\r
+Subject: Re: (auto-)tagging sent messages\r
+In-Reply-To: <87k4esjwmj.fsf@hermes.hocat.ca>\r
+References: <8739ll8dkv.fsf@eve.chaoflow.net>\r
+       <87pqomgxr0.fsf@A7GMS.i-did-not-set--mail-host-address--so-tickle-me>\r
+       <87sjtij8zj.fsf@hermes.hocat.ca>\r
+       <87bp04ix2n.fsf@A7GMS.i-did-not-set--mail-host-address--so-tickle-me>\r
+       <87k4esjwmj.fsf@hermes.hocat.ca>\r
+User-Agent: Notmuch/0.5-87-g30203d7 (http://notmuchmail.org) Emacs/23.1.50.1\r
+       (x86_64-pc-linux-gnu)\r
+Date: Mon, 18 Apr 2011 08:40:36 +0200\r
+Message-ID:\r
+ <87oc449i57.fsf@A7GMS.i-did-not-set--mail-host-address--so-tickle-me>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain; charset=us-ascii\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.13\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+       <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
+List-Archive: <http://notmuchmail.org/pipermail/notmuch>\r
+List-Post: <mailto:notmuch@notmuchmail.org>\r
+List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
+List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Mon, 18 Apr 2011 06:40:53 -0000\r
+\r
+On Sun, 17 Apr 2011 19:17:40 -0400, Tom Prince <tom.prince@ualberta.net> wrote:\r
+> On 2011-04-17, Pieter Praet wrote:\r
+> > On Sat, 16 Apr 2011 15:23:44 -0400, Tom Prince <tom.prince@ualberta.net> wrote:\r
+> > > > > Further, for certain mails I sent (like this one ) I would like a\r
+> > > > > WAITING tag (or similar) in order to indicate that I am waiting for an\r
+> > > > > answer. Currently I set this manually. Could this be achieved through\r
+> > > > > some indicators via message mode or similar means? e.g.:\r
+> > > > > \r
+> > > > > <#notmuch tag=WAITING> analog to <#secure method=pgpmime mode=sign>\r
+> > > > \r
+> > > > No idea how this works since I don't follow Jameson's crypto branch,\r
+> > > > but it's probably not a good idea for this use case since (I presume)\r
+> > > > the indicator will become permanently lodged in the content of the\r
+> > > > mail, which isn't where highly volatile metadata belongs.\r
+> > > \r
+> > > I think the idea isn't to save it in the message, but to postprocess the\r
+> > > message when sending, remove the marker and add the tag instead.\r
+> > > \r
+> > >   Tom\r
+> > \r
+> > Seems like a Catch-22 to me.\r
+> > \r
+> > The marker needs to remain there long enough for Notmuch to index and\r
+> > tag the message appropriately (which happens long after message-mode has\r
+> > left the building) so it's up to Notmuch itself (as opposed to a\r
+> > message-mode hook) to do the pre-/postprocessing.\r
+> \r
+> Not if message mode post-processing is hooked up to something like\r
+> notmuch-deliver, that indexes and tags the message on send.\r
+> \r
+>   Tom\r
+\r
+Hadn't looked into notmuch-deliver yet.\r
+\r
+Now that I did, I stand corrected, good sir!\r
+\r
+\r
+Peace\r
+\r
+-Pieter\r