On Mon, 7 Jan 2002 20:04, Alessandro Vesely wrote: > Simon Cocking writes: > > [...] > > My interpretation of the RFC is that 'binary' content transfer > > encoding should allow 8-bit characters in the body > > The "binary" content-transfer-encoding requires a binary > transport, not merely 8bitmime. Under ESMTP it would > conflict with the concept of a line terminated by CRLF, > which is inherently not binary.
Yep -- that's a good point. However, the perl MIME-tools classes generate MIME messages which have this content-transfer-encoding. > AFAIK, binary is only used when encoding HTTP posts > with the MIME multipart/form-data content type. It > might also be used for an imap server internal storage, > with questionable advantages. The messages I was referring to were generated by either Microsoft Outlook, or the MIME-tools modules; hence my concern. The code I maintain which uses MIME-tools I can manage (by forcing generated messages to the 8bit MIME-type) but I'm worried that Outlook users will receive bounce notifications which they won't understand. -- Simon Cocking <[EMAIL PROTECTED]> Network Operations MailGuard Pty. Ltd. -- Message protected by MailGuard: e-mail anti-virus and content filtering. http://www.mailguard.com.au _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
