Re: Bogusly RFC2047'd "inline" for Content-Disposition

    Date:        Sat, 26 Sep 2020 17:09:36 +0100
    From:        Ralph Corderoy <ralph(_at_)inputplus(_dot_)co(_dot_)uk>
    Message-ID:  
<20200926160936(_dot_)731172209E(_at_)orac(_dot_)inputplus(_dot_)co(_dot_)uk>

  | that field does not parse so RFC 2183's

How do you know for sure?  In this case it seems unlikely, but
any string could be "An extension token defined by a
                    standards-track RFC and registered
                    with IANA"

The code certainly isn't going to go look in the IANA registry to see
if some unknown string is registered there or not, all it is possible
to do is assume that it might have been.

kre