Return-Path: X-Original-To: notmuch@notmuchmail.org Delivered-To: notmuch@notmuchmail.org Received: from localhost (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id 3B130431FB6 for ; Mon, 18 Apr 2011 00:16:53 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: 0.01 X-Spam-Level: X-Spam-Status: No, score=0.01 tagged_above=-999 required=5 tests=[T_MIME_NO_TEXT=0.01] autolearn=disabled Received: from olra.theworths.org ([127.0.0.1]) by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9kx3zJ7al2ZC for ; Mon, 18 Apr 2011 00:16:51 -0700 (PDT) Received: from brinza.cc.columbia.edu (brinza.cc.columbia.edu [128.59.29.8]) by olra.theworths.org (Postfix) with ESMTP id 60AE4431FB5 for ; Mon, 18 Apr 2011 00:16:50 -0700 (PDT) Received: from servo.factory.finestructure.net (cpe-98-149-172-122.socal.res.rr.com [98.149.172.122]) (user=jgr2110 author=jrollins@servo.factory.finestructure.net mech=PLAIN bits=0) by brinza.cc.columbia.edu (8.14.4/8.14.3) with ESMTP id p3I7GlBB003462 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT) for ; Mon, 18 Apr 2011 03:16:49 -0400 (EDT) Received: from jrollins by servo.factory.finestructure.net with local (Exim 4.75) (envelope-from ) id 1QBihT-0008GH-IU for notmuch@notmuchmail.org; Mon, 18 Apr 2011 00:16:47 -0700 Resent-To: notmuch@notmuchmail.org Resent-From: Jameson Graef Rollins Resent-Date: Mon, 18 Apr 2011 00:16:47 -0700 Resent-Message-ID: <87aafoowps.fsf@servo.factory.finestructure.net> From: Jameson Graef Rollins To: Pieter Praet , Florian Friesdorf , notmuch@notmuchmail.org Subject: Re: (auto-)tagging sent messages In-Reply-To: <87pqomgxr0.fsf@A7GMS.i-did-not-set--mail-host-address--so-tickle-me> References: <8739ll8dkv.fsf@eve.chaoflow.net> <87pqomgxr0.fsf@A7GMS.i-did-not-set--mail-host-address--so-tickle-me> User-Agent: Notmuch/0.5-150-g3d45e49 (http://notmuchmail.org) Emacs/23.2.1 (i486-pc-linux-gnu) Date: Sun, 17 Apr 2011 11:23:33 -0700 Message-ID: <878vv8hh3u.fsf@servo.factory.finestructure.net> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" X-No-Spam-Score: Local X-Scanned-By: MIMEDefang 2.68 on 128.59.29.8 X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Apr 2011 07:16:53 -0000 --=-=-= Content-Transfer-Encoding: quoted-printable On Sat, 16 Apr 2011 14:57:07 +0200, Pieter Praet wrote: > > Further, for certain mails I sent (like this one ) I would like a > > WAITING tag (or similar) in order to indicate that I am waiting for an > > answer. Currently I set this manually. Could this be achieved through > > some indicators via message mode or similar means? e.g.: > >=20 > > <#notmuch tag=3DWAITING> analog to <#secure method=3Dpgpmime mode=3Dsig= n> >=20 > No idea how this works since I don't follow Jameson's crypto branch, > but it's probably not a good idea for this use case since (I presume) > the indicator will become permanently lodged in the content of the > mail, which isn't where highly volatile metadata belongs. Hey, Pieter. This doesn't actually have anything to do with the crypto branch. These indicators are how emacs handles signing/encryption of outgoing messages in emacs message-mode, as well as other things like adding attachments. It's not actually a part of notmuch. When using emacs message-mode to compose a message, you can add tags like these to the message body. When you then tell emacs to send the message, emacs reads these tags and performs the specified operation, like signing the message or adding an attachment. Emacs then removes the tags so they're never actually stored in the message. These tags are also not interpreted when reading a message, only when composing. I don't think it's a bad idea to extend this system to benefit notmuch, by instructing emacs message mode to add tags to outgoing messages. Like someone suggested, though, it should really be done by having notmuch index the outgoing message at the time of sending, which would best be handled by telling notmuch to index an individual message. Having notmuch index a single message would I think be incredibly useful, for a lot of different reasons. I think it would enable a lot of nice integration with other mail handling tools. I can imagine this being done in a couple of ways: By giving "notmuch new" a path to a message in the store: notmuch new /path/to/message By feeding "notmuch new" a message on stdin, and then having it write the message to a specified location: notmuch new /path/to/maildir