| 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 | 6/28/05 (7669 days ago) |
| Due | |
| Updated | 6/30/05 (7667 days ago) |
| Assigned | |
| Resolved | 6/28/05 (7669 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
utf8locale-without-swidth-040319 package for FreeBSD) resolved this.
Thanks for the help.
State ⇒ Not A Bug
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?
State ⇒ Unconfirmed
Priority ⇒ 2. Medium
Type ⇒ Bug
Summary ⇒ Message charset doesn't match headers for Cyrillic
Queue ⇒ IMP
New Attachment: Cyrillic test.txt
ticket 2021, however I don'tbelieve 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.