Re: MIME restructuring [was: Re: release-candidate/0.6]

2011-05-17 Thread Carl Worth
On Mon, 16 May 2011 13:59:51 -0700, Carl Worth wrote: > So what I'd love to see from here is a commit with a description like > the above, and then a test case looking like your example. > > From there, I'd next like a new version of the commit that gets the > intended behavior with less code dup

Re: MIME restructuring [was: Re: release-candidate/0.6]

2011-05-16 Thread Carl Worth
On Mon, 16 May 2011 15:37:49 -0700, Jameson Graef Rollins wrote: > See mml-secure-message-sign-pgpmime to sign an entire message, as > opposed to just a single part. Thanks! That's good to know. (Trying here.) > I think the two paths reconverge later in the series. Can you look > ahead a bit t

Re: MIME restructuring [was: Re: release-candidate/0.6]

2011-05-16 Thread Jameson Graef Rollins
On Mon, 16 May 2011 14:20:07 -0700, Carl Worth wrote: > I'll have to learn better how to control the emacs mail composer in > order to understand how to get signatures to cover attachments if I want > to do that kind of thing. See mml-secure-message-sign-pgpmime to sign an entire message, as oppo

Re: MIME restructuring [was: Re: release-candidate/0.6]

2011-05-16 Thread Daniel Kahn Gillmor
On 05/16/2011 05:20 PM, Carl Worth wrote: > Interestingly, this is not quite the behavior I get (with commit > 373f352). With --format=text I'm now seeing: > > 2) C > 3) D > 4) E --format=text should only show the parts that are readable in text. the ultimate goal is to get the part numbers alig

Re: MIME restructuring [was: Re: release-candidate/0.6]

2011-05-16 Thread Simon Hürlimann
lol, made my day! Simon On 05/16/2011 11:05 PM, Daniel Kahn Gillmor wrote: On 05/16/2011 04:50 PM, Daniel Kahn Gillmor wrote: So a message like this: A└┬╴multipart/signed 355339 bytes B ├┬╴multipart/mixed 353462 bytes C │├╴text/plain 235 bytes D │└╴image/jpeg attachment [foo.jpg] 352752 bytes

Re: MIME restructuring [was: Re: release-candidate/0.6]

2011-05-16 Thread Carl Worth
On Mon, 16 May 2011 16:50:06 -0400, Daniel Kahn Gillmor wrote: > So a message like this: > > A└┬╴multipart/signed 355339 bytes > B ├┬╴multipart/mixed 353462 bytes > C │├╴text/plain 235 bytes > D │└╴image/jpeg attachment [foo.jpg] 352752 bytes > E └╴application/pgp-signature attachment [signature

Re: MIME restructuring [was: Re: release-candidate/0.6]

2011-05-16 Thread Daniel Kahn Gillmor
On 05/16/2011 04:50 PM, Daniel Kahn Gillmor wrote: > So a message like this: > > A└┬╴multipart/signed 355339 bytes > B ├┬╴multipart/mixed 353462 bytes > C │├╴text/plain 235 bytes > D │└╴image/jpeg attachment [foo.jpg] 352752 bytes > E └╴application/pgp-signature attachment [signature.asc] 1030 byt

Re: MIME restructuring [was: Re: release-candidate/0.6]

2011-05-16 Thread Carl Worth
On Mon, 16 May 2011 16:50:06 -0400, Daniel Kahn Gillmor wrote: > 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: [snip example of change]