>What's the (config file?) fix so the string in
> filename=SOME_UTF-8_CODED_STRING
>associated w/below attachment headers
>is properly decoded?
Expanding on this a bit ... it is unequivocally WRONG for things like
MIME parameters to be encoded using RFC 2047 rules (it's explicitly
prohibited in t
Hi Tom,
> What's the (config file?) fix so the string in
> filename=SOME_UTF-8_CODED_STRING
> associated w/below attachment headers
> is properly decoded?
...
> Content-Disposition: attachment;
> filename="=?UTF-8?b?Y2xpbWF0ZSBmbHllciB1cGRhdGVkLnBkZg==?="
$ scan -forma '%{Content-Dispositi
