After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 713519 - Discarded drafts moved to Trash on Gmail
Discarded drafts moved to Trash on Gmail
Status: RESOLVED DUPLICATE of bug 726728
Product: geary
Classification: Other
Component: composer
master
Other All
: Normal normal
: ---
Assigned To: Geary Maintainers
Geary Maintainers
Depends on:
Blocks:
 
 
Reported: 2013-08-14 08:12 UTC by Jim Nelson
Modified: 2014-04-10 19:54 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Charles Lindsay 2013-11-21 20:21:19 UTC


---- Reported by jim@yorba.org 2013-08-14 13:12:00 -0700 ----

Original Redmine bug id: 7343
Original URL: http://redmine.yorba.org/issues/7343
Searchable id: yorba-bug-7343
Original author: Jim Nelson
Original description:

When Geary discards a draft (either because the user requested that to happen,
or a saved draft was "replaced" as the user kept typing, or the user sent the
email), the draft winds up in the Trash on Gmail. Fortunately messages older
than 30 days are removed from the Trash automatically, but some users might
prefer the message is removed entirely.

For Gmail, it appears the only way to ensure a draft is really deleted is to
move it to the Trash and then remove it from the Trash itself.



--- Bug imported by chaz@yorba.org 2013-11-21 20:21 UTC  ---

This bug was previously known as _bug_ 7343 at http://redmine.yorba.org/show_bug.cgi?id=7343

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 

Comment 1 Jakob Unterwurzacher 2014-04-02 20:33:00 UTC
Duplicate of bug #726728
Comment 2 Jim Nelson 2014-04-10 19:54:15 UTC

*** This bug has been marked as a duplicate of bug 726728 ***