Bug 186524

Summary:	reply selects wrong identity for folder
Product:	[Applications] kmail2	Reporter:	Peter Lewis <peterl>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED FIXED
Severity:	normal	CC:	panfaust
Priority:	NOR	Keywords:	triaged
Version:	4.11.5
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Peter Lewis 2009-03-08 10:59:10 UTC

Version:           1.10.3 (using KDE 4.1.3)
OS:                Linux
Installed from:    SuSE RPMs

This is a reversion to a prior behaviour that was corrected several years ago (it was deemed a bug then).

Incoming emails are filtered into folders according to their to address and their from address. The folders that they are sorted into have different identities assigned to them.

When a new mail is created the appropriate identity for the folder is used for the mail. When a reply is created the first identity in my list of identities that has the same TO address as the mail that is being replied to is used.

The identities are sorted alphabetically by identity name so "children" is before "family" which is before "personal". Correspondents will use the same TO address for all these mail groups.

KMail will use the "children" identity to reply to emails that have been filtered into the "personal" folder unless  the "children" identity is renamed to "z-children". In that case the "family" identity is used. When that is renamed to "z-family" the "personal" identity is used, as desired.

The solution applied last time was to use the identity assigned to the folder that held the mail for which the reply was being generated, unless "use default identity" was selected for the folder. In that case the reply identity was selected according to the TO address.

As the behaviour has reverted to a previous "buggy" state, I think that this is a bug.

Comment 1 José Manuel Santamaría Lema 2009-03-15 20:37:00 UTC

I'm using kmail 1.11.1, KDE 4.2.1 installed from debian experimental packages:
$ apt-show-versions kdepim
kdepim/experimental uptodate 4:4.2.1-1

I can reproduce the bug, not exactly in the same way: for me identities are not allways sorted alphabetically, sometimes for me the default identity is at top, and the other identities are appended under the default identity alphabetically. When I reply a message, as Peter says above, the identity used is the first in the list of identities that has the same TO address as the mail that is being replied to is used. I can change this behavior renaming identities and/or changing default identity, but the identities which I assigned to folders with "Right click on folder -> Properties" seems to be ignored.

Comment 2 Laurent Montel 2015-04-12 10:08:49 UTC

Thank you for taking the time to file a bug report.

KMail2 was released in 2011, and the entire code base went through significant changes. We are currently in the process of porting to Qt5 and KF5. It is unlikely that these bugs are still valid in KMail2.

We welcome you to try out KMail 2 with the KDE 4.14 release and give your feedback.

Comment 3 Peter Lewis 2015-04-12 18:59:26 UTC

I am (still) using Kmail with the 4.11.5 version from openSuSE 13.1.
We still have the behaviour that a new mail from a folder (highlight folder, press <ctrl>n) will use the identity assigned to that folder but when replying to a message in the same folder (select message, press r) will use the default identity.

The only change is that now all replies use the default identity.

As I use my identities to apply suitable signatures for different addressees this is a bit of a pain. Quite frankly I have just got used to the behaviour and select the appropriate identity myself. It is not a show-stopper just a nice feature missed.

Comment 4 Denis Kurz 2016-09-24 18:08:07 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 Peter Lewis 2016-09-25 08:15:45 UTC

Using KDE 4.14 this bug is no longer present.