[Top] [All Lists]

Re: [ietf-822] RFC 2183: Unparseable Content-Disposition Field.

2020-09-26 17:09:06
On Sat, 26 Sep 2020 17:42:51 +0100, Ralph Corderoy said:
Hi, says what to
do if the disposition type is unrecognised, but not what to do if the
Content-Disposition field does not parse.  For example,

    Content-Disposition: =?utf-8?Q?inline?=

is being seen on real-life emails due to a bug.

Ralph: Can you confirm/deny the datestamp on the mail you saw this on?

On another mailing list, it was attributed to the Magento/Zend mailer software,
but various fixes to those packages were made all the way back in Dec 2019. So
before devoting much resources to it, we should confirm whether the cause has
repented and changed their ways, or if somebody needs to update their system,
or something else is going on...

(Back in 2016, there was a bot that encoded many of the headers using
=?utf-8?B?...  encoding, but that one got fixed within a few hours)

Attachment: pgpL3u1Tzo4XN.pgp
Description: PGP signature

ietf-822 mailing list
<Prev in Thread] Current Thread [Next in Thread>