[JDEV] A piece of MIME? (possible alternate solution)

Jeremie jeremie at jabber.org
Wed Aug 11 01:31:12 CDT 1999

> 	I think in this case you are mistaken. Take a look at RFC 2045 sections 6.2
> and 6.3; there's a copy at :
> http://www.oac.uci.edu/indiv/ehood/MIME/2045/rfc2045.html.
> 	My interpretation of all that is: Content-Transfer-Encoding indicates how
> the original data - say, a gzip file or whatever - has been mangled into a
> 'mailable' format. There are only a handful of defined values for
> Content-Transfer-Encoding identity, "quoted-printable", and base64. 'binary'
> encoding is discouraged - it usually won't work - and we can specifically
> disallow binary encoded MIME.
> 	From the RFC:
> "The quoted-printable and base64 encodings transform their input from an
> arbitrary domain into material in the "7bit" range, thus making it safe to
> carry over restricted transports."
> 	So a chunk of MIME message body should always be XML legal text. :)

Yup, my misunderstanding, thank you for correcting me.  In that case,
Content-Transfer-Encoding is perfectly legit and quite appropriate.

If someone wants to write up a summary of the <mime></mime> suggestions
thus far I can post it as an official proposal and we can move forward on
implimenting it.  If nobody else gets to it, I'll write it up in the next
few days.


More information about the JDev mailing list