Version:            (using Devel)
OS:                Linux
Installed from:    Compiled sources

When I reply to an e-mail and supply an attachment, the main body will not have a charset in the header.

The received e-mail has this in the main part:

------------=_1237106374-16227-4391
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable

The one I send will have:

--Boundary-00=_vCRvJgGpKZCcc1S
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

with the content in quoted-printable escaped UTF-8.

The attachment, however, will have for example:

--Boundary-00=_vCRvJgGpKZCcc1S
Content-Type: application/x-shellscript;
  name="createdev"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
	filename="createdev"

as expected...  and my signature:

--Boundary-00=_vCRvJgGpKZCcc1S
Content-Disposition: inline
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit

Correctly UTF-8.


So in short:
Experienced behaviour: the message body has no charset tag, going against all logic and KMail's settings.

Expected behaviour: the message "body" should keep the charset tag as received (if possible) or otherwise attempt to fall back to the first applicable charset (as mentioned in the KMail configuration).