At 8:54 PM 10/27/94, Mr Rhys Weatherley wrote:
... and NO octets are dropped. Everything goes through unchanged,
including NULs.
Definitely agree with the NULs.
There is still a question in my mind about what you mean by "unchanged", as
well as what 1521 means by "does not obey SMTP CRLF semantics".
The question is this:
If the content-type requires newline canonicalization, does CTE: binary
override it? I think it definitely *should* not. I think you could read
the current spec such that it does, though this is not my reading.
The problem datasets are:
1. Normal text with lines, just very long ones.
2. Text that uses CRLF for something other than newline.
I believe that CT: text/plain, CTE: binary is (among other things) for the
former, and that the latter does not belong under type text at all, but
should get a new type.
--
Steve Dorner, Qualcomm Incorporated. "Oog make mission statement."