--- /dev/null
+Return-Path: <gmn-notmuch@m.gmane.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 1268A431FC9\r
+ for <notmuch@notmuchmail.org>; Fri, 24 Oct 2014 09:57:36 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -0.7\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-0.7 tagged_above=-999 required=5\r
+ tests=[RCVD_IN_DNSWL_LOW=-0.7] 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 DySEMYR1VxBb for <notmuch@notmuchmail.org>;\r
+ Fri, 24 Oct 2014 09:57:28 -0700 (PDT)\r
+Received: from plane.gmane.org (plane.gmane.org [80.91.229.3])\r
+ (using TLSv1 with cipher AES256-SHA (256/256 bits))\r
+ (No client certificate requested)\r
+ by olra.theworths.org (Postfix) with ESMTPS id 21697431FBD\r
+ for <notmuch@notmuchmail.org>; Fri, 24 Oct 2014 09:57:28 -0700 (PDT)\r
+Received: from list by plane.gmane.org with local (Exim 4.69)\r
+ (envelope-from <gmn-notmuch@m.gmane.org>) id 1XhiB0-0004wn-QL\r
+ for notmuch@notmuchmail.org; Fri, 24 Oct 2014 18:57:22 +0200\r
+Received: from c-76-28-195-250.hsd1.wa.comcast.net ([76.28.195.250])\r
+ by main.gmane.org with esmtp (Gmexim 0.1 (Debian))\r
+ id 1AlnuQ-0007hv-00\r
+ for <notmuch@notmuchmail.org>; Fri, 24 Oct 2014 18:57:22 +0200\r
+Received: from eric by c-76-28-195-250.hsd1.wa.comcast.net with local (Gmexim\r
+ 0.1 (Debian)) id 1AlnuQ-0007hv-00\r
+ for <notmuch@notmuchmail.org>; Fri, 24 Oct 2014 18:57:22 +0200\r
+X-Injected-Via-Gmane: http://gmane.org/\r
+To: notmuch@notmuchmail.org\r
+From: Eric Abrahamsen <eric@ericabrahamsen.net>\r
+Subject: Re: [O] how to put into a journal info about the email sent\r
+Followup-To: gmane.emacs.orgmode\r
+Date: Fri, 24 Oct 2014 10:02:10 -0700\r
+Lines: 41\r
+Message-ID: <87a94lh04t.fsf@ericabrahamsen.net>\r
+References: <uaxh9yty1pm.fsf@beesknees.cern.ch>\r
+ <87ppdhh3rh.fsf@ericabrahamsen.net>\r
+ <m2k33p31yb.fsf@heart-of-gold.hh.sledj.net>\r
+Mime-Version: 1.0\r
+Content-Type: text/plain\r
+X-Complaints-To: usenet@ger.gmane.org\r
+X-Gmane-NNTP-Posting-Host: c-76-28-195-250.hsd1.wa.comcast.net\r
+User-Agent: Gnus/5.130012 (Ma Gnus v0.12) Emacs/25.0.50 (gnu/linux)\r
+Cancel-Lock: sha1:IPoQ6Jh7S/3SC/8FCtzXMQSKkh8=\r
+Cc: emacs-orgmode@gnu.org\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: Fri, 24 Oct 2014 16:57:36 -0000\r
+\r
+David Edmondson <dme@dme.org> writes:\r
+\r
+> On Fri, Oct 24 2014, Eric Abrahamsen wrote:\r
+>> David Belohrad <david@belohrad.ch> writes:\r
+>>\r
+>>> Dear All,\r
+>>>\r
+>>> i'm using org. And I'm using notmuch (that's why I address both mailing\r
+>>> lists). Now, writing an email in everyday bussiness requires a\r
+>>> non-significant time of your workhours. So I'd like to have this event\r
+>>> in my org agenda. So any time I send some email with a given subject,\r
+>>> I'd like to 'automatically' entry the information about it into\r
+>>> e.g. sentmails.org in form of a diary entry, with appropriate tag.\r
+>>\r
+>> I do something like this in Gnorb, which I'd recommend you use except\r
+>> it's mostly Gnus specific.\r
+>>\r
+>> I do it in two parts, but you could do it in one. Basically I add a\r
+>> function to the `message-header-hook' (which ensures that all the\r
+>> message headers have been generated properly).\r
+>\r
+> Does `message-generate-headers-first' not do what you want for this\r
+> specific part?\r
+\r
+Yeah, I think I looked at that previously. But this thing is going in a\r
+hook anyway, might as well use the hook that *doesn't* require me to\r
+call that function explicitly.\r
+\r
+>> Obviously the downside is that, without a "Gcc:" header, org can't\r
+>> actually make a real link to the message. It doesn't know where it's\r
+>> going to be. However if you know that all your sent messages can be\r
+>> reached with a link that looks like "notmuch:id#Message-id", then you\r
+>> can make that yourself in your org capture template with something like\r
+>\r
+> As you suggest, know the message-id should be good enough to generate a\r
+> notmuch link, though you may have to wait for the notmuch index to be\r
+> updated for the link to be valid.\r
+\r
+Yup, I've got the same issue with nnimap -- you have to wait for the\r
+next sync to get access to the message. So far it hasn't been a problem,\r
+though.\r
+\r