Bug 160357 - Some e-mail addresses with umlauts are broken on reply/reply-all
Summary: Some e-mail addresses with umlauts are broken on reply/reply-all
Status: RESOLVED DUPLICATE of bug 126025
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: 1.9.50
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
Depends on:
Reported: 2008-04-04 13:00 UTC by Luka Renko
Modified: 2008-04-14 00:42 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Note You need to log in before you can comment on or make changes to this bug.
Description Luka Renko 2008-04-04 13:00:14 UTC
Version:           1.9.50 (using Devel)
Installed from:    Compiled sources
OS:                Linux

I am using KMail from SVN trunk (today's build), but the same problem is also reproducible in KDE 3.5.9 (using Kubuntu Hardy packages).

I receive some e-mails from people that have German umlauts in their descriptive name. Everything is fine when I read such e-mails, but when I try to reply on such e-mail, I get the e-mail address split to two parts (in two To/Cc fields). For example:

- original e-mail address: Lüre, Miki <lure.miki@miki.com>

will get split into two To/Cc fields:
- first: Lüre
- second: Miki <lure.miki@miki.com>

Similarly, if I just click on e-mail address in preview window, I get new message (compose) window, but the e-mail address in To field is just Miki <lure.miki@miki.com>

When I have looked at message source, I can see that e-mail address is encoded strangely:
=?iso-8859-1?Q?L=FCre=2C_Miki?= <lure.miki@miki.com>

Note: I have just put some names in example to make in anonymous. If I developer would like get full example of such e-mail, please drop me an e-mail or ping Lure in #kontact channel (I am there from time to time).

It seems to me the main problem is that this e-mail description is not put in quotes ("") when presented to the user and then when reply is done, umlauts confuse KMail.
Comment 1 Thomas McGuire 2008-04-14 00:42:53 UTC

*** This bug has been marked as a duplicate of 126025 ***