Bug 339874 - Regression: editing message in outbox creates a copy
Summary: Regression: editing message in outbox creates a copy
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: commands and actions (show other bugs)
Version: 4.12.5
Platform: FreeBSD Ports FreeBSD
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-10-11 11:58 UTC by John Baldwin
Modified: 2017-01-07 21:52 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description John Baldwin 2014-10-11 11:58:48 UTC
I'm not sure at which version this changed, but I have long been used to being able to edit a pending message (queued via "Send Later") by using "Edit Message" on a box in the outbox.  Once I had finished editing the message, I used "Send Later" to save it.  The result was that the message in the outbox was edited in place.  Now when the edited message is saved via "Send Later", this queues the edited copy of the message as a new message in the outbox alongside of the original message.  This is quite astonishing compared to previous behavior, especially since the primary reason I use "Send Later" is that I can edit pending messages before finally sending them.

Reproducible: Always

Steps to Reproduce:
1. Compose a message and use "Send Later" to save it in outbox.
2. Use "Edit Message" (e.g. via 't') to edit the message in the outbox and save it via "Send Later"
3. Check the outbox and find both copies of the message (original and edited)

Actual Results:  
Both copies of the message in the outbox.

Expected Results:  
Only the edited copy of the message in the outbox.
Comment 1 Denis Kurz 2016-09-24 18:10:53 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:52:42 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.