Bug 288105

Summary: Untainted drafts & outbox messages get lost when closing the composer
Product: [Applications] kmail2 Reporter: Bernd Oliver Sünderhauf <pancho.s>
Component: composerAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED FIXED    
Severity: major CC: cschwan, montel
Priority: NOR    
Version: 4.7   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In: 4.7.4

Description Bernd Oliver Sünderhauf 2011-12-03 01:53:08 UTC 
Version:           4.7 (using KDE 4.7.3) 
OS:                Linux

When closing the composer, I'm usually asked whether I want to save the message as a draft, unless the new message was left untainted.

However, this concept doesn't work out well with drafts and outbox messages. Here, the question whether the message has been tainted in the composer, is simply no good criterion.
Often enough, one just takes a look at the draft. Now if then the composer window is closed without any change, the draft simply disappears into the abyss, instead of being kept unchanged.

Also the options in the dialog box are irritating for already existing drafts and outbox messages. IMHO, the question should not be "Save as draft" vs. "Discard", but rather "Save" vs. "Discard changes".

Reproducible: Always



Expected Results:
Comment 1 Laurent Montel 2011-12-08 08:57:30 UTC 
Now when we edit draft without change data we will allow to save in draft.
So we don't lose data.
Comment 2 Christopher Schwan 2011-12-09 11:29:15 UTC 
I can confirm this behavior with KDE 4.7.3 on Gentoo. I did the following:

1. Create new mail with Ctrl+N
2. Write any text
3. Alt+F4 to close the composer and choose "Save as Draft"

So far everything is fine, but if I

4. reopen mail again by right-clicking to it and choosing "Edit Message"
5. do not change text
6. Press Alt+F4 again to exit composer

the e-mail is no longer present in any folder.
Comment 3 Laurent Montel 2011-12-09 14:31:46 UTC 
As I wrote comment#2 is fixed in 4.7.4/master
Comment 4 Christopher Schwan 2011-12-12 10:36:26 UTC 
(In reply to comment #3)
> As I wrote comment#2 is fixed in 4.7.4/master

OK, can confirm this. Someone with permission should close this bug as RESOLVED FIXED.