Package: mpack
Version: 1.6-8
Severity: normal
Dear Maintainer,
If a MIME header uses a character set encoding, munpack does not
correctly decode the string when naming the file. For example, if a
MIME header looks like this:
===8<----------------------------------------
--926373431-533330545-903641383=:8047
Content-Type: application/pdf;
name="=?ISO-8859-1?Q?Andr=E9?="
Content-Disposition: attachment;
filename="=?ISO-8859-1?Q?Andr=E9?="
Content-Transfer-Encoding: BASE64
===8<----------------------------------------
Then munpack creates a file that is literally named
"=?ISO-8859-1?Q?Andr=E9?=". Likewise, it's the same problem if the
filename is UTF-8 encoded, which takes the form:
"=?UTF-8?B?blahblah=?=".
This does not comply with RFC 2047. For simple example if the
decoding that's needed, see: http://dogmamix.com/MimeHeadersDecoder/
Perhaps that site will be good for testing purposes.
-- System Information:
Debian Release: 8.4
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages mpack depends on:
ii libc6 2.19-18+deb8u4
mpack recommends no packages.
Versions of packages mpack suggests:
pn inews <none>
ii postfix [mail-transport-agent] 2.11.3-1
-- no debconf information
