From: Florian Weimer <fw@deneb.enyo.de>
Subject: Re: Multipart PGP sign/encrypt (was: Posting styles and PGP integration?)
Date: 18 Apr 2001 18:25:59 +0200 [thread overview]
Message-ID: <87ae5ekwdk.fsf@deneb.enyo.de> (raw)
In-Reply-To: <87r8yqqrz0.fsf_-_@mclinux.com> (Josh Huber's message of "18 Apr 2001 09:04:35 -0400")
Josh Huber <huber@nospam.alum.wpi.edu> writes:
> So, is there a way to get Gnus to do what I want it to do?
We could resurrect direct multipart/signed support, which reflects the
structure of the generated message more closely:
<$multipart type=signed method=pgp>
...
<$/multipart>
I still consider this the correct approach. (The necessary hooks are
already there.)
next prev parent reply other threads:[~2001-04-18 16:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-17 18:18 Posting styles and PGP integration? Andreas Fuchs
2001-04-18 3:13 ` Daniel Pittman
2001-04-18 4:23 ` Andreas Fuchs
2001-04-18 4:29 ` Andreas Fuchs
2001-04-19 1:23 ` Daniel Pittman
2001-04-19 8:34 ` lantz moore
2001-04-19 19:05 ` Andreas Fuchs
2001-04-18 13:04 ` Multipart PGP sign/encrypt (was: Posting styles and PGP integration?) Josh Huber
2001-04-18 16:25 ` Florian Weimer [this message]
2001-04-18 16:57 ` Josh Huber
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=87ae5ekwdk.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).