Bug 343812

Summary:	kmail does not properly quote From field when replying
Product:	[Applications] kmail2	Reporter:	Sandro Knauß <sknauss>
Component:	composer	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	montel
Priority:	NOR
Version:	4.14.2
Target Milestone:	---
Platform:	Debian unstable
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Sandro Knauß 2015-02-05 12:46:18 UTC

Fist you need an default identity, that requires quoting. Like:
"Knauß, Sandro" <knauss@kolabsys.com>

So go to kmail->settings->identity and change the default Identity name to
Knauß, Sandro

than go to an mail that is send at your default identity and reply to it. If you activate view->all fields you see the from address:
Knauß, Sandro <knauss@kolabsys.com>

If you change the identity while having the reply open the address is correctly quoted.
If you replying to other identities it's quoted correctly.
If you create a new mail it is quoted correctly.

There is also a debian bugreport:  https://bugs.debian.org/730048

Reproducible: Always

Comment 1 Sandro Knauß 2015-02-05 12:48:14 UTC

I can confirm this with current debian packages.

Comment 2 Laurent Montel 2015-02-05 13:08:35 UTC

So for you :     Knauß, Sandro <knauss@kolabsys.com> is not correct

you want as "Knauß, Sandro" <knauss@kolabsys.com>
am I right ?

Comment 3 Sandro Knauß 2015-02-05 13:17:44 UTC

Jepp exactly the expected output in the from field should be
"Knauß, Sandro" <knauss@kolabsys.com>

Comment 4 Denis Kurz 2017-06-23 19:57:44 UTC

This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks (5.x). Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the oportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it.

Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.

Comment 5 Denis Kurz 2018-01-31 16:50:47 UTC

Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12, preferably more recent), please open a new one unless it already exists. Thank you for all your input.