Owen O' Shaughnessy wrote: > My customer receives daily mailings from an advisor, but receives > corrupted characters in the message. > > The character set being used is iso-8859-1 > ... > The difference is certain characters in the character set are rendered > differently in the same MUA, an example would be the dash - character, > what is in the courier message source for this is: > =E2=80=93 > and what is in the exchange server message source is: > – > > The message received through exchange renders a dash, whilst the > message received through courier receives something looking like a > with a hat symbol above it, a euro symbol, and a quotes symbol.
The MUA is doing the right thing when it displays the odd symbols. Those three bytes are UTF-8 (I believe). ISO-8859-1 isn't a multi-byte encoding, so each byte is interpreted and rendered as an individual character. I'm not sure if Courier will add an encoding specification to a Content-type header if it receives a message that doesn't have one, so I'm not sure if it's more likely that the sender is leaving out the fact that the message is UTF-8, or if the sender is specifying the wrong encoding. Either way, the sender needs to specify the correct encoding in order for your customer to view a message that looks correct. > When the message is received by courier it is sent using content > transfer encoding "7 bit". > When the message is received by a Microsoft exchange server, it is > sent using content transfer encoding "quoted-printable" > Additionally, "=E2=80=93" is quoted-printable text. If the content-type header says otherwise, that is also wrong. > The only difference in the two mails is that the exchange server has > negotiated (?) "quoted-printable" content transfer encoding while the > courier server has used "7 bit". > > What determines the content transfer encoding? And is this problem due > to courier not supporting a better transfer encoding and having to > negotiate a lesser encoding scheme which corrupts characters in the > message? or is this down to something in the sending application? > Courier fully supports 8BITMIME transfers. It should be able to accept anything that's standards-compliant. You could try setting "opt BOFHBADMIME=accept" in the bofh file and see if the message is rewritten differently. I'm not too firm on Courier's MIME rewriting rules. ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
