While what I wrote below is true, I didn't understand correctly the
problem with demime. I thought it properly "demimed" the message,
including the headers. Turns out it just stupidly and brokenly mangled
the body. And it looks like the problem is fixed now. Yay!
Simon
On 2012-06-05 08:39, Simon Perreault wrote:
On 2012-06-04 19:10, Jérémie Courrèges-Anglas wrote:
AFAIK SMTP without MIME can only transport ASCII.
Sure, but shear.ucar.edu advertizes 8BITMIME, the only problem here is
demime.
8BITMIME is useless. It only allows SMTP to transport arbitrary 8-bit
content. It still doesn't allow you to specify a character set other
than ASCII. So what are you going to do with this extra bit? Unless you
can communicate the character set, you're still pretty much stuck with
ASCII. You need MIME, with its Content-Type header, to be able to
specify a character set other than ASCII.
8BITMIME is an optimization to allow bodies to be encoded more
efficiently, using 8 bits instead of 7. But you need an 8-bit character
set in order to benefit from it.
Simon
--
DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 open-source --> http://ecdysis.viagenie.ca
STUN/TURN server --> http://numb.viagenie.ca
