From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/88825 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Florian Weimer Newsgroups: gmane.emacs.gnus.general Subject: Re: Content-Type: =?windows-1252?q?application/pdf; considered as text/plain Date: Sat, 19 Oct 2019 16:58:47 +0200 Message-ID: <87v9sksrx4.fsf@mid.deneb.enyo.de> References: <87eezdb3uf.fsf@example.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="173473"; mail-complaints-to="usenet@blaine.gmane.org" Cc: ding@gnus.org To: Denis =?iso-8859-1?Q?Bitouz=E9?= Original-X-From: ding-owner+M37029@lists.math.uh.edu Sat Oct 19 16:59:52 2019 Return-path: Envelope-to: ding-account@gmane.org Original-Received: from lists1.math.uh.edu ([129.7.128.208]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1iLqCr-000iwc-Vz for ding-account@gmane.org; Sat, 19 Oct 2019 16:59:50 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu) by lists1.math.uh.edu with smtp (Exim 4.92.3) (envelope-from ) id 1iLqC4-0006le-Vy; Sat, 19 Oct 2019 09:59:01 -0500 Original-Received: from mx1.math.uh.edu ([129.7.128.32]) by lists1.math.uh.edu with esmtps (TLSv1.3:TLS_AES_256_GCM_SHA384:256) (Exim 4.92.3) (envelope-from ) id 1iLqC0-0006j6-UR for ding@lists.math.uh.edu; Sat, 19 Oct 2019 09:58:56 -0500 Original-Received: from quimby.gnus.org ([80.91.231.51]) by mx1.math.uh.edu with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.92.3) (envelope-from ) id 1iLqBz-0003XR-Br for ding@lists.math.uh.edu; Sat, 19 Oct 2019 09:58:56 -0500 Original-Received: from albireo.enyo.de ([37.24.231.21]) by quimby.gnus.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1iLqBt-0001Nt-CK for ding@gnus.org; Sat, 19 Oct 2019 16:58:51 +0200 Original-Received: from [172.17.203.2] (helo=deneb.enyo.de) by albireo.enyo.de with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) id 1iLqBs-0002GT-3E; Sat, 19 Oct 2019 14:58:48 +0000 Original-Received: from fw by deneb.enyo.de with local (Exim 4.92) (envelope-from ) id 1iLqBr-00008S-Ud; Sat, 19 Oct 2019 16:58:47 +0200 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") List-ID: Precedence: bulk Xref: news.gmane.org gmane.emacs.gnus.general:88825 Archived-At: * Denis Bitouz=C3=A9: > =E2=94=82 Content-Type: =3D?windows-1252?q?application/pdf; > =E2=94=82 name=3D"PVCONSEIL DIRECTION 09 Septembre 2019.pdf" > Strangely enough, the attached PDF file is considered by Gnus as a plain > text file. > > =E2=94=8C=E2=94=80=E2=94=80=E2=94=80=E2=94=80 > =E2=94=82 text/plain; PVCONSEIL DIRECTION 09 Septembre 2019.pdf > =E2=94=94=E2=94=80=E2=94=80=E2=94=80=E2=94=80 > > Do you know what's going on? Reading Section 5.1 of RFC 2045 and section 5 of RFC 2047 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.