Bug 325299

In Kmail settings (Configurations -> Configure Kmail -> Compositor -> Character set encoding) the user can list the character encoding preferences that kmail will use when sending the email. In theory the first charset that can acommodate all letters in the message will be used.

It seems that this settings are not followed for message headers. When using Kmail in a coporate environment where most of the people use MS Outlook/MS Exchange every Kmail sent message arrives for them incomprehensible. The only way to send them a correctly encoded mail is to make sure that there are no non-ascii chars in the heardes. That means manually retyping every email address to strip people names and the subject line to remove non-ascii characters. It is also very time consuming and tedious for discussion threads.

By looking at the message source one can see that in some places that encoding are changed to teh desired (ISO-8859-1, for instance) but in the same message it also includes utf-8 encoding. This mixing of encodings is not respecting the settings definitions and it causes other email clientes to incorrectly display the charset encoding.




Reproducible: Always

Steps to Reproduce:
1. Go to Settings -> Configure Kmail -> Composer -> Character encoding . Remove all items from the list and add only "ISO-8859-1". Push Apply and then Close.
2. Click on new email to start a new message.
3. On the "TO:" field type "Ação" (that's A &ccedil; &atilde; o) <youraddress@example.com>
4. On the "Subject field" type "Açaí" (That's A &ccedil; a &iacute;)
5. On the message body, type anything, but include a few non-ascii chars, like: "Sequência" (&ecirc;)
6. In the Sent folder, click on the just sent email and the Manu "view->view source"
7. See that there should be only ISO-8859-1 tags but there are also UTF-8 tags.
Actual Results:  
From: My Name <my.name@example.com>
To: =?ISO-8859-1?Q?A=E7=E3o?= <my.name@example.com>
Subject: =?UTF-8?B?QcOnYcOt?=
Date: Wed, 25 Sep 2013 10:46:37 -0300
Message-ID: <4109830.nKvFdzYvjl@hostname>
X-KMail-Identity: 243885538
Disposition-Notification-To: My Identity <my.name@example.com>
User-Agent: KMail/4.10.5 (Linux/3.8.0-30-generic; KDE/4.10.5; x86_64; ; )
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"

Sequ=EAncia

Expected Results:  
From: My Name <my.name@example.com>
To: =?ISO-8859-1?Q?A=E7=E3o?= <my.name@example.com>
Subject: =?ISO-8859-1?Q?a=E7a=ED?= 
Date: Wed, 25 Sep 2013 10:46:37 -0300
Message-ID: <4109830.nKvFdzYvjl@hostname>
X-KMail-Identity: 243885538
Disposition-Notification-To: My Identity <my.name@example.com>
User-Agent: KMail/4.10.5 (Linux/3.8.0-30-generic; KDE/4.10.5; x86_64; ; )
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"

Sequ=EAncia

It seems that there is indeed an error and that is the fact that Kmail is not respecting the encoding preferences.

Although kmail itself can handle multiple different encodings, it seems that MS products can't. This annoys MS Outlook and MS Exchange users. Some of them are already questioning that should I use their non-free system, they would not be annoyed.