Gnus development mailing list
 help / color / mirror / Atom feed
From: Fabien Penso <penso@linuxfr.org>
Cc: Nevin Kapur <nevin@jhu.edu>, ding@gnus.org
Subject: GPG and Mailcrypt (was: GPG Failure from Evolution)
Date: Thu, 27 Sep 2001 17:48:59 +0200	[thread overview]
Message-ID: <plop87bsjwfxck.fsf@linuxfr.org> (raw)
In-Reply-To: <conectiva-linux.m3ofnxfsrw.fsf@godoy.laptop> (Jorge Godoy's message of "Wed, 26 Sep 2001 20:15:31 -0300")

[-- Attachment #1: Type: text/plain, Size: 994 bytes --]


Jorge on Wed, 26 Sep 2001 20:15:31 -0300 wrote:


 > My GPG settings are:

 > ,----
 > | ;; GnuPG Settings
(...)

As I see, you are using mailcrypt and gpg.el.

Let's say you want to encrypt or sign 'in-body' you will then use
mc-sign instead of mml-secure-sign-pgpmime. It might be usefull as
sometimes you talk with people which don't understand MIME signature
(Outlook, etc) but only the ones put directly in the body.

But then you do have to enter your passphrase twice as the var name
isn't the same for mailcrypt and gpg. I guess maybe gpg.el should use
the same name to prevent that.

Also it would be nice to have a feature which allow to automaticly sign
any signed message, and same for crypt. The only thing needed is to set
up a var to true when gpg verify the signature, if true then we sign in
mail-send-hook. (I don't no sh*t about lisp, but I guess it should
work this way). Is this feature in the TODO list of Gnus ? :-)

-- 
Sorry, bad English.

[-- Attachment #2: Type: application/pgp-signature, Size: 239 bytes --]

      parent reply	other threads:[~2001-09-27 15:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-26 21:36 GPG Failure from Evolution Nevin Kapur
2001-09-26 22:12 ` Neal H Walfield
2001-09-27  1:23   ` Jorge Godoy
2001-09-27  8:38   ` Simon Josefsson
2001-09-26 23:15 ` Jorge Godoy
2001-09-26 23:41   ` Nevin Kapur
2001-09-27 15:48   ` Fabien Penso [this message]

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=plop87bsjwfxck.fsf@linuxfr.org \
    --to=penso@linuxfr.org \
    --cc=ding@gnus.org \
    --cc=nevin@jhu.edu \
    /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).