My customer receives daily mailings from an advisor, but receives
corrupted characters in the message.

The character set being used is iso-8859-1

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"

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:
&#8211

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 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?

Any insight appreciated.

Owen.

-------------------------------------------------------------------------
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

Reply via email to