Re: mhfixmsg -fixcte not working?

[Paul Fox]

ralph wrote:
 > Hi Paul,
 > 
 > >     mhshow: "message/rfc822" type in message 1 should be encoded in 7bit 
 > > or 8bit, continuing...
 > ...
 > > I thought (from reading the man page, and skimming the code) that this
 > > change to C-T-E (i.e., binary --> 8bit) is exactly what -fixcte was
 > > supposed to do.
 > 
 > What does ‘mhfixmsg -version’ print,

I'm running top-of-git:
mhfixmsg -- nmh-1.7+dev 1.7-branchpoint-775-ga8b8a241 built 2021-12-09 13:08:06 
+0000 on grass

 > and what does the -fixcte paragraph in mhfixmsg(1) say?

   The  -fixcte  switch  enables  a  transformation to change the Content-
   Transfer-Encoding from an invalid value to 8-bit in message parts  with
   a Content-Type of multipart and message, as required by RFC 2045, §6.4.
   That condition is indicated by a “must be encoded in 7bit, 8bit, or bi‐
   nary”  error message from mhlist and other nmh programs that parse MIME
   messages.

Perhaps I'm not interpreting the conditions correctly:  "...in message
parts with a Content-Type of multipart and message..."

=----------------------
paul fox, pgf@foxharp.boston.ma.us (arlington, ma, where it's 30.7 degrees)