From 33765e5c2eb18de14fc542a6324c0806af8f59f7 Mon Sep 17 00:00:00 2001 From: Carl Worth Date: Thu, 3 Jun 2010 16:43:21 -0700 Subject: [PATCH] Add a test case for the previous commit. The commit said it fixed a problem with headers >200 characters long. But examination of the code suggests that it was a header of exactly 200 characters long that caused the problem. So we add a test case for that here. Before the fix in the previous commit, valgrind would detect many errors when replying to the message created with this test case. After that commit, those errors are gone. --- test/notmuch-test | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/test/notmuch-test b/test/notmuch-test index a861df16..ca414089 100755 --- a/test/notmuch-test +++ b/test/notmuch-test @@ -798,6 +798,22 @@ References: <${gen_msg_id}> On Tue, 05 Jan 2010 15:43:56 -0800, Sender wrote: > Un-munging Reply-To" +printf " Message with header of exactly 200 bytes...\t" + +add_message '[subject]="This subject is exactly 200 bytes in length. Other than its length there is not much of note here. Note that the length of 200 bytes includes the Subject: and Re: prefixes with two spaces"' \ + '[date]="Tue, 05 Jan 2010 15:43:56 -0800"' \ + '[body]="200-byte header"' + +output=$($NOTMUCH reply id:${gen_msg_id}) +pass_if_equal "$output" "From: Notmuch Test Suite +Subject: Re: This subject is exactly 200 bytes in length. Other than its length there is not much of note here. Note that the length of 200 bytes includes the Subject: and Re: prefixes with two spaces +Bcc: test_suite@notmuchmail.org +In-Reply-To: <${gen_msg_id}> +References: <${gen_msg_id}> + +On Tue, 05 Jan 2010 15:43:56 -0800, Notmuch Test Suite wrote: +> 200-byte header" + printf "\nTesting handling of uuencoded data:\n" add_message [subject]=uuencodetest '[date]="Sat, 01 Jan 2000 12:00:00 -0000"' \