[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: mhfixmsg -fixcte not working?
From: |
Ralph Corderoy |
Subject: |
Re: mhfixmsg -fixcte not working? |
Date: |
Thu, 09 Dec 2021 15:56:21 +0000 |
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.
...
> > 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.
I MANOPT='--nh --nj'. :-)
David's answered fully. My suspicions were raised by the error you
quoted from mhshow above not matching my mhfixmsg(1) man page, or yours.
should be encoded in 7bit or 8bit,
must be encoded in 7bit, 8bit, or binary
--
Cheers, Ralph.
- mhfixmsg -fixcte not working?, Paul Fox, 2021/12/09
- Re: mhfixmsg -fixcte not working?, Ralph Corderoy, 2021/12/09
- Re: mhfixmsg -fixcte not working?, Paul Fox, 2021/12/09
- Re: mhfixmsg -fixcte not working?,
Ralph Corderoy <=
- Re: mhfixmsg -fixcte not working?, David Levine, 2021/12/09
- Re: mhfixmsg -fixcte not working?, Ken Hornstein, 2021/12/09
- Re: mhfixmsg -fixcte not working?, David Levine, 2021/12/15
- Re: mhfixmsg -fixcte not working?, Paul Fox, 2021/12/15