Aw: Re: OpenPGP SMTP headers
JPClizbe at comcast.net
Fri Jul 2 17:04:57 CEST 2004
Holger Sesterhenn wrote:
> There are two things to mention:
> First, David uses PGP/MIME (RFC 3156) instead of the old (but most
> widespread) PGP/INLINE signatures (CLASSIC). All known OpenPGP plugins
> for OE just support the latter. Even the original PGP 8.x.
The lack of RFC 3156 support in some OpenPGP plugins is often used as the
reason to continue with inline signatures. Aside from PGP's work with
their plugin, I don't think there is any work being done to
maintain/evolve the OpenPGP OE & Outlook plugins.
> Second, the mailing list software creates an envelope around the
> PGP/MIME message so it looks like "multipart/mixed" instead of
> "multipart/signed". There are some OpenPGP clients (like Enigmail) which
> try to detect this but its just experimental.
I'm not sure how 'experimental' Enigmail's support still is at this point.
It works without issue for myself and many others and has been in the code
since 0.83.0 which was released mid-January.
> I wouldn't call it a bug in the mailing list software ;-)
Nor would I
John P. Clizbe Inet: JPClizbe(a)comcast DOT nyet
Golden Bear Networks PGP/GPG KeyID: 0x608D2A10
"Most men take the straight and narrow. A few take the road less
traveled. I chose to cut through the woods."
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 312 bytes
Desc: OpenPGP digital signature
Url : /pipermail/attachments/20040702/064d134c/signature.bin
More information about the Gnupg-devel