From: jam@jamux.com (John A. Martin)
Cc: ding@gnus.org
Subject: Re: How does one pgp/mime encrypt to different recipients?
Date: Mon, 02 Sep 2002 18:38:28 -0400 [thread overview]
Message-ID: <87it1o10gr.fsf@athene.jamux.com> (raw)
In-Reply-To: <iluk7m4gnps.fsf@latte.josefsson.org> (Simon Josefsson's message of "Mon, 02 Sep 2002 22:07:11 +0200")
[-- Attachment #1: Type: text/plain, Size: 1338 bytes --]
>>>>> "Simon" == Simon Josefsson
>>>>> "Re: How does one pgp/mime encrypt to different recipients?"
>>>>> Mon, 02 Sep 2002 22:07:11 +0200
Simon> jam@jamux.com (John A. Martin) writes:
>> How does one encrypt mail to key user-ids other than those
>> auto-detected from the To/CC headers?
Simon> The old per-part MML tags `recipients' and `sender' works:
Thank you for the quick response.
Being a newbe I don't know nut'n 'bout old stuff. It all looks the
same to me. :)
Simon> #multipart encrypt=pgpmime recipients=foo@bar.com
Using something like
example: #multipart encrypt=pgpmime recipients=comma,seperated,list[1]
worked OK for me except that when decrypting, also with ognus-5.07
(XEmacs-21.4p5), I saw no indication that their was a good signature
before encrypting. Using something like
example: #multipart sign=pgpmime encrypt=pgpmime recipients=l,i,s,t
also gave no hint what key if any had signed tha message.
How does one supply the --throw-keyid option?
Simon> but they doesn't seem to work in the new <#secure> tag.
Simon> I'm not sure why.
Will this get on someone's To Do list after appearing here?
Footnotes:
[1] What is a sure way of 'protecting' a line like this? I finally
removed the pointy brackets.
jam
[-- Attachment #2: Type: application/pgp-signature, Size: 154 bytes --]
next prev parent reply other threads:[~2002-09-02 22:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-02 18:33 John A. Martin
2002-09-02 20:07 ` Simon Josefsson
2002-09-02 22:38 ` John A. Martin [this message]
2002-09-03 9:45 ` Kai Großjohann
2002-09-03 14:52 ` Josh Huber
2002-09-04 13:56 ` David S Goldberg
2002-09-04 14:46 ` Josh Huber
2002-09-05 16:53 ` David S Goldberg
2002-09-05 17:05 ` Josh Huber
2002-09-06 15:22 ` David S Goldberg
2002-09-03 16:10 ` Simon Josefsson
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=87it1o10gr.fsf@athene.jamux.com \
--to=jam@jamux.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).