Bogusly RFC2047'd "inline" for Content-Disposition

nmh-workers

Bogusly RFC2047'd "inline" for Content-Disposition

2020-09-25 18:16:27

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

[More with this subject...]

<Prev in Thread]	Current Thread	[Next in Thread>
Bogusly RFC2047'd "inline" for Content-Disposition, Conrad Hughes <= Re: Bogusly RFC2047'd "inline" for Content-Disposition, Ken Hornstein Re: Bogusly RFC2047'd "inline" for Content-Disposition, David Levine Re: Bogusly RFC2047'd "inline" for Content-Disposition, Ken Hornstein Re: Bogusly RFC2047'd "inline" for Content-Disposition, David Levine Re: Bogusly RFC2047'd "inline" for Content-Disposition, Ralph Corderoy Re: Bogusly RFC2047'd "inline" for Content-Disposition, Ken Hornstein Re: Bogusly RFC2047'd "inline" for Content-Disposition, Robert Elz Re: Bogusly RFC2047'd "inline" for Content-Disposition, Valdis Klētnieks

Previous by Date:	Running Tests in Parallel. (Was: Make test-mhical pass with BSD yacc.), Ralph Corderoy
Next by Date:	Re: Bogusly RFC2047'd "inline" for Content-Disposition, Ken Hornstein
Previous by Thread:	Re: [nmh-commits] [SCM] The nmh Mail Handling System branch, master, updated. 1.7-branchpoint-587-g843bc85, Ralph Corderoy
Next by Thread:	Re: Bogusly RFC2047'd "inline" for Content-Disposition, Ken Hornstein
Indexes:	[Date] [Thread] [Top] [All Lists]