From: Florian Weimer <fw@deneb.enyo.de>
Subject: Re: Crypto-MIME in GNUS
Date: 12 Apr 2001 13:27:34 +0200 [thread overview]
Message-ID: <874rvutl21.fsf@deneb.enyo.de> (raw)
In-Reply-To: <m3wv8qjtlf.fsf@reason.gnu-hamburg> ("Georg C. F. Greve"'s message of "12 Apr 2001 12:33:16 +0200")
"Georg C. F. Greve" <greve@gnu.org> writes:
> sj> FWIW, people I communicate with that uses Outlook and some PGP
> sj> plugin does not handle PGP/MIME (RFC2015). The plugin perform
> sj> PGP-operations on each MIME part individually and only insert the
> sj> PGP output instead of the MIME content of that part. I don't
> sj> think it even modifies MIME headers. Yuk.
>
> Yikes. This doesn't sound very standard-ish.
The plug-in interface of some MUAs doesn't provide access to message
and/or MIME part headers, so there's no way to implement OpenPGP/MIME
properly.
next prev parent reply other threads:[~2001-04-12 11:27 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 [this message]
2001-04-10 14:19 ` Josh Huber
2001-04-13 13:10 ` 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=874rvutl21.fsf@deneb.enyo.de \
--to=fw@deneb.enyo.de \
/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).