Press R while reading a message, or click the Reply button at top of kmail/kontact or right click in the message window and select Reply, You will occasionally see your own address in the TO field. This happens even more frequently if Your name matches the original sender's name (such as when I send to my work account from my gmail account, both have the same name, but different email addresses. However, I have seen this when the names differ wildly. Reply-to-Author gets it right always, but simple Reply will some times get it wrong. Reproducible: Sometimes Steps to Reproduce: 1. Send a mail to yourself from a different Email Account but the same user name 2. Reply to with the R key in Kmail 3. Play with it, because it doesn't happen all the time. Actual Results: R/Reply/Context-Reply should reply to Sender (assuming a mailing list is not involved). Expected Results: Sometimes the Reply address is set up to go to the account from which you are replying. Image might help: https://dl.dropboxusercontent.com/u/35567349/320581-4.png The image shows: I'm reading a gmail mailbox. Reply window is setting on top of the message in the Reading window. It came from screenio.com. To Gmail.com. R was pressed to compose a reply. Reply should have been set up to go to Screenio.com but in fact it was set up to go to gmail.com
This always happens when a sender has sent the email to a group email address. Message sent: From - person@company.com To - group@company.com When I reply (not reply all) the response is sent: To - group@company.com From - me@company.com This may also be affecting responses to calender invites. For some invites I become the organiser when I accept the invite. I think that may be because the acceptance is automatically sent to the wrong address. My calender (and everyone else who receives the acceptance) uses the last sender as the organiser.
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.
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.