From: Florian Weimer <fw@deneb.enyo.de>
Subject: Re: MML multipart tag -- what does it do?
Date: Sun, 05 Aug 2001 18:06:07 +0200 [thread overview]
Message-ID: <87ofpu330w.fsf@deneb.enyo.de> (raw)
In-Reply-To: <ilu1ymriwv1.fsf@barbar.josefsson.org> (Simon Josefsson's message of "Sat, 04 Aug 2001 19:00:18 +0200")
Simon Josefsson <jas@extundo.com> writes:
> This requires users to know how the sign/encrypt mechanism they use
> are implemented in MIME. E.g., if you want to sign using PGP/MIME you
> must write the above, if you want to encrypt with S/MIME you need to
> write something completely different because S/MIME encryption doesn't
> use RFC 1847.
Really? I assumed it did, and using S/MIME in a RFC 1847 context is
indeed described in the S/MIME RFCs...
> Maybe users shouldn't need to know that.
Okay, I agree, so there's probably no other choice.
next prev parent reply other threads:[~2001-08-05 16:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-03 16:44 Kai Großjohann
2001-08-03 17:35 ` Simon Josefsson
2001-08-03 18:16 ` ShengHuo ZHU
2001-08-03 17:52 ` ShengHuo ZHU
2001-08-03 19:21 ` Kai Großjohann
2001-08-03 21:05 ` Nuutti Kotivuori
2001-08-04 15:42 ` Florian Weimer
2001-08-04 17:00 ` Simon Josefsson
2001-08-05 16:06 ` Florian Weimer [this message]
2001-08-05 19:54 ` Simon Josefsson
2001-08-17 10:57 ` Lars Magne Ingebrigtsen
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=87ofpu330w.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).