Bug 301449

Summary: Replying to a mail sent by another identity in the same kmail copy leads to replying to the current identity itself
Product: [Applications] kmail2 Reporter: Tamás Németh <nt1277>
Component: composerAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED UNMAINTAINED    
Severity: major    
Priority: NOR    
Version: 4.8.3   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Tamás Németh 2012-06-08 14:28:32 UTC 
I have two identities (email boxes) in my kmail installataion. One is my workingplace address and the other is my gmail address both of them are configured as disconnected IMAP. I sent a test mail from my workingplace address to my gmail address. The I went to my gmail folders, downloaded the message sent previusly from my other address, and started to reply to it. To the greatest surprise, kmail wanted to send the reply mail to my gmail address, not to the one it was sent from. I committed this test in the reverse layout and the same thing happened: If kmail realizes that the sender is me then it unconditionally wants to replace the recipient address with that of my current identiy upon replying.

Reproducible: Always

Steps to Reproduce:
1. Create two identities/mailboxes in kmail
2. Send a test mail from one to another
3. Go to the another account
4. Try to reply to that mail from your other address
Actual Results:  
kmail sends the reply to the address of your current identity, not to yout original sender address.

Expected Results:  
Reply mails should probably always sent to the sender of the mail they are sent to as a reply.
Comment 1 Denis Kurz 2016-09-24 18:01:30 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 2 Denis Kurz 2017-01-07 21:44:57 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.