Powered by phpBB 2.0.11 © 2001 phpBB Group
QUOTE:
From: ihanitse@claymountain.com
Message-ID:
MIME-Version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 8bit
Date: Thu, 20 Jan 2005 09:34:40 +0200
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: PHP
X-MimeOLE: Produced By phpBB2
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: BASE64
VGVydmVoZHlzIG1vcw0KDQpTYWF0IHTDpG3DpG4gc8OkaGvDtnBvc3RpbiBrb3NrYSBvbGV0ICh0
YWkgam9rdSBqb2thIHbDpGl0dMOkw6Qgb2xldmFuc2Egc2luw6QpIHB5eXTDpG5
From: ihanitse@claymountain.com
Message-ID:
MIME-Version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 8bit
Date: Thu, 20 Jan 2005 09:34:40 +0200
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: PHP
X-MimeOLE: Produced By phpBB2
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: BASE64
VGVydmVoZHlzIG1vcw0KDQpTYWF0IHTDpG3DpG4gc8OkaGvDtnBvc3RpbiBrb3NrYSBvbGV0ICh0
YWkgam9rdSBqb2thIHbDpGl0dMOkw6Qgb2xldmFuc2Egc2luw6QpIHB5eXTDpG5
I do not know if it is permissible to have two Content-Types set inside header of the message. But what I do know is what some Outlook Express clients and at least some Evolution clients do when they encounter this kind of message. They discard the first Content-type and go for the second one.
Also some Outlook Express clients and at least some Thunderbird clients use the first Content-type and discard the latter content-type thus showing base64 encoded trash.
What the phpBB 2 coder probably had intended was:
- Please decode the BASE64 encoding. It is done in UTF-8 encoding.
- After decoding show the contents as it was encoded in ISO-8859-1.
When we have content that contains letters in ISO-8859-1 characters and they are displayed as UTF-8 characters in the best case, we have no winners. Just losers. This sucks major time.