"Jason R. Mastaler" <[EMAIL PROTECTED]> writes: >> so, theories on how one should format the confirm_request message so >> that mail clients will properly see 8 bit characters?
[...] > I've tried adding these to my confirm_request.txt which contains a > euro sign, and it does work. i.e, > > From: "%(FULLNAME)s" <%(recipient_address)s> > Subject: Please confirm your message > Content-Type: text/plain; charset=iso-8859-15 > Content-Transfer-Encoding: quoted-printable I gave you some bad advice, so I'm here to correct it after having learned more about how to handle 8-bit data in e-mail. Basically, it's not a good idea to send email containing 8-bit data. These days _most_ (but not all) SMTP servers supports 8-bit transmissions via the 8BITMIME ESMTP extension. However, it's not required that an SMTP server support 8-bit transmissions, and RFC 2821 gives it liberty to clear the high-order bit on such messages (therefore garbling the content) and/or outright bounce the message. This is bad news for TMDA since it means your confirmation request might never reach its recipient. There is no way you can account for all the SMTP servers between you and your recipient, so it's better to be safe avoid 8-bit transmissions. This problem is gotten around by encoding the headers and/or body of the outgoing message with either quoted-printable or base64 so it can be transmitted as 7-bit data, and then the message is decoded by the recipient's mail client. Current releases of TMDA do not have this capability. The next release will. In the meantime, I'd suggest removing any Content-* lines as well as the Euro symbol (and any other 8-bit data) from your templates. The same advice applies to any of you using languages in your templates with 8-bit character sets! If you really need to retain that content and are feeling brave, here's a hack to try: Leave those Content-* headers in your template, and then hand encode your template body with quoted-printable and then insert that back into your .txt file. If you don't feel comfortable with this, wait until the next TMDA release which will automate all of this. _____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
