Bug 310141

Summary:	When responding to a message, "From" address gets truncatet on non-ASCII characters
Product:	[Applications] kmail2	Reporter:	Marc González Majoral <gonssal>
Component:	composer	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED FIXED
Severity:	minor	CC:	montel
Priority:	NOR
Version:	4.9.3
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Marc González Majoral 2012-11-15 11:33:25 UTC

When you choose to respond a message and composer opens, if the "From" field gets autopopulated with an address that contains non-ASCII characters, it gets truncated, or at least if its an "á".

The domain I'm using is marcgonzález.com and its the default account when sending. When i choose to respond a message, address appears as "xxx@marcgonz". The first time I responded to a message I didn't notice it was truncated so the receiving server said the address was not valid. Took some minutes to realize what the problem was.

I understand that the domain is really "xn--marcgonzlez-r7a.com", but it should be converted transparently to the user, like for example web browsers do. The domains apparently aren't being converted anywhere in Kmail (for example I have to configure the accounts as xn--marcgonzlez-r7a.com or they won't work), but I don't feel that's a bug, rather than a lack of a basic feature.

Reproducible: Always

Steps to Reproduce:
1. Receive a message
2. Respond to that message using a default sending account with the domain containing non-ASCII characters (á in my case)
Actual Results:  
Address' domain gets truncated

Expected Results:  
Domain shouldn't get truncated

Comment 1 Laurent Montel 2012-11-15 12:19:34 UTC

I confirm that it's converted...
not good.
Will look at it.

Comment 2 Laurent Montel 2012-11-27 12:45:58 UTC

I need an account from non ascii name to test all kmail...

Comment 3 Marc González Majoral 2012-11-28 16:56:04 UTC

Sent you e-mail with credentials etc.

Comment 4 Denis Kurz 2016-09-24 18:06:52 UTC

This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.

Comment 5 Marc González Majoral 2016-09-26 11:41:18 UTC

This indeed seems fixed.