Bug 323948 - Reply doesn't select identity to use from email being replied to
Summary: Reply doesn't select identity to use from email being replied to
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: composer (show other bugs)
Version: 4.10.5
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-08-23 22:47 UTC by Volker Kuhlmann
Modified: 2017-01-07 22:48 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Volker Kuhlmann 2013-08-23 22:47:39 UTC
Reply to an email does not select the correct identity to use for the reply. It always uses the default identity, but it should use the identity matching my email adddress in the email I'm replying to.


Reproducible: Always

Steps to Reproduce:
1. Click reply on an email sent to one of your identities that is NOT your default one.
2.
3.
Actual Results:  
The reply has the default identity selected.

Expected Results:  
Reply uses the same identity as the email being replied to! This is a regression from kmail 1.

Matching for identity selection should be made on email address only - not on other parts like name, that can change, especially when replying to an older email.
Comment 1 GASPARD "Koshie" Kévin 2013-12-16 15:24:12 UTC
Hello,

I have the same problem on KMail  (4.11.3) too and I was expecting to have the identity 'A' when a e-mail is for 'A' and I'm clicking on reply. And 'B' when the e-mail is for 'B'.

Cordially, Koshie
Comment 2 Denis Kurz 2016-09-24 17:58:54 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 3 Denis Kurz 2017-01-07 22:48:32 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.