On 2000-09-27 13:29:35 -0500, Petr Hlustik wrote:
> I think somebody asked about this earlier but the problem apparently
> persists: mutt does not decode attachment names. Example:
>
> [-- Attachment #2: =?ISO-8859-2?Q?mar=BBa=2Ejpg?= --]
> [-- Type: image/jpeg, Encoding: base64, Size: 33K --]
>
> Obviously, when trying to save this, mutt offers the nonsense string as the
> name. Assuming the name encoding was done correctly by the sender's mailer,
> can this be fixed or worked around in mutt?
Actually, that use of the rfc2047 encoding is prohibited in the
standard. However, as a workaround, you can set the
$rfc2047_parameters variable.
--
Thomas Roessler <[EMAIL PROTECTED]>
