On Tue, Dec 20, 2011 at 1:22 PM, Eli Barzilay <e...@barzilay.org> wrote:
> > 2. There is still an issue with non-ascii content in the body. > Digging around, it seems to me that the easiest way to make it work > is to always add a "Content-Transfer-Encoding: 8bit" header. > > Does anyone know if this is a correct way to do this? (I'm not > clear about the differences between the different "content" > headers.) 8bit is not considered safe for SMTP - a SMTP server is 8bit safe if it supports 8bitmime (see http://www.ietf.org/rfc/rfc1652.txt), but it's no guarantee that 8bit-safe server will route only with 8bit-safe servers. By default content are encrypted either via quote-printable or base64, with the content-transfer-encoding set accordingly. Cheers, yc
_________________________________________________ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/dev
