Simon Cocking writes: > Hi all, > > I'm seeing problems with Courier (0.36.1) rejecting messages containing > 8-bit data (typically, an 8-bit apostrophe character) with the following > error: > > The following message contains 8-bit content, but does not have the > required MIME headers for 8-bit data transport. > > The MIME headers of such messages look like this: > > MIME-Version: 1.0 > Content-Type: text/plain > Content-Disposition: inline > Content-Transfer-Encoding: binary > > Note that the content-transfer-encoding is specified as 'binary', not > 8bit. From rfc2045, sec 2.9: > > "Binary data" refers to data where any sequence of octets whatsoever > is allowed. > > My interpretation of the RFC is that 'binary' content transfer encoding > should allow 8-bit characters in the body -- is this incorrect, or is > Courier rejecting these messages erroneously? > From section 6.2 of the same RFC: Mail transport for unencoded 8bit data is defined in RFC 1652. As of the initial publication of this document, there are no standardized Internet mail transports for which it is legitimate to include unencoded binary data in mail bodies. Thus there are no circumstances in which the "binary" Content-Transfer-Encoding is actually valid in Internet mail. However, in the event that binary mail transport becomes a reality in Internet mail, or when MIME is used in conjunction with any other binary-capable mail transport mechanism, binary bodies must be labelled as such using this mechanism.
However, for future compatibility, it would seem sensible for courier to allow these to pass without modification... -- Bill Michell [EMAIL PROTECTED] (home) _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
