There is one thing which troubles me with the "BINARY" transport,
and either you gentlemen (I mean the group, not anybody personally)
don't consider it an issue, or have missed it:
It's not an issue at all.
What happens when I want to process email with MIME-structures
in it (with "--ContentBoundaryString"s in it), and there is a
body-part with a UNICODE 16-bit chars in it containing explicite
16-bit CRLF: 000D 000A ?
Being ASCII incompatible, UNICODE, a Euro local code system, with 16bit
or with utf-7 encoding has absolutely no future.
Masataka Ohta