Re: attachment names

[Simon Josefsson <sj@extundo.com>]

[ding: cc of a private response, with a solution to the problem in
this thread]

Christoph Conrad <C.Conrad@cli.de> writes:

>     Simon> No, gnus is correct, outlook is violating MIME specs.
>     Simon> However, it doesn't seem to be alone in this behaviour, so
>     Simon> perhaps we should try to support QP encoded parameter values
>     Simon> anyway. (The "proper" solution would be to make every other
>     Simon> client support rfc 2231.)
>
> I found a simple workaround:

The following won't require modifying gnus, which probably is more
future-safe.

(require 'mail-parse)
(defun my-parse-string (string)
  (rfc2231-parse-string (rfc2047-decode-string string)))
(defalias 'mail-header-parse-content-type 'my-parse-string)
(defalias 'mail-header-parse-content-disposition 'my-parse-string)

Do you all think Gnus should handle this by default, even though it's
wrong?  It would cause problems (only) if someone actually intended
the filename to be a valid QP encoded word.  That isn't very likely
IMHO.