Gnus development mailing list
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: ding@gnus.org
Subject: Encryption vs. Gcc
Date: Wed, 04 Sep 2013 15:13:56 +0200	[thread overview]
Message-ID: <87fvtku3u3.fsf@gnu.org> (raw)

To keep a clear-text copy of encrypted messages that I send, I tried
this, as evasively suggested by the manual:

--8<---------------cut here---------------start------------->8---
;; Keep a clear-text copy of sent messages.
(setq gnus-gcc-post-body-encode-hook
      'mml-unsecure-message)
--8<---------------cut here---------------end--------------->8---

However, that doesn’t work, apparently because when the hook is called
the buffer that is current is not the message (see ‘gnus-inews-do-gcc’.)

Anyway, a more ideal solution for Gcc: would be this: if the message is
encrypted, then keep a copy encrypted with the sender’s public key
(rather than clear-text); otherwise keep a copy as is.

Does anyone have something like this?

TIA,  :-)
Ludo’.




             reply	other threads:[~2013-09-04 13:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-04 13:13 Ludovic Courtès [this message]
2013-09-04 18:41 ` Philipp Haselwarter
2013-09-06 13:02   ` Ludovic Courtès
2013-09-04 20:07 ` Adam Sjøgren
2013-09-06 13:10 ` Christopher Schmidt

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=87fvtku3u3.fsf@gnu.org \
    --to=ludo@gnu.org \
    --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).