Added mention of mhfixmsg -fixcte to error message for improper C-T-E in

multipart message.  Thanks to Conrad Hughes for suggesting this.

diff --git a/uip/mhparse.c b/uip/mhparse.c
index 7c8f07dc73ca4090038c4d77f329f99317809188..6f8ebaf1e6d102ed37df87fadcba7404a6e027fc 100644 (file)
--- a/uip/mhparse.c
+++ b/uip/mhparse.c
@@ -1101,8 +1101,9 @@ InitMultiPart (CT ct)
 
        admonish (NULL,
                  "\"%s/%s\" type in message %s must be encoded in\n"
 
        admonish (NULL,
                  "\"%s/%s\" type in message %s must be encoded in\n"

-                 "7bit, 8bit, or binary, per RFC 2045 (6.4).  One workaround "
-                 "is to\nmanually edit the file and change the \"%s\"\n"
+                 "7bit, 8bit, or binary, per RFC 2045 (6.4).  "
+                  "mhfixmsg -fixcte can fix it, or\n"
+                  "manually edit the file and change the \"%s\"\n"

                  "Content-Transfer-Encoding to one of those.  For now",
                  ci->ci_type, ci->ci_subtype, ct->c_file, bp);
        free (cte);
                  "Content-Transfer-Encoding to one of those.  For now",
                  ci->ci_type, ci->ci_subtype, ct->c_file, bp);
        free (cte);