---- Reported by adam@yorba.org 2012-04-26 06:35:00 -0700 ----

Original Redmine bug id: 5129
Original URL: http://redmine.yorba.org/issues/5129
Searchable id: yorba-bug-5129
Original author: Adam Dingle
Original description:

Michael Spencer wrote on the mailing list:

One feature I cannot live without is undo send (as seen in gmail). I've caught
some catastrophically stupid mistakes thanks to it, and it has saved me quite
a bit of embarrassment.

I imagine it would be fairly simple to present the user a view of the final
formatted email after they click send while the app waits 30 seconds before
actually sending it.

Related issues:
related to geary - Feature #4570: split Geary engine into separate shared
library or backgr... (Open)
related to geary - Feature #6461: Scheduled send (Open)



---- Additional Comments From geary-maint@gnome.bugs 2012-09-20 10:47:00 -0700 ----

### History

####

#1

Updated by Timo Kluck about 1 year ago

I've been thinking about this feature. The hardest thing to overcome is this:
the nice thing about gmail's undo functionality is that the message has
actually been sent to the server when it presents the Undo link. That means
that if the user logs out, loses his connection or shuts down his computer,
the message will still be sent after the time-out.

I cannot think of a way how Geary can replicate that behaviour. It would be
really annoying if you want to shut down your computer to have to wait for the
time-out before the message is sent. One could add a "skip time-out" button
next to the "undo" button, but it would look cumbersome. Besides, many people
will make clicking such a button part of their muscle-memory, rendering the
undo functionality useless.

Does anyone else have ideas about this?

####

#2

Updated by Eric Gregory about 1 year ago

Gmail's "undo" time period is very short, ~10 seconds. It's worth considering,
but to me it seems like a corner case that the user would quit Geary or shut
down their computer in the next 10 seconds.

####

#3

Updated by Jim Nelson about 1 year ago

There's also this: http://developer.gnome.org/gtk3/3.3/GtkApplication.html
#gtk-application-inhibit

Although I've not played with this, it looks like Geary could inhibit
logout/shutdown/suspend for a brief period of time to ensure the message is
sent in time (and likewise allowing for the user to undo the send). The amount
of time Geary inhibits these activities should be brief in any case.

As far as the user simply exiting Geary, that event could flush the outbox and
force messages to be sent in the background. The window disappears but for a
few moments the process remains running as it cleans up the queue. If Geary is
broken out into a separate daemon (#4570) then even this isn't a problem.



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

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

Unknown Component 
   Using default product and component set in Parameters 
Unknown version " in product geary. 
   Setting version to "!unspecified".
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