Message-ID: <4DD18DFE.7090206@fifthhorseman.net>
Date: Mon, 16 May 2011 16:50:06 -0400
From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.9.2.15) Gecko/20110402 Icedove/3.1.9
MIME-Version: 1.0
To: Carl Worth <cworth@cworth.org>
Subject: MIME restructuring [was: Re: release-candidate/0.6]
References: <8762pn7gth.fsf@servo.factory.finestructure.net>
	<874o4zczr8.fsf@yoom.home.cworth.org>
	<87wrhvyqfn.fsf@servo.factory.finestructure.net>
	<87r57ybcna.fsf@yoom.home.cworth.org>
In-Reply-To: <87r57ybcna.fsf@yoom.home.cworth.org>
Content-Type: multipart/signed; micalg=pgp-sha512;
	protocol="application/pgp-signature";
	boundary="------------enig766C5CB43E706E134D070582"
Cc: Notmuch Mail <notmuch@notmuchmail.org>
Precedence: list
Reply-To: notmuch <notmuch@notmuchmail.org>

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig766C5CB43E706E134D070582
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 05/16/2011 04:42 PM, Carl Worth wrote:
> 	Meanwhile, I still can't tell exactly what the behavioral change
> 	intended is. The commit message talks about "fully recursing"
> 	and "match[ing] the MIME structure of the message". Was it not
> 	fully recursing before? In what way did the output not match the
> 	MIME structure before?

before, the output was a linearized version of the mime tree, in
particular removing the multipart pieces and only enumerating the leaves
in a depth-first walk of the tree.

So a message like this:

A=E2=94=94=E2=94=AC=E2=95=B4multipart/signed 355339 bytes
B =E2=94=9C=E2=94=AC=E2=95=B4multipart/mixed 353462 bytes
C =E2=94=82=E2=94=9C=E2=95=B4text/plain 235 bytes
D =E2=94=82=E2=94=94=E2=95=B4image/jpeg attachment [foo.jpg] 352752 bytes=

E =E2=94=94=E2=95=B4application/pgp-signature attachment [signature.asc] =
1030 bytes

would come out with three parts:

 1) C
 2) D
 3) E

the new code assigns this message to 5 parts:

 1) A
 2) B
 3) C
 4) D
 5) E

This change is critical to be able to properly delineate which parts of
a message were signed and/or encrypted.

hth,

	--dkg


--------------enig766C5CB43E706E134D070582
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/

iQJ8BAEBCgBmBQJN0Y3+XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQwRUU1QkU5NzkyODJEODBCOUY3NTQwRjFD
Q0QyRUQ5NEQyMTczOUU5AAoJEMzS7ZTSFznpCO0P/jtlyDHL1DCTVo+Nr9fFTJln
7TVI1gfETjMPGYY7A6A7dMuKYCjxm7DdvV4nPnqi4yrz/yxja41P161QrdZdzvMb
i4MsivVQWTMUUvCWC2ns86YvHu1wI6LitvBw0DhKMxuKTxmPNsU4R8pUGa/2kQ8U
b99VS87na8F4DCD0a05gdgHejOUJB9dpXcjBj8Kh3yHldHKr/AVjZfokjiX9dc5a
/zrcN16pE1aPC6mFznpqPdhwdXcfWtMu25YpXQTV5NXuEWKXsCynPtO4FCy94DF2
14g5KHldp6PdKSTlfHgaYfF9T0jYCm8Ii06U7vpPRgbiNh7wg87mI7ZteB6B5URb
vBFSCo5bHrHZ+uNnRjRH5GiiMHTzRBcth968N4+TSmaKB8eIBeQ+EwBCZ2Ic9iZQ
xM2n//Jx7Tk0vjbrPMJhc+9+pPvnoGlyMGjhpTGIIuG1cTIU32JEFLTJOeZcedD8
Y4XxwW74sWU25AGyhL1Ya4hBcnrrTE9LZeNdOQ0dz+yW4ABbWP8oq/+tuYWz+eSg
dcYLoiSQbqPqO7zTeqlWtSaUB417CFYyLk4nZ82peMzBGig3fodRtslxuw5sI0de
hGl9rnxa1z3d9ffGUXc56ohRKVZDitnxsVBdrv7Yi3QLcTHsTatsHuoMi6lHQnbO
MisaLcAn2fhPuf+QGduS
=Z+jK
-----END PGP SIGNATURE-----

--------------enig766C5CB43E706E134D070582--