From: Florian Weimer <fw@deneb.enyo.de>
To: "Denis Bitouzé" <dbitouze@wanadoo.fr>
Cc: ding@gnus.org
Subject: Re: Content-Type: =?windows-1252?q?application/pdf; considered as text/plain
Date: Sat, 19 Oct 2019 16:58:47 +0200 [thread overview]
Message-ID: <87v9sksrx4.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <87eezdb3uf.fsf@example.com> ("Denis \=\?iso-8859-1\?Q\?Bitouz\=E9\?\= \=\?iso-8859-1\?Q\?\=22's\?\= message of "Wed, 16 Oct 2019 08:29:28 +0200")
* Denis Bitouzé:
> │ Content-Type: =?windows-1252?q?application/pdf;
> │ name="PVCONSEIL DIRECTION 09 Septembre 2019.pdf"
> Strangely enough, the attached PDF file is considered by Gnus as a plain
> text file.
>
> ┌────
> │ text/plain; PVCONSEIL DIRECTION 09 Septembre 2019.pdf
> └────
>
> Do you know what's going on?
Reading Section 5.1 of RFC 2045 and section 5 of RFC 2047
<https://tools.ietf.org/html/rfc2045#section-5.1>
<https://tools.ietf.org/html/rfc2047#section-5>
I don't think encoded-words are allowed in Content-Type headers. The
latter is quite explicit about this:
| + An 'encoded-word' MUST NOT be used in parameter of a MIME
| Content-Type or Content-Disposition field, or in any structured
| field body except within a 'comment' or 'phrase'.
So I would say that the message is malformed.
prev parent reply other threads:[~2019-10-19 14:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-16 6:29 Denis Bitouzé
2019-10-19 14:58 ` Florian Weimer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v9sksrx4.fsf@mid.deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=dbitouze@wanadoo.fr \
--cc=ding@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).