Content-Type: multipart/signed; protocol="application/pgp-signature";
 micalg="pgp-sha256"; boundary="===============5813283568621693483=="
MIME-Version: 1.0
Content-Disposition: inline
From: Johannes Schauer <josch@debian.org>
User-Agent: alot/0.3.6
To: Jani Nikula <jani@nikula.org>, "David Bremner" <david@tethera.net>,
 "David Bremner" <david@tethera.net>, notmuch@notmuchmail.org
References: <1443260122-5122-2-git-send-email-jani@nikula.org>
 <1444126846-1918-1-git-send-email-david@tethera.net>
 <87r3kscrsm.fsf@nikula.org>
In-Reply-To: <87r3kscrsm.fsf@nikula.org>
Message-ID: <20151018120544.4280.70668@localhost>
Subject: Re: [WIP] tests: add test for case insensitive Content-Disposition
Date: Sun, 18 Oct 2015 14:05:44 +0200
Precedence: list

--===============5813283568621693483==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

Hi,

Quoting Jani Nikula (2015-10-18 13:58:01)
> On Tue, 06 Oct 2015, David Bremner <david@tethera.net> wrote:
> > These broken now, but will be fixed in the next commit
> > ---
> >
> > The first test is OK, but the second one currently fails. It isn't
> > clear to me if content dispositions permit RFC2047 style
> > encoding. GMime does not decode them automatically (hence this test is
> > failing). What is true is that the RFC states "Unrecognized
> > disposition types should be treated as `attachment'". So maybe the
> > logic in patch 1 should be reversed to check !=3D 'inline'.
> =

> > +Content-Type: text/plain
> > +Content-Disposition: =3D?utf-8?b?YXR0YWNobWVudDsgZmlsZW5hbWU9ImJlZ3LDv=
MOfdW5n?=3D
> > + =3D?utf-8?b?LnBkZiI=3D?=3D
> > +Content-Description: this is a very exciting file
> =

> Did you handcraft the example, or did some program actually produce
> this? I don't think this is [RFC 2231] compliant. IIUC only the content
> disposition parameter values may contain encoded words with
> charset/language specification. Like this,
> =

> Content-Disposition: attachment; filename=3D"=3D?utf-8?B?cMOkw6RtaWVz?=3D"

I'm using alot as my MUA and that produced the Content-Disposition line I
quoted.

Thanks!

cheers, josch

--===============5813283568621693483==
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Description: signature
Content-Type: application/pgp-signature; name="signature.asc"; charset="us-ascii"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAABCAAGBQJWI4sYAAoJEPLLpcePvYPhjnsP/1yEawnlB7hExS9Bb8dUqOh7
paNeYjCUNAGko0z+Kt4YysWvK/T7McXr/U9t6osmeKoaRmiCijUTi/9yfXBu3to1
Ou28Fa/gUyfJbiMtE8JbTUfqB/dOSy2wY5RNfAqikU8NkhuNsAjhkncRautZ+YyY
HLJUigT6V5nVoN7FlGjJ1atalEqbn5kpZlnIIafQWW5M5cnHSWiL1n7lmBjWev/T
bQyDmKGN7JN6eyeyHbqvqIcNIPsGQd7sODUNW4ukUz9R1wVzNGBWqpXiI8+zCN3d
YXg1jMNEzGaAjYTcyFKYe74KD2E5tgDeXmII63B7cpsry6OJRHcQUD9I8CJWylC9
ZRuPk4YZy9s8CMtioTPoTq+w8siccSLB9Qcrr3pWWy1b4sNCDgnmSYQD9YJuGgkt
4pzYX3AaorN2ILEuWzN8tqb7iTQXfQLoLYSFoR6lrVO48BGBY7L8Wc+OJUkw+AeX
Czel0eD2mny6SxFw7NtRsDBo1Wwzp869YKd2X0MTVrUm9ZXlRfGcXAGQFBTQFPTn
WaYnSCY9bKpXoZldI9tJq6wIoPd54w6GYCbMLMEZisn4mFHVeOgGlwPUaYzsm86T
835AGm62l+26M50V4L6c3DTJ1D5O8sKsXSA9CakPypSGyGXOZAY8gNZX7Y+sof7Q
YcbmXyBxKNCFpTrkQW0h
=H93j
-----END PGP SIGNATURE-----

--===============5813283568621693483==--