From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: Capturing outgoing gnus e-mail
Date: Thu, 25 Sep 2014 08:30:20 -0400 [thread overview]
Message-ID: <m2vboblw6b.fsf@lifelogs.com> (raw)
In-Reply-To: <upzcmw9ow3c4.fsf@dod.no>
On Thu, 25 Sep 2014 09:45:31 +0200 Steinar Bang <sb@dod.no> wrote:
SB> Um... what does this do? Write a log of sent messages to the diary?
Yes.
SB> I thought the diary was for future appointments, and appointment
SB> notifications?
I choose to use the diary for sent mail and think that's appropriate,
but really I posted that code to help the OP with capturing sent e-mails
to an Org mode file.
Ted
next prev parent reply other threads:[~2014-09-25 12:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-14 8:32 Ivan Kanis
2014-06-14 9:05 ` Bastien
2014-12-15 12:08 ` Uwe Brauer
2014-06-14 10:06 ` Eric Abrahamsen
2014-09-24 21:04 ` Ted Zlatanov
2014-09-25 7:45 ` Steinar Bang
2014-09-25 12:30 ` Ted Zlatanov [this message]
2014-12-14 22:58 ` Uwe Brauer
Reply instructions:
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2vboblw6b.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=ding@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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.
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 NNTP newsgroup(s).