Message-ID: <51F6C6AA.7010001@fifthhorseman.net>
Date: Mon, 29 Jul 2013 15:46:50 -0400
From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:17.0) Gecko/20130630 Icedove/17.0.7
MIME-Version: 1.0
To: David Bremner <david@tethera.net>
Subject: Re: UTF-8 in mail headers (namely FROM) sent by bugzilla
References: <08cb1dcd-c5db-4e33-8b09-7730cb3d59a2@gmail.com>
	<871u6psjwr.fsf@ericabrahamsen.net>
	<5712cc41-d0ce-4ed3-af1c-37cf639dd9c0@gmail.com>
	<87y58xv71x.fsf@zancas.localnet>
In-Reply-To: <87y58xv71x.fsf@zancas.localnet>
Content-Type: multipart/signed; micalg=pgp-sha512;
	protocol="application/pgp-signature";
	boundary="----enig2LHNJNKRNVBGUMGFBMJAV"
Cc: notmuch@notmuchmail.org
Precedence: list

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
------enig2LHNJNKRNVBGUMGFBMJAV
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 07/23/2013 07:39 AM, David Bremner wrote:
> Franz Fellner <alpine.art.de@gmail.com> writes:
>=20
>>
>> OK, thx. So every app needs to get patched to display those strings
>> properly? Any chance this could be done directly in libnotmuch?  I
>> grepped for "2047" inside te "emacs" subtree, but found nothing (had
>> the hope for a comment for the workaround). Would be interesting to
>> see how this is done, so I can at least try to create a patch (though
>> my ruby is quite basic).
>=20
> In general notmuch relies on libgmime for rfc2047 parsing.  I'm not sur=
e
> of all the details now, but some of the filtering does happen in the
> CLI, not the lib.  You could start by looking at
> gmime-filter-headers.[ch] in the top directory.

I agree this should be handled properly by gmime.  If it turns out that
the library is misbehaving (i.e. that notmuch is using it sensibly and
we're still getting bad data out of well-formed strings), it should be
reported and fixed there.

Just a note that other MUAs are struggling with this sort of thing too:

http://blog.steve.org.uk/international_character_sets_and_encodings_are_h=
ard_.html

Steve Kemp (author of lumail) has good engineering skills and instincts;
anyone actively working on trying to get this fixed "right" within
notmuch (or underlying libraries) could probably drop him an e-mail and
collaborate.  With a decent diagnostic of the specific problems and use
cases, plus a recommendation for where the fix should be and how it
should be done, the two projects together could probably exert
sufficient influence on underlying libraries and toolchains to get them
to address any issues.

sorry to just provide links and not any actual analysis and code.

	--dkg


------enig2LHNJNKRNVBGUMGFBMJAV
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/

iQJ8BAEBCgBmBQJR9saqXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRFQjk2OTEyODdBN0FEREUzNzU3RDkxMUVB
NTI0MDFCMTFCRkRGQTVDAAoJEKUkAbEb/fpcyk0QANMkTyqXqpFZ8sBaKhw1rY/P
SzyCDFYWaTXhPMFDacCEmU6bG8OB1/0VLvPjKwcXs40UHgtxu2aNswJhoyuP0lry
MYZCo/zb3Tup5m6jSXbMaZxvjHZ1kjsOUNR0mvMOJoAva81mbubG15I4obmWSldb
sR4/vYqjGfO8Q69wRzJpJBUPM3qReKUDd8fr0/frI6DR4UYB7QusASLaEp7d/WgY
MBqPD0DIw9nF1FOZ2xX1kdNbtNQvOdK3VBL9793k4VGJMfv/qzkfn3TPHwQMwCNP
OlhjHPUDr1fhZKiFp4xa7dPFIvWEppEdyeNaQ3SLIEV7GHw2Qw1yGubnneh3IEOg
VFXOnmD+eurxyHM6r9KEzmRK4K9X5CA6abLOcNYb6R6FFPZ2BDWZiOGWiTgsyJsl
T/6DlZzubBTg/s3Wj0YKPVCq28/xyt7XT8zw9kMM+7eKNww2boqkZruvFIwFhcx1
Bet8bualMUQasp/B/MN3Z2AQZJD+FoPeYIbqQytkhRBlbIiDbABKINdqnmpMabd1
3/ah9gw/X4/s2/euAY1TzwiIgAfgj30ZD/gn4wXTIZ7sC1ITo/VV9Iyf29X/oHKf
DzCOa0WR9YG5ML0OYDSJqxJEaLomJaAtH3TGzQ/Lcl+A+6dS9+Fik8lhvKarDOxM
nCAIMQidKBxWcXRdAzkf
=VNoq
-----END PGP SIGNATURE-----

------enig2LHNJNKRNVBGUMGFBMJAV--