GNOME Bugzilla – Bug 713533
Deal with draft after user changes From
Last modified: 2017-12-04 01:05:54 UTC
---- Reported by eric@yorba.org 2013-08-08 17:50:00 -0700 ---- Original Redmine bug id: 7321 Original URL: http://redmine.yorba.org/issues/7321 Searchable id: yorba-bug-7321 Original author: Eric Gregory Original description: When the user changes the From: field in the composer, Geary needs to handle the draft situation properly. Currently, it simply makes the "Save Draft" button sensitive or insensitive depending on whether the account has a draft folder, but there's a couple more things that need doing: * Should the existing draft be deleted? * When the mail is sent, which draft(s) should be deleted? Related issues: related to geary - Feature #3769: Save to Drafts folder (Fixed) ---- Additional Comments From geary-maint@gnome.bugs 2013-09-23 14:38:00 -0700 ---- ### History #### #1 Updated by Eric Gregory 3 months ago So I tested this one out in Apple Mail, and the result is actually quite surprising. If you change the From address, the draft is NOT moved; it remains in whatever account's [Imap]/Drafts folder created the message in the first place. All subsequent edits continue to affect the original account's draft folder. When the message is sent, it's of course removed from that folder as well. The special Drafts folder in the Apple Mail UI reflects this convention as well. #### #2 Updated by Jim Nelson about 1 month ago * **Target version** changed from _0.4.0_ to _0.5.0_ --- Bug imported by chaz@yorba.org 2013-11-21 20:21 UTC --- This bug was previously known as _bug_ 7321 at http://redmine.yorba.org/show_bug.cgi?id=7321 Unknown milestone "unknown in product geary. Setting to default milestone for this product, "---". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one. Resolution set on an open status. Dropping resolution
I think this is a criminal bug. Geary creates too much draft automatically and still save it even when i sent the right email. Devs please fix it!
The situation has changed greatly in 0.12 - currently the only thing left to address is Bug 778976, so resolving this as obsolete.