Plugged remaining mhfixmsg(1) memory leaks.

[nmh] / test / mhfixmsg / test-mhfixmsg
diff --git a/test/mhfixmsg/test-mhfixmsg b/test/mhfixmsg/test-mhfixmsg

index bd63446aa14a13583f121379c45311a084237fdc..5f33b79b917b8975e464236c6ce8d6ecae7da4ee 100755 (executable)
--- a/test/mhfixmsg/test-mhfixmsg
+++ b/test/mhfixmsg/test-mhfixmsg
@@ -16,9 +16,10 @@ fi
  
  setup_test
  
+check_exit '-eq 1' mhfixmsg -
+
  #### Make sure that html-to-text conversion is what we expect.
-require_locale en_US.utf-8 en_US.utf8
-LC_ALL=en_US.UTF-8; export LC_ALL
+require_locale en_US.UTF-8 en_US.UTF8 en_US.utf-8 en_US.utf8
  
  expected="$MH_TEST_DIR/test-mhfixmsg$$.expected"
  expected_err="$MH_TEST_DIR/test-mhfixmsg$$.expected_err"
@@ -697,6 +698,7 @@ From: sender@example.com
  Subject: mhfixmsg successful decode of text/plain with failed binary decode
  MIME-Version: 1.0
  Content-Type: multipart/mixed; boundary="----- =_aaaaaaaaaa0"
+Content-Transfer-Encoding: binary
  
  ------- =_aaaaaaaaaa0
  Content-Type: text/plain; charset="iso-8859-1"
@@ -725,6 +727,7 @@ From: sender@example.com
  Subject: mhfixmsg binary decode test
  MIME-Version: 1.0
  Content-Type: multipart/mixed; boundary=\"----- =_aaaaaaaaaa0\"
+Content-Transfer-Encoding: binary
  
  ------- =_aaaaaaaaaa0
  Content-Type: text/plain; charset=\"UTF-8\"; name=\"nul+square.txt\"
@@ -821,6 +824,7 @@ From: sender@example.com
  Subject: mhfixmsg textcharset test
  MIME-Version: 1.0
  Content-Type: multipart/mixed; boundary="----- =_aaaaaaaaaa0"
+Content-Transfer-Encoding: 8bit
  
  ------- =_aaaaaaaaaa0
  Content-Type: text/plain; charset="utf-8"; name="square.txt"
@@ -1068,6 +1072,7 @@ fi
  
  
  # check handling of rfc822 message type
+# also, checks -fixboundary
  start_test "handling of rfc822 message type"
  cat >"$expected" <<EOF
  From: Test <test@example.com>
@@ -1105,7 +1110,7 @@ Date: Fri, 29 Sep 2006 00:00:00
  Message-Id: @test.nmh
  Subject: message with message/rfc822 attachment
  MIME-Version: 1.0
-Content-Type: multipart/mixed; boundary="----- =_aaaaaaaaa0"
+Content-Type: multipart/mixed; boundary="----- =badboundary"
  
  and some garbage before the attachment
  
@@ -1204,7 +1209,6 @@ Yes, the text/plain part really was empty.
  
  ------=_Part_876302
  Content-Type: text/html; charset="UTF-8"
-Content-Transfer-Encoding: 8bit
  Content-Disposition: inline
  
  <html><head>
@@ -1234,7 +1238,6 @@ Content-Disposition: inline
  
  ------=_Part_876302
  Content-Type: text/html; charset="UTF-8"
-Content-Transfer-Encoding: 8bit
  Content-Disposition: inline
  
  <html><head>
@@ -1276,7 +1279,6 @@ Content-Disposition: inline
  
  ------=_Part_876302
  Content-Type: text/html; charset="UTF-8"
-Content-Transfer-Encoding: 8bit
  Content-Disposition: inline
  
  <html><head>
@@ -1712,10 +1714,22 @@ set +e
  run_prog mhfixmsg -file - -outfile - <`mhpath last` >"$actual" 2>/dev/null
  set -e
  #### Expected output is identical to the input message.
+check `mhpath last` "$actual" 'keep first'
+
+
+start_test "pass through message with relative folder path with parse error"
+#### Factor out leading portion of current folder path and make it relative.
+pwd=`pwd`
+set +e
+run_prog mhfixmsg +./`mhpath | sed "s%^$pwd/%%"` last -out - >"$actual" 2>/dev/null
+set -e
+folder -f +inbox >/dev/null
+#### Expected output is identical to the input message.
  check `mhpath last` "$actual"
  
  
  start_test "fix RFC 2047 encoded header parameters"
+#### Also, add C-T-E:8bit to the message headers.
  cat >"$expected" <<EOF
  To: recipient@example.com
  From: sender@example.com
@@ -1723,6 +1737,7 @@ Date: Wed, 28 Sep 2016 11:24:28 -0400
  Subject: invalid header parameter encoding
  MIME-Version: 1.0
  Content-Type: multipart/mixed; boundary=001a114dd3e8fe9c56053d92f414
+Content-Transfer-Encoding: 8bit
  
  --001a114dd3e8fe9c56053d92f414
  Content-Type: text/plain; charset=UTF-8