From: "Georg C. F. Greve" <greve@gnu.org>
Subject: Re: Crypto-MIME in GNUS
Date: 13 Apr 2001 15:10:48 +0200 [thread overview]
Message-ID: <m3pueh54iv.fsf@reason.gnu-hamburg> (raw)
In-Reply-To: <ilu3dbhm3jz.fsf@barbar.josefsson.org> (Simon Josefsson's message of "10 Apr 2001 12:50:40 +0200")
[-- Attachment #1.1: Type: text/plain, Size: 1164 bytes --]
Hi Simon,
|| On 10 Apr 2001 12:50:40 +0200
|| Simon Josefsson <simon@josefsson.org> wrote:
>> The biggest problem was that the gnus crypto function didn't work
>> since it gave mailcrypt the buffer to encrypt that didn't contain
>> headers so mailcrypt had no way to determine who to encrypt it
>> for.
sj> Weird, this is definitely not the case for me. Could you tell
sj> why `message-options-set-recipient' function fail to figure out
sj> recipients? Or if there's some problem in mml2015 when mailcrypt
sj> is given the information snarfed from the *mail* buffer?
Okay, I left away my cludge and you're right, it works now.
The only thing I prefer about my cludge is that it shows you the
recipients and allows you to edit them. This is pretty nice as
sometimes people will have mail-addresses in their headers that don't
match the addresses in their GPG keys.
Regards,
Georg
--
Georg C. F. Greve <greve@gnu.org>
Free Software Foundation Europe (http://fsfeurope.org)
Brave GNU World (http://brave-gnu-world.org)
[-- Attachment #2: Type: application/pgp-signature, Size: 268 bytes --]
prev parent reply other threads:[~2001-04-13 13:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-10 8:52 Georg C. F. Greve
2001-04-10 10:50 ` Simon Josefsson
2001-04-10 13:27 ` Georg C. F. Greve
2001-04-10 13:23 ` Simon Josefsson
2001-04-12 10:33 ` Georg C. F. Greve
2001-04-12 11:27 ` Florian Weimer
2001-04-10 14:19 ` Josh Huber
2001-04-13 13:10 ` Georg C. F. Greve [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=m3pueh54iv.fsf@reason.gnu-hamburg \
--to=greve@gnu.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).