Re: name and filename parameters
Keith Moore <moore@network-heretics.com> Sat, 21 June 2008 14:08 UTC
Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m5LE8LZK068260 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 21 Jun 2008 07:08:21 -0700 (MST) (envelope-from owner-ietf-smtp@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id m5LE8LH6068258; Sat, 21 Jun 2008 07:08:21 -0700 (MST) (envelope-from owner-ietf-smtp@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-smtp@mail.imc.org using -f
Received: from m1.imap-partners.net (m1.imap-partners.net [64.13.152.131]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m5LE8JIM068244 for <ietf-smtp@imc.org>; Sat, 21 Jun 2008 07:08:20 -0700 (MST) (envelope-from moore@network-heretics.com)
Received: from lust.indecency.org (user-119b1dm.biz.mindspring.com [66.149.133.182]) by m1.imap-partners.net (MOS 3.8.4-GA) with ESMTP id AVJ57499 (AUTH admin@network-heretics.com) for ietf-smtp@imc.org; Sat, 21 Jun 2008 07:08:18 -0700 (PDT)
Message-ID: <485D0B50.4080205@network-heretics.com>
Date: Sat, 21 Jun 2008 10:08:16 -0400
From: Keith Moore <moore@network-heretics.com>
User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421)
MIME-Version: 1.0
To: Francesco Gennai <francesco.gennai@isti.cnr.it>
CC: ietf-smtp@imc.org
Subject: Re: name and filename parameters
References: <01MW9A0NEWP08WWGUF@mx.isti.cnr.it>
In-Reply-To: <01MW9A0NEWP08WWGUF@mx.isti.cnr.it>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-smtp@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-smtp/mail-archive/>
List-ID: <ietf-smtp.imc.org>
List-Unsubscribe: <mailto:ietf-smtp-request@imc.org?body=unsubscribe>
as far as I know, the name parameter is only defined for the application/octet-stream content-type. content-disposition is the standard way to associate a filename with a MIME body part. many user agents have supplied a name parameter with other content-types, but this is not standard and never has been. content-disposition was defined some time after the original MIME specifications that defined the name parameter for application/octet-stream, so many user agents borrowed the name parameter for use with other content-types. RFC 3851 appears to be recommending nonstandard behavior, though it is probably mostly harmless. Keith Francesco Gennai wrote: > Question about composing a MIME part where I would suggest > also the file name. > > Question: > In the case that I would suggest a file name to the remote > MIME client could I use only the name parameter of the content-type > or MUST I add the content-disposition header with the filename parameter? > > My doubt come also from the following sentence in RFC3851 > (Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.1 > Message Specification): > > .. ..... . > 3.2.1. The name and filename Parameters > > For the application/pkcs7-mime, sending agents SHOULD emit the > optional "name" parameter to the Content-Type field for compatibility > with older systems. Sending agents SHOULD also emit the optional > Content-Disposition field [CONTDISP] with the "filename" parameter. > If a sending agent emits the above parameters, the value of the > parameters SHOULD be a file name with the appropriate extension: > .... ..... ... > > where a system using only the name parameter is considered an "old system". > So, I don't understand if "old system" is related to some old S/MIME > system, or to a generic old MIME system.... > > Francesco >
- Re: name and filename parameters Francesco Gennai
- Re: name and filename parameters ned+ietf-smtp
- Re: name and filename parameters Keith Moore
- name and filename parameters Francesco Gennai