From: Eric Abrahamsen <email@example.com>
Subject: Re: Capturing outgoing gnus e-mail
Date: Sat, 14 Jun 2014 18:06:44 +0800 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
Ivan Kanis <email@example.com> writes:
> I would like to capture outgoing e-mail in my org file.
> I use the gcc mechanism in gnus with a nnml backend.
> I think I have read on the org mailing list that someone has implemented
> that feature. I did a search but could not find the article.
> I tried implementing it myself. I had a look at the function
> gnus-inews-do-gcc. It has the group and the article number. However org
> link expect the Message-ID header. How do I get it?
That's something that Gnorb can do. Make a capture template that
you want to use for outgoing mail TODOs, and identify it:
(setq gnorb-gnus-new-todo-capture-key "O")
Then, while you're composing the email, call
`gnorb-gnus-outgoing-do-todo' in the message buffer, which I have bound
to "C-c t".
You can also call it *after* sending the message, if you forgot, and it
will initiate the same process from the last sent message.
It works best when you're using Gcc, as that means Org is able to make a
real link to the sent message. Gnorb will try to fake it, if you're not.
If you set (setq gnorb-gnus-hint-relevant-article t), Gnorb will even
notify you when you get a reply to your sent message.
It's early days for Gnorb, but this part of it works well for me. I'd
love a little more road-testing, if you're interested!
I'm going to stick it in ELPA in a month or so, but for now:
Hope it helps!
next prev parent reply other threads:[~2014-06-14 10:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-14 8:32 Capturing outgoing gnus e-mail Ivan Kanis
2014-06-14 9:05 ` Bastien
2014-12-15 12:08 ` Uwe Brauer
2014-06-14 10:06 ` Eric Abrahamsen [this message]
2014-06-16 2:08 ` Esben Stien
2014-06-16 13:29 ` Eric Abrahamsen
2014-09-24 21:04 ` Ted Zlatanov
2014-12-14 22:58 ` Uwe Brauer
2014-06-14 14:43 Marvin Doyley
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).