|
From: | Conrad Hughes |
Subject: | Bogusly RFC2047'd "inline" for Content-Disposition |
Date: | Sat, 26 Sep 2020 00:14:59 +0100 |
Just saw this for the first time: Content-Disposition: =?utf-8?Q?inline?= .. causing "mhshow: extraneous information in message 126's Content-Disposition: field (=?utf-8?Q?inline?=)". As far as I can see this is a MUST NOT do, but probably not too hard to accept and DTRT. Thoughts? Conrad
[Prev in Thread] | Current Thread | [Next in Thread] |