Re: mysterious c0 80

[Ken Hornstein]

>> ...draft file does NOT contain a '\n' as the last character?  My
>> memory is that for some strange reason Emacs like to default to doing
>> that.  I suspect we do not test for that.
>
>A POSIX text file is zero or more lines where a line is zero or more
>bytes terminated by '\n'.

I don't make the news, I just report it.  My vague memory is that this
is centered around Emacs having it's roots in a pre-UNIX operating system.

However, it seems like Mike's problem is NOT that; the last two bytes of
his draft file are 00 a0.  Cy's bug report said that can happen anywhere,
though.

I know this change was to handle NUL bytes in outgoing messages, but I am
wondering if maybe we should reject such drafts?  Seems like any message
actually sent with a NUL in it would be rather unfriendly.  That might
break things for people using MH-E, though, and as we've seen before that
has a very long release cycle.

According to RFC 5322, a NUL in a message body is not permitted.  From
§3.5:

   body            =   (*(*998text CRLF) *998text) / obs-body

   text            =   %d1-9 /            ; Characters excluding CR
                       %d11 /             ;  and LF
                       %d12 /
                       %d14-127

Obviously if you are sending binary, you can (RFC 2045 explicitly
disallows NUL when sending 8bit).  I realize that I started this whole
mess last time I asked about this.  Sigh.

--Ken