5 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] reformime doesn't dec...
FromSent OnAttachments
Andreas HasenackFeb 1, 2005 11:20 am.patch
Sam VarshavchikFeb 1, 2005 3:52 pm 
Andreas HasenackFeb 2, 2005 5:04 am 
Sam VarshavchikFeb 2, 2005 4:35 pm 
Andreas HasenackFeb 2, 2005 4:47 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [maildropl] reformime doesn't decode (QP nor base64) filenames (PATCH)Actions...
From:Sam Varshavchik (mrs@courier-mta.com)
Date:Feb 2, 2005 4:35:33 pm
List:net.sourceforge.lists.courier-maildrop

Andreas Hasenack writes:

On Tue, Feb 01, 2005 at 06:50:54PM -0500, Sam Varshavchik wrote:

That's because the above mutation is not the correct way to encode 8bit characters in MIME headers. This type of QP/Base64 encoding is valid only for the Subject/From/To/Cc/Bcc headers, and a few others.

See RFC 2231 for the correct way to encode these headers.

I will try (mail RFCs are intimidating). In the meantime, are some test results with three MUAs. In all cases, the attached file is called "bláblá.txt"

mutt: --45Z9DzgjV8m4Oswq Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: attachment; filename*=iso-8859-1''bl%E1bl%E1%2Etxt Content-Transfer-Encoding: 8bit

reformime gets this one correctly: Filename [bl_bl_.txt]:

This is the correct encoding format.

Thunderbird: --------------080408010609090603030907 Content-Type: text/plain; name="=?ISO-8859-1?Q?bl=E1bl=E1=2Etxt?=" Content-Transfer-Encoding: 8bit Content-Disposition: inline; filename="=?ISO-8859-1?Q?bl=E1bl=E1=2Etxt?="

reformime -x gives: Filename [_ISO-8859-1_Q_bl_E1bl_E1_2Etxt__]:

Wrong format. File a bug to fix Thunderbird.

Outlook express: ------=_NextPart_000_0015_01C50864.97F08000 Content-Type: text/plain; format=flowed;
name="=?iso-8859-1?B?YmzhYmzhLnR4dA==?="; reply-type=original Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="=?iso-8859-1?B?YmzhYmzhLnR4dA==?="

reformime -x gives: Filename [_iso-8859-1_B_YmzhYmzhLnR4dA____]:

So, is mutt the only one getting it correctly?

Yup.

(just read the rfc and it seems so: Asterisks ("*") are reused to provide the indicator that language and character set information is present and encoding is being used. A single quote ("'") is used to delimit the character set and language information at the beginning of the parameter value. Percent signs ("%") are used as the encoding flag, which agrees with RFC 2047 )

If yes, then it is bad for the other mailers... As much as I love mutt as I do, it is of course one of the least used MUAs out there... :(

You could try to see if you can get Thunderbird fixed.