<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/test/multipart, branch 0.6.1</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=0.6.1</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=0.6.1'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2011-06-03T22:24:35Z</updated>
<entry>
<title>test: modify multipart test to use test_expect_equal_file</title>
<updated>2011-06-03T22:24:35Z</updated>
<author>
<name>Jameson Graef Rollins</name>
<email>jrollins@finestructure.net</email>
</author>
<published>2011-05-28T21:16:30Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=61ff61cc2cb12ecc5020477bf8f7c1b4d31f953a'/>
<id>urn:sha1:61ff61cc2cb12ecc5020477bf8f7c1b4d31f953a</id>
<content type='text'>
Again, this is a much cleaner and more thorough test, and in fact
exposes a bug in the format=text output, that will be fixed the next
commit.  Because of this, some of the multipart tests currently fail.
</content>
</entry>
<entry>
<title>test: Add test showing notmuch corrupts a part with a CRLF pair in it</title>
<updated>2011-05-31T22:39:26Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2011-05-31T22:39:26Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=c6b49ae752e642d779941a63bc65d5107e7010f1'/>
<id>urn:sha1:c6b49ae752e642d779941a63bc65d5107e7010f1</id>
<content type='text'>
Since commit 2f8871df6ea3c0b44f85a0fc1b4f58a6b70b0a0e notmuch has been
using a function (show_part_content) originally written only for text
parts to save all MIME parts. The problem with this is that this
function converts CRLF pairs to LF only and optionally converts to
UTF-8 encoding. These two conversions have the potential to corrupt
binary data when passed through the function.

This test demonstrates that corruption, and so fails currently, until
we fix the bug.
</content>
</entry>
<entry>
<title>test: Fix a misspelling in one of our test cases.</title>
<updated>2011-05-31T22:19:12Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2011-05-31T22:19:12Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=6ca7d73239091e8bff7cb05b145c6696d7b5d79a'/>
<id>urn:sha1:6ca7d73239091e8bff7cb05b145c6696d7b5d79a</id>
<content type='text'>
Not that it affects the correctness of the test, but it's nice to use
proper spelling. This kind of change could invalidate a signature on the
test message, but I think that would have happened previously when the
HTML part was added in the first place.
</content>
</entry>
<entry>
<title>tag signed/encrypted during notmuch new</title>
<updated>2011-05-27T23:22:00Z</updated>
<author>
<name>Jameson Graef Rollins</name>
<email>jrollins@finestructure.net</email>
</author>
<published>2011-05-26T01:01:20Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=1d6b49561f50d6cde1b473f9887e37748e49c02c'/>
<id>urn:sha1:1d6b49561f50d6cde1b473f9887e37748e49c02c</id>
<content type='text'>
This patch adds the tag "signed" to messages with any multipart/signed
parts, and the tag "encrypted" to messages with any
multipart/encrypted parts.  This only occurs when messages are indexed
during notmuch new, so a database rebuild is required to have old
messages tagged.
</content>
</entry>
<entry>
<title>Update some more recent tests to use /usr/bin/env to find bash</title>
<updated>2011-05-27T21:08:04Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2011-05-27T21:08:04Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=33cf04c6a5f76cba2bf56a27504eaf9ac022f5a2'/>
<id>urn:sha1:33cf04c6a5f76cba2bf56a27504eaf9ac022f5a2</id>
<content type='text'>
The recentl-applied patch had grown stale, so update the tests that had
been created since it was originally written.
</content>
</entry>
<entry>
<title>test: Expand multipart test to cover "notmuch reply" as well</title>
<updated>2011-05-24T19:19:18Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2011-05-24T17:56:38Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=e267f9a46731e796f7064c7483de9942caba3c2a'/>
<id>urn:sha1:e267f9a46731e796f7064c7483de9942caba3c2a</id>
<content type='text'>
This gives coverage for the segmentation fault in "notmuch reply" that
was just fixed with the previous commit.
</content>
</entry>
<entry>
<title>test: Expand multipart test to cover part output in all formats.</title>
<updated>2011-05-24T19:19:18Z</updated>
<author>
<name>Jameson Graef Rollins</name>
<email>jrollins@finestructure.net</email>
</author>
<published>2011-05-23T07:46:44Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=916c2aa6247c6ef3d2a9c9c784cf4d3a5de263d0'/>
<id>urn:sha1:916c2aa6247c6ef3d2a9c9c784cf4d3a5de263d0</id>
<content type='text'>
The example multipart message is made a bit more complicated by adding
a message/rfc822 message, and the all parts are output and tested in
all output formats.
</content>
</entry>
<entry>
<title>test: remove hard-coded paths from multipart test</title>
<updated>2011-05-20T18:32:47Z</updated>
<author>
<name>Jameson Graef Rollins</name>
<email>jrollins@finestructure.net</email>
</author>
<published>2011-05-19T13:04:06Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=8b9fc33d9904070d88e8b94711f613886b2eb2db'/>
<id>urn:sha1:8b9fc33d9904070d88e8b94711f613886b2eb2db</id>
<content type='text'>
Small oversite, easily corrected.
</content>
</entry>
<entry>
<title>notmuch show: Properly nest MIME parts within mulipart parts</title>
<updated>2011-05-17T22:58:57Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2011-05-17T22:34:57Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=362ab047c264ae67ec3de041aec637979077db21'/>
<id>urn:sha1:362ab047c264ae67ec3de041aec637979077db21</id>
<content type='text'>
Previously, notmuch show flattened all output, losing information
about the nesting of the MIME hierarchy. Now, the output is properly
nested, (both in the --format=text and --format=json output), so that
clients can analyze the original MIME structure.

Internally, this required splitting the final closing delimiter out of
the various show_part functions and putting it into a new
show_part_end function instead. Also, the show_part function now
accepts a new "first" argument that is set not only for the first MIME
part of a message, but also for each first MIME part within a series
of multipart parts. This "first" argument controls the omission of a
preceding comma when printing a part (for json).

Many thanks to David Edmondson &lt;dme@dme.org&gt; for originally
identifying the lack of nesting in the json output and submitting an
early implementation of this feature. Thanks as well to Jameson Graef
Rollins &lt;jrollins@finestructure.net&gt; for carefully shepherding David's
patches through a remarkably long review process, patiently explaining
them, and providing a cleaned up series that led to this final
implementation. Jameson also provided the new emacs code here.
</content>
</entry>
<entry>
<title>notmuch show: Include output for the enclosing multipart part of a MIME mail</title>
<updated>2011-05-17T21:51:06Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2011-05-17T05:28:36Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=c51d5b3cdb5ca0816816e88ca6f7136a24e74eee'/>
<id>urn:sha1:c51d5b3cdb5ca0816816e88ca6f7136a24e74eee</id>
<content type='text'>
Previously, the outer multipart part of any multipart/mixed,
multipart/signed, etc. MIME message was silently omitted from the
"notmuch show" output. This prevented any client from correctly
determining to which parts a signature applies, for example.

Now, we actually emit these parts as their own parts. The output is
still flattened---the contained parts are not yet included "within"
the multipart part---so it's still not possible to determine to which
parts a signature applies, but this is one step along the path.

The test suite is updated to reflect this change, (though we'll
eventually want to fix the emacs interface to not display buttons for
the multipart enclosure parts as there's nothing useful for the user
to actually do with them).
</content>
</entry>
</feed>
