Odd character, was Re: buster, ekiga.
On Tue 23 Jul 2019 at 11:07:37 (-0400), Greg Wooledge wrote:
> On Tue, Jul 23, 2019 at 07:41:20AM -0700, peter@easthope.ca wrote:
> > * From: Brad Rogers
>
> Oh, it's this guy again.
>
> /me looks at the raw mail message with less(1)
>
> * From: Brad Rogers ^@brad@fineby.me.uk^@
>
> 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.
>
> Other people are seeing the entire message truncated at that point, not
> just one line truncated.
>
> Peter, whatever you're doing with your outgoing mail is really strange,
> and if possible, you should try to stop it. Embedding raw NUL characters
> in the body of an email is a problem.
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?
000017C0 64 2D 73 65 │ 61 72 63 68 │ 2F 45 31 68 │ 70 76 79 69 │ 2D 30 30 30 d-search/E1hpvyi-000
000017D4 31 6E 78 2D │ 4B 6C 40 64 │ 61 6C 74 6F │ 6E 2E 69 6E │ 76 61 6C 69 1nx-Kl@dalton.invali
000017E8 64 0A 52 65 │ 73 65 6E 74 │ 2D 44 61 74 │ 65 3A 20 54 │ 75 65 2C 20 d.Resent-Date: Tue,
000017FC 32 33 20 4A │ 75 6C 20 32 │ 30 31 39 20 │ 31 34 3A 35 │ 37 3A 32 30 23 Jul 2019 14:57:20
00001810 20 2B 30 30 │ 30 30 20 28 │ 55 54 43 29 │ 0A 0A 2A 09 │ 46 72 6F 6D +0000 (UTC)..*.From
00001824 3A 20 42 72 │ 61 64 20 52 │ 6F 67 65 72 │ 73 20 80 62 │ 72 61 64 40 : Brad Rogers .brad@
00001838 66 69 6E 65 │ 62 79 2E 6D │ 65 2E 75 6B │ 80 0A 2A 09 │ 44 61 74 65 fineby.me.uk..*.Date
0000184C 3A 20 46 72 │ 69 2C 20 31 │ 39 20 4A 75 │ 6C 20 32 30 │ 31 39 20 31 : Fri, 19 Jul 2019 1
00001860 39 3A 33 32 │ 3A 34 36 20 │ 2B 30 31 30 │ 30 0A 3E 20 │ 49 74 20 77 9:32:46 +0100.> It w
00001874 61 73 20 72 │ 65 70 6C 61 │ 63 65 64 20 │ 62 79 20 45 │ 6D 70 61 74 as replaced by Empat
00001888 68 79 2E 0A │ 0A 54 68 61 │ 6E 6B 73 2E │ 20 20 45 6D │ 70 61 74 68 hy...Thanks. Empath
Well, here's what I think is going on. The OP wrote "The links are
from the debian mailing list software. 128270(9) =
1F50E(E) or 128270(decimal) = 1F50E(hexadecimal). U+1F50E is beyond
the list in …"
So it would appear the OP has pasted the Unicode "RIGHT-POINTING
MAGNIFYING GLASS" character into their postings, which seems somewhat
reasonable as it's used on the Debian web pages to mark all the
Message-IDs and references thereto.
Where that gets mangled along the way, I can't guess. but it would see
that 0x80 is a reasonable choice as that's a Latin-1 Control Character
with the meaning PAD.
https://en.wikipedia.org/wiki/Latin-1_Supplement_(Unicode_block)
Converting it to NUL seems hazardous to me, almost asking for trouble.
Cheers,
David.
Reply to: