Tickets :: [#2190] Message charset doesn't match headers for Cyrillic

Summary	Message charset doesn't match headers for Cyrillic
Queue	IMP
Queue Version	4.0.3
Type	Bug
State	Not A Bug
Priority	2. Medium
Owners
Requester	dfurman (at) cloud9 (dot) net
Created	06/28/2005 (7389 days ago)
Due
Updated	06/30/2005 (7387 days ago)
Assigned
Resolved	06/28/2005 (7389 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

06/30/2005 11:52:50 PM	dfurman (at) cloud9 (dot) net	Comment #3	Reply to this comment
Installing the iconv extension (or possibly the utf8locale-without-swidth-040319 package for FreeBSD) resolved this. Thanks for the help.

06/28/2005 08:01:27 AM	Jan Schneider	Comment #2 State ⇒ Not A Bug	Reply to this comment
I can't reproduce this with the latest released versions. Whether I choose the windows or the koi charset in the compose view, the message is sent correctly. Maybe you don't have the mbstring or iconv extensions installed?

06/28/2005 01:07:43 AM	dfurman (at) cloud9 (dot) net	Comment #1 State ⇒ Unconfirmed Priority ⇒ 2. Medium Type ⇒ Bug Summary ⇒ Message charset doesn't match headers for Cyrillic Queue ⇒ IMP New Attachment: Cyrillic test.txt	Reply to this comment
This is the same issue as mentioned in ~~ticket 2021~~, however I don't believe it is resolved as of 4.0.3: IMP H3 (4.0.3) Final. A message composed with the KOI8-R charset selected in the charset dropdown of the message composition window is actually sent using Windows-1251 charset. A sample message is attached. KOI8-R is indeed the standard charset for Cyrillic email. Even though using Windows-1251 is often an issue in itself for recipients, it wouldn't be too bad if the Content-Type header said so. But instead it has KOI8-R, which misleads MUAs into using an incorrect charset by default when displaying the message.