Re: octet/stream attachment with non-ascii file name
Hello Anders,
On Saturday, September 11, 2004 at 6:53:08 PM +0200, Anders Helmersson wrote:
>| Content-Type: application/octet-stream;
>| name="=?iso-8859-1?Q?f=F6rs=F6k=2Epng?="
>| Content-Disposition: attachment;
>| filename="=?iso-8859-1?Q?f=F6rs=F6k=2Epng?="
> I haven't checked the appropriate RFC so I cannot tell if the attached
> message complies or not (produced by microsoft exchange V6.0.6249.0).
It violates chapter 5 of RFC 2047 who states:
| An 'encoded-word' MUST NOT be used in parameter of a MIME Content-Type
| or Content-Disposition field, or in any structured field body except
| within a 'comment' or 'phrase'.
There is a different encoding for attachment filenames, specified in
RFC 2231. It is used by all good mailers, including Mutt.
>| Content-Description: =?iso-8859-1?Q?f=F6rs=F6k=2Epng?=
> The file name is correctly displayed in the attachment menu as
> "försök.png"
Probably OK because of the valid "Content-Description:". Chapter 8
of RFC 2045 allows encoded-words there:
| the mechanism specified in RFC 2047 may be used for non-US-ASCII
| Content-Description values.
> I get "Save to file: =?iso-8859-1?Q?f=F6rs=F6k=2Epng?="
| set rfc2047_parameters
| set create_rfc2047_parameters
The first will decode the ugly filename, and is harmless. The second
will generate such rubish, and should *NOT* be used, unless you have to
(like when spitt^Wsending attachments to Outlookers).
Bye! Alain.
--
set honor_followup_to=yes in muttrc is the default value, and makes your
list replies go where the original author wanted them to go: Only to the
list, or with a private copy.