On Tue, Jul 23, 2019 at 03:38:33PM -0400, Greg Wooledge wrote: > On Tue, Jul 23, 2019 at 02:19:27PM -0500, David Wright wrote: > > On Tue 23 Jul 2019 at 11:07:37 (-0400), Greg Wooledge wrote: > > > Yup. Two NUL bytes in the body of the message. How completely bizarre. > > > > > > Apparently what mutt does is truncate that *line* at the first NUL > > > byte, but then show all the other lines after that just fine. > > > I don't see any NUL characters, but x80 as shown below. I'm reading > > the cached message that mutt downloaded from an IMAP server. Is that > > different from you? > > In my case, the email is sent first to a Debian 9 system running qmail + > magic-smtpd [...] > I'll try to remember to keep a copy of the next one for hex-dumping. Looking forward :-) > Meanwhile, as a test, I ran the following from my home system outside > the workplace firewall: [...] Interesting. Note that both your tests have a Content-Transfer-Encoding (first: 8bit, second: quoted-printable; the first one gets a slight indigestion, the second not). The original messages have no Content-Type, much less Content-Transfer-Encoding (so x00 as well as x80 should be both a no-no anyway). Cheers -- t
Attachment:
signature.asc
Description: Digital signature