<br><div class="gmail_quote">On Tue, Dec 20, 2011 at 1:22 PM, Eli Barzilay <span dir="ltr"><<a href="mailto:eli@barzilay.org">eli@barzilay.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <br> 2. There is still an issue with non-ascii content in the body.<br> Digging around, it seems to me that the easiest way to make it work<br> is to always add a "Content-Transfer-Encoding: 8bit" header.<br> <br> Does anyone know if this is a correct way to do this? (I'm not<br> clear about the differences between the different "content"<br> headers.)</blockquote><div><br></div><div>8bit is not considered safe for SMTP - a SMTP server is 8bit safe if it supports 8bitmime (see <a href="http://www.ietf.org/rfc/rfc1652.txt">http://www.ietf.org/rfc/rfc1652.txt</a>), but it's no guarantee that 8bit-safe server will route only with 8bit-safe servers. </div> <div><br></div><div>By default content are encrypted either via quote-printable or base64, with the content-transfer-encoding set accordingly. </div><div><br></div><div>Cheers,</div><div>yc</div><div><br></div><div><br></div> <div><br></div></div>