From: ShengHuo ZHU <zsh@cs.rochester.edu>
Subject: Re: wrong MIME composing
Date: 22 Nov 2000 08:48:49 -0500 [thread overview]
Message-ID: <2nzoisrubi.fsf@tiger.jia.vnet> (raw)
In-Reply-To: <m3em04guec.fsf@reason.gnu-hamburg>
"Georg C. F. Greve" <greve@gnu.org> writes:
> Although it seems that this cannot deal with multiple recipients,
> i.e. recipients="someone@else.com, another@recipient" won't work...
This parameter is passed to the PGP wrap package (gpg.el or
mailcrypt).
> I think that a manual way of specifying all recipients is crucial
> sometimes. And if we could have TAB-completion there, it'd beat
> anything there is right now afaik. .-)
Gnus can do nothing, unless the PGP wrap package provides the key
rings.
ShengHuo
next prev parent reply other threads:[~2000-11-22 13:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-21 15:19 Georg C. F. Greve
2000-11-21 15:32 ` ShengHuo ZHU
2000-11-21 23:28 ` Georg C. F. Greve
2000-11-22 1:07 ` ShengHuo ZHU
2000-11-22 10:42 ` Georg C. F. Greve
2000-11-22 13:48 ` ShengHuo ZHU [this message]
2000-11-22 14:39 ` Georg C. F. Greve
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=2nzoisrubi.fsf@tiger.jia.vnet \
--to=zsh@cs.rochester.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).