Bug 71031

Version:            (using KDE KDE 3.1.4)
Installed from:    Debian testing/unstable Packages

Yo,

I'd like to be able to change the encoding of an attachment - I recently sent somebody a text file once as KOI8-T and as UTF-8 - but in the outgoing email, both attachments had Content-Type: text/plain; charset=us-ascii (which surprised me - I use de_CH.UTF8 charset).

LANG=POSIX
LC_CTYPE=en_US.UTF-8
LC_NUMERIC="POSIX"
LC_TIME="POSIX"
LC_COLLATE=C
LC_MONETARY="POSIX"
LC_MESSAGES=C
LC_PAPER="POSIX"
LC_NAME="POSIX"
LC_ADDRESS="POSIX"
LC_TELEPHONE="POSIX"
LC_MEASUREMENT="POSIX"
LC_IDENTIFICATION="POSIX"

Sample mail:

Return-Path: ...
From: Adrian 'Dagurashibanipal' von Bidder <...>
To: ...
Subject: One, Two, Test
Date: Mon, 22 Dec 2003 13:27:04 +0100
User-Agent: KMail/1.5.4
MIME-Version: 1.0
Content-Type: Multipart/Mixed;
  boundary="Boundary-00=_YMu5/zZ7/7CfPLD"
Message-Id: <200312221327.04314@fortytwo.ch>


--Boundary-00=_YMu5/zZ7/7CfPLD
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Subject: 

Testing, testing
-- 
Vote for me.  You may not agree with me, but at least I understand
what's going on
        -- steevo in news.admin.net-abuse.email

--Boundary-00=_YMu5/zZ7/7CfPLD
Content-Type: text/plain;
  charset="us-ascii";
  name="README.koi8-t"
Content-Transfer-Encoding: base64
Content-Disposition: inline;
	filename="README.koi8-t"

79TNwdrLwTog4s/M2NvJztPU188g0NLFxNPUwdfMxc7O2cgg2sTF09ggwcbP0snazc/XCiAgICAg
ICAgINPPwsnSwczJ09ggwdfUz83B1MnexcvJINPL0snQ1M/NLCDXIM7JyCDQ0snT1dTT1NfVxdQK
CSDPwtPDxc7OwdEgzMXL08nLwSDJIMTP09TB1M/ezs8g0M/bzNnFINfZ08vB2tnXwc7J0S4KCSDx
INDF0snPxMnexdPLySDeyd3VIMbP0tTVzsvJLCDOzyDTycwgzc/JyCDOxSDI18HUwcXULAoJINDP
3NTPzdUgxMHOzsHRIM/UzcHay8EgxM/M1s7BIM3FztEgz9TNwdrB1Nggz9Qg18HbycgKCSDQ0sXU
xc7aycog0M8g0M/Xz8TVIMzFy9PJy8kgOikuCgoJIAkJCQkwNi4wNi4yMDAwCgkJCQkJYXJ0dXIu
cGVudHRpbmVuQHNvbmVyYS5pbmV0LmZpCg==

--Boundary-00=_YMu5/zZ7/7CfPLD
Content-Type: text/english;
  charset="us-ascii";
  name="README.utf8"
Content-Transfer-Encoding: base64
Content-Disposition: inline;
	filename="README.utf8"

0J7RgtC80LDQt9C60LA6INCR0L7Qu9GM0YjQuNC90YHRgtCy0L4g0L/RgNC10LTRgdGC0LDQstC7
0LXQvdC90YvRhSDQt9C00LXRgdGMINCw0YTQvtGA0LjQt9C80L7QsgogICAgICAgICDRgdC+0LHQ
uNGA0LDQu9C40YHRjCDQsNCy0YLQvtC80LDRgtC40YfQtdC60Lgg0YHQutGA0LjQv9GC0L7QvCwg
0LIg0L3QuNGFINC/0YDQuNGB0YPRgtGB0YLQstGD0LXRggoJINC+0LHRgdGG0LXQvdC90LDRjyDQ
u9C10LrRgdC40LrQsCDQuCDQtNC+0YHRgtCw0YLQvtGH0L3QviDQv9C+0YjQu9GL0LUg0LLRi9GB
0LrQsNC30YvQstCw0L3QuNGPLgoJINCvINC/0LXRgNC40L7QtNC40YfQtdGB0LrQuCDRh9C40YnR
gyDRhNC+0YDRgtGD0L3QutC4LCDQvdC+INGB0LjQuyDQvNC+0LjRhSDQvdC1INGF0LLQsNGC0LDQ
tdGCLAoJINC/0L7RjdGC0L7QvNGDINC00LDQvdC90LDRjyDQvtGC0LzQsNC30LrQsCDQtNC+0LvQ
ttC90LAg0LzQtdC90Y8g0L7RgtC80LDQt9Cw0YLRjCDQvtGCINCy0LDRiNC40YUKCSDQv9GA0LXR
gtC10L3Qt9C40Lkg0L/QviDQv9C+0LLQvtC00YMg0LvQtdC60YHQuNC60LggOikuCgoJIAkJCQkw
Ni4wNi4yMDAwCgkJCQkJYXJ0dXIucGVudHRpbmVuQHNvbmVyYS5pbmV0LmZpCg==

--Boundary-00=_YMu5/zZ7/7CfPLD--

====================

The funny bit: when I was sending a similar message, but PGP/MIME signed, both attached files had iso-88591 encoding.

Thanks & greets