From: Stainless Steel Rat <ratinox@peorth.gweep.net>
Subject: Re: X-Pgp is not rfc2015
Date: Wed, 21 Apr 1999 14:08:09 -0400 [thread overview]
Message-ID: <99Apr21.140502edt.13854-2@gateway.intersys.com> (raw)
In-Reply-To: Hrvoje Niksic's message of "21 Apr 1999 19:53:19 +0200"
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
* Hrvoje Niksic <hniksic@srce.hr> on Wed, 21 Apr 1999
| Neither do I. But "submitting things to IETF" certainly sounded like
| talking about PGP/MIME to me, unless there is an X-Pgp rfc I know
| nothing about.
Jari might have submitted it. I do not know for certain.
Even so, there *are* some really bad RFCs in the 2000-odd list.
| Anyway, do you agree that a correct MIME implementation /could/
| support PGP/MIME (rfc2015) without breaking the operation?
Yes. Where X-pgp is Stupidly Evil, MIME is just Evil. RFC 2015 is
actually a well thought out document.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v0.9.5 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE3HhQJgl+vIlSVSNkRAmBLAKCkXe/iNTLgO9VviL6LA4mNytFBcwCguHN7
BHL2qaRL3sEFC3OHQldhqUY=
=6ZEH
-----END PGP SIGNATURE-----
--
Rat <ratinox@peorth.gweep.net> \ When not in use, Happy Fun Ball should be
Minion of Nathan - Nathan says Hi! \ returned to its special container and
PGP Key: at a key server near you! \ kept under refrigeration.
prev parent reply other threads:[~1999-04-21 18:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-21 0:04 Hrvoje Niksic
1999-04-21 0:42 ` Stainless Steel Rat
1999-04-21 1:47 ` Hrvoje Niksic
1999-04-21 14:33 ` Stainless Steel Rat
1999-04-21 17:53 ` Hrvoje Niksic
1999-04-21 18:08 ` Stainless Steel Rat [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=99Apr21.140502edt.13854-2@gateway.intersys.com \
--to=ratinox@peorth.gweep.net \
/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).