From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/37528 Path: main.gmane.org!not-for-mail From: Florian Weimer Newsgroups: gmane.emacs.gnus.general Subject: Re: MML multipart tag -- what does it do? Date: Sun, 05 Aug 2001 18:06:07 +0200 Message-ID: <87ofpu330w.fsf@deneb.enyo.de> References: <2nr8utf2u6.fsf@piglet.jia.vnet> <874rrolurg.fsf@smarttrust.com> <87zo9fq1az.fsf@deneb.enyo.de> NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1035172927 14363 80.91.224.250 (21 Oct 2002 04:02:07 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 21 Oct 2002 04:02:07 +0000 (UTC) Return-Path: Return-Path: Original-Received: (qmail 25560 invoked from network); 5 Aug 2001 15:48:21 -0000 Original-Received: from mail.s.netic.de (HELO mail.netic.de) (212.9.160.11) by gnus.org with SMTP; 5 Aug 2001 15:48:21 -0000 Original-Received: by mail.netic.de (Smail3.2.0.111/mail.s.netic.de) via LF.net GmbH Internet Services via remoteip 212.9.163.52 via remotehost mail.enyo.de with esmtp for mail.gnus.org id m15TQ8a-001X1nC; Sun, 5 Aug 2001 17:48:20 +0200 (CEST) Original-Received: from [192.168.1.2] (helo=deneb.enyo.de ident=exim) by mail.enyo.de with esmtp (Exim 3.12 #1) id 15TQ7U-00071l-00 for ding@gnus.org; Sun, 05 Aug 2001 17:47:12 +0200 Original-Received: from fw by deneb.enyo.de with local (Exim 3.12 #1) id 15TQPn-0000gN-00 for ding@gnus.org; Sun, 05 Aug 2001 18:06:07 +0200 Original-To: ding@gnus.org In-Reply-To: (Simon Josefsson's message of "Sat, 04 Aug 2001 19:00:18 +0200") User-Agent: Gnus/5.090004 (Oort Gnus v0.04) Emacs/20.7 Original-Lines: 14 Xref: main.gmane.org gmane.emacs.gnus.general:37528 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:37528 Simon Josefsson 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.