Bug 271826 - kmail does not handle message encoding properly on replies (base64 encoded multipart message)
Summary: kmail does not handle message encoding properly on replies (base64 encoded mu...
Status: RESOLVED WORKSFORME
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: Git (master)
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2011-04-27 10:40 UTC by Marc Schiffbauer
Modified: 2018-10-27 03:51 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marc Schiffbauer 2011-04-27 10:40:44 UTC
Version:           Git (master) (using KDE 4.6.2) 
OS:                Linux

I just received a multipart mail with following headers:

Content-Type: multipart/alternative;
	boundary="_000_2E0B97FC886742438D4972827280027E32DA419325MAILSERVHwwhl_"

And then with multiparts:

--_000_2E0B97FC886742438D4972827280027E32DA419325MAILSERVHwwhl_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

And:

--_000_2E0B97FC886742438D4972827280027E32DA419325MAILSERVHwwhl_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

When I hit reply, I get garbage instead of german umlauts in the quoted text of the message body:


Am Wednesday, 27. April 2011, 09:30:28 schrieben Sie:
> Marc,
> 
> Beitrag könnt ihr auf das Konto leisten.
> 
> Gruà und bis Samstag.



Reproducible: Always

Steps to Reproduce:
1. Have a multipart, base64 encoded utf8 message in your inbox
2. Hit reply

Actual Results:  
Garbage instead of correct utf8 encoded characters

Expected Results:  
Correct utf8 characters
Comment 1 Thomas McGuire 2011-05-08 19:59:11 UTC
I can not reproduce this. I created a multipart/alternative base64 utf8 message from within KMail, and tried replying to it, which worked fine.
Maybe it only happens to a subset of messages? Please attach your message (you can strip out some of the headers for privacy) to provide a test.
Comment 2 Marc Schiffbauer 2011-05-10 00:49:11 UTC
I just noticed that saving a message to a file (.mbox) seems to be broken, too: The saved file is empty...

I saved the message using mutt then. But when I open the mail saved file in kmail I cannot reply to it (button disabled)

I may sent you that mail via PM if you pretend to delete it afterwards.

-Marc
Comment 3 Thomas McGuire 2011-05-16 13:00:37 UTC
Yes, please send me the mail via PM (simply add the mbox as an attachment to a mail), I'll delete it afterwards.
Comment 4 Marc Schiffbauer 2011-06-30 16:26:38 UTC
Mail sent on 17.05.2011 23:16
Comment 5 Jakub Januszkiewicz 2011-09-18 18:47:36 UTC
Same problem here in KMail 4.7.1, I can provide a number of affected emails if needed.
Comment 6 sabik 2012-02-25 04:48:56 UTC
I seem to be affected by the same problem.

My messages are 8bit-encoded, and the parts are iso-latin-2, but otherwise similar: multipart/alternative outer layer, inner layers text/plain; charset=ISO-8859-2; format=flowed and text/html; charset=ISO-8859-2). When I hit "r" for reply, the text is decoded to utf-8 but then shown in iso-latin-2.

There seems to be some interaction with the "Keep original charset" option, but even when it's off, for encrypted e-mails, the problem still occurs when replying to the whole e-mail - but not when the text is selected (so that only the selected part is quoted).

So the work-around ends up being (a) turning off "Keep original charset" (Settings | Composer | Charset) and (b) selecting the text of encrypted e-mails before hitting "r" for reply.
Comment 7 Martin Koller 2013-02-09 21:42:52 UTC
Please add a testmail here as attachment to be able to reproduce the problem.
(And please check with current 4.10)
Comment 8 Andrew Crouthamel 2018-09-24 02:10:20 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 9 Andrew Crouthamel 2018-10-27 03:51:41 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!