Message-ID: <4E08F069.2070701@fifthhorseman.net>
Date: Mon, 27 Jun 2011 17:04:41 -0400
From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.9.2.17) Gecko/20110516 Icedove/3.1.10
MIME-Version: 1.0
To: Notmuch Mail <notmuch@notmuchmail.org>
Subject: Re: [PATCH] Do not attept to output part raw if part is not
 GMimePart.
References: <1307032735-27427-1-git-send-email-jrollins@finestructure.net>
	<1307120466-4980-1-git-send-email-jrollins@finestructure.net>
	<87wrgccedd.fsf@yoom.home.cworth.org>
	<87mxh319un.fsf@servo.factory.finestructure.net>
	<BANLkTik8v7uZDcO4wV1Ve1Lymd03Z-WWdw@mail.gmail.com>
In-Reply-To: <BANLkTik8v7uZDcO4wV1Ve1Lymd03Z-WWdw@mail.gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha512;
	protocol="application/pgp-signature";
	boundary="------------enig378C3B4467E8ABB9EE4D8BA2"
Precedence: list
Reply-To: notmuch <notmuch@notmuchmail.org>

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig378C3B4467E8ABB9EE4D8BA2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 06/27/2011 04:43 PM, Austin Clements wrote:
> Just to clarify my understanding, --format=3Draw is only intended to
> work on either the whole message (special-cased in do_show_single) or
> a leaf MIME part, and in any other case, it will output nothing?  The
> raw output test cases seem pretty thin.

I personally think that --format=3Draw *should* work on non-leaf parts; i=

don't know if that was the original intent.

> (BTW, I believe the show restructuring I have under way should both
> lift this restriction and eliminate the special case.)

I hope the tests for this feature can eventually include some weird
compound parts with whitespace-wrapped header lines, odd MIME
delimiters, character encodings, etc.  It would be really good if the
--part=3Dwhatever --format=3Draw output produces byte-for-byte identical
streams.  Both PGP/MIME and S/MIME signatures rely on explicit opacity
of the signed MIME parts, so being able to retrieve the signed data
precisely would be quite useful for weird corner cases.

	--dkg


--------------enig378C3B4467E8ABB9EE4D8BA2
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.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQJ8BAEBCgBmBQJOCPBpXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQwRUU1QkU5NzkyODJEODBCOUY3NTQwRjFD
Q0QyRUQ5NEQyMTczOUU5AAoJEMzS7ZTSFznpdXgP/RUBVhSEZdPNQpkP5s0wV+CS
w26vm1DvGbQL+Y76v9b87FHs/inQxX3o92PAi1bn3AxIIi6z2ty1Lj9jBLQ1RDzr
oZEdfpaTK6YUvrSvTGtuG22CJ4+/Sd8YYKOHFDIrNXMlsOx2nF2KLi6mHDW7gMRY
9+3ZXrqI5g9TMFJIPKqaQ/YSyPso1fCjQmO/9nZRFh7LSacsQ4Zj4yESLz7/wCYo
AKwYqXjRxfGWqLlJ08w4yUPOgX3UWFx+jg0kXrjpHFYmkcZUVDQyy/m8R6//+7Lj
KpuCzAFbHMjftE+cp2qIajxeMe2roJbBpfgrFZQlV8n18QOvTSWDUJqOCBaGryma
whjd2GIAUuMPetVoI2WmXTeEbOhbFCIw2ULrxG0rG2T3xqhL9Vq5t5Ue+llqaLFS
cgExrd4AxCdtvcU+zaOLCsB/z/JCk2x8MW136MfE0XwgMhVURFxJ00RnN2qYTr+W
605VNsem14vL+6DeSzBjxN7P3TeLU3QzgrNhRpiz18ExRtDcwkmtGEAA4/Pc6vqd
T3evYq302zTe/JKhzKPddSo6N27lEeouLwBPZpAfnnmgonkpzz2HssDrazCWcCS6
Pj7jfAGGn0GQtRcWw6O0GQiSPWrYeEsEv1/OxV2SuHWTWz1VyDfFjebF0FUu8He/
31MEVzY1i4OyzUwf7GKa
=QlMT
-----END PGP SIGNATURE-----

--------------enig378C3B4467E8ABB9EE4D8BA2--