Sam Varshavchik <mrs...@courier-mta.com> wrote:
Julian Mehnle writes:
I'd have to point him to an RFC implicitly or explicitly forbidding it.
I couldn't find any such statement in RFC 2045 ("MIME"), and neither in
Look closer. RFC 2045, section 6.2, page 16:
"Thus there are no circumstances in which the "binary"
Content-Transfer-Encoding is actually valid in Internet mail."
Can't get any more clear than that.
Oh dear. I had read section 6.2 (among others) of RFC 2045 in another
context recently, but stopped on page 15 and skipped the rest of the
section. I should have re-read it completely -- please excuse my ignorance,
and thanks for pointing me in the right direction.
On a related note, for anyone who's interested: there seems to be an
experimental SMTP extension for sending binary MIME messages (RFC 1830[1]).
James A Baker <jaba...@mac.com> wrote:
I believe Sam was saying that the encoding *name* of "binary" is
invalid, not specifically that binary content is the problem. [...] The
proper encoding name, IIRC, would be "8bit" -- or maybe it's "8-bit",
but I think the hyphen is not used.
Actually, there *is* a CTE type of "binary", next to "8bit".
Julian.
[1] http://www.rfc-editor.org/rfc/rfc1830.txt
9 messages in net.sourceforge.lists.courier-users[courier-users] RE: "Content-Transfer...
