Message-ID: <522FA24D.8080307@fifthhorseman.net>
Date: Tue, 10 Sep 2013 18:50:53 -0400
From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:17.0) Gecko/20130821 Icedove/17.0.8
MIME-Version: 1.0
To: Austin Clements <amdragon@MIT.EDU>
Subject: Re: [PATCH] lib/cli: pass GMIME_ENABLE_RFC2047_WORKAROUNDS to
	g_mime_init() =?utf-8?q?a test?=
References: <1378839078-6298-1-git-send-email-jani@nikula.org>
	<522F73A4.90802@fifthhorseman.net> <20130910223553.GI1426@mit.edu>
In-Reply-To: <20130910223553.GI1426@mit.edu>
Content-Type: multipart/signed; micalg=pgp-sha512;
	protocol="application/pgp-signature";
	boundary="----enig2KLXWITXHWXJBIDUVJJLO"
Cc: notmuch <notmuch@notmuchmail.org>
Precedence: list

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
------enig2KLXWITXHWXJBIDUVJJLO
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 09/10/2013 06:35 PM, Austin Clements wrote:

> I haven't looked at exactly what workarounds this enables, but if it's
> what I'm guessing (RFC 2047 escapes in the middle of RFC 2822 text
> tokens), are there really subject lines that this will misinterpret
> that weren't obviously crafted to break the workaround? =20

not to get all meta, but i imagine subject lines that refer an example
of this particular issue (e.g. when talking about RFC 2047) will break
;)  I'm trying one variant here.

> The RFC 2047
> escape sequence was deliberately designed to be obscure, since RFC
> 2047 itself caused previously "standards-compliant" subject lines to
> potentially be interpreted differently.

right, and it was designed explicitly to put the boundary markers atword
boundaries, and not in the middle of a word (i think that's what this is
all about, right?).  so implementations which put the boundary markers
in the middle of a word, or which include whitespace within the encoded
text, aren't speaking RFC 2047.

anyway, if there's a rough consensus to go forward with this, i'm not
about to block it.  I understand that a large part of the business of
being an MUA is working around other people's bugs instead of expecting
them to fix them :/  I just don't like mis-rendering other text.

	--dkg


------enig2KLXWITXHWXJBIDUVJJLO
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)
Comment: Using GnuPG with Icedove - http://www.enigmail.net/

iQJ8BAEBCgBmBQJSL6JNXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRFQjk2OTEyODdBN0FEREUzNzU3RDkxMUVB
NTI0MDFCMTFCRkRGQTVDAAoJEKUkAbEb/fpcDlkP/RGwWm+rGz/1yR/JvvcfhDJA
UhxbacLjpd2w5yRqc4iPmUc1O3w2tiXbhV+3d0PWI/NoCQu+bWNsEhfOUS1KUZiC
q0iThisNMMeSS+BgiqjvB6aB6XPmn83SKeG3C/6eduarvzmuDrL/QIog0DJJ0854
8HZNJLYmSYJM1h9E0bjX0DjBAmVJ2Pawc2zcY6BHiJtBx63+JZoJvrftYTcgClpj
8e3n1UJu/9Lv+x77KPQ8p77MMOy79n1NFcneyHGqYTXO071tqyfJy7OQMDPkOyFt
tF7mcI160Mnsujd5dj2CH1d93uTIJ6eZgwhVq4slbC1Bfdure5kFIioT0EqZYwFS
si4ShzmvAtKDBi1ydwhDwtTTg52i/9b0UbprEm22YDpdnZTnZX7GfA42mg5w++bX
hCG0WdSkr7JrFoNncSnjRETPp7IZxvz7eT40vocnKv1l7ZVcaHorNyZEseTEOEX8
eV1QHfxtTsEaJSM2iOiUEEOG4cT6cADlm4qdP6K+c6LokfVTL5ZLKn1BpWfFzkdn
nTeLajJx8XFNR4EYBav4Q4X9W4wNUZH15aCG3JiAfJssBlNIHAI9nYxyN3f9oRHL
1gd2zPXoUkcY321/+3tMjSITEe+9OibZ9eWxFGrTUXUvZfJaPNsLirVPGN+Tmeti
Q+HaUBGs3c/T3THhsoq3
=1sjc
-----END PGP SIGNATURE-----

------enig2KLXWITXHWXJBIDUVJJLO--