From: Simon Josefsson <jas@slipsten.extundo.com>
Cc: ding@gnus.org
Subject: Re: pgp/mime encryption with specified public-key
Date: Fri, 18 Jan 2002 12:55:19 +0100 [thread overview]
Message-ID: <ilu7kqf6fh4.fsf@slipsten.extundo.com> (raw)
In-Reply-To: <87d708dvet.fsf@cs.utah.edu> (Karra's message of "Fri, 18 Jan 2002 11:59:14 +0530")
Karra <karra@cs.utah.edu> writes:
> By default, the public keys that are looked up are the based on the
> recipient email ids in the message. I want to specify another key
> instead (say because I am sending a message to a friend who uses the
> same gpg key pair on different acounts). If there is a legit way of
> doing this, pray explain it and ignore the rest of this mail.
You can specify a `recipients' tag in the MML tag:
To: bob@example.org
...
<#part sign=pgpmime recipients=alice@example.org>
It will be encrypted to alice but sent to bob.
There should be key and menu bindings for this, and documentation in
english instead of elisp. Maybe tonight.
prev parent reply other threads:[~2002-01-18 11:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-18 6:29 Karra
2002-01-18 11:55 ` Simon Josefsson [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=ilu7kqf6fh4.fsf@slipsten.extundo.com \
--to=jas@slipsten.extundo.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).