On 2016-07-29 12:35:31 -0500, Derek Martin wrote: > On Thu, Jul 28, 2016 at 11:12:48AM +0200, Vincent Lefevre wrote: > > I think that the right solution would be to prompt the user for > > retrying. The user should have the choice between: > > > > 1. Retry (default). > > 2. Choose a different folder where the message could be saved, and > > retry on it. > > 3. Some alternative solution to avoid losing the message (in case > > the user had not put himself in Cc/Bcc)? (e.g. send the message > > to some address if possible) > > 4. Abort (i.e. the message is not saved at all). > > This makes sense to me. I'd be somewhat inclined to skip option #3 > but it does provide some recourse if the user's configured Fcc > location is unwritable, and the user lacks sufficient priviledges to > do anything about that.
I'm wondering... At this point, a copy of the message is still somewhere on the file system (under $tmpdir). So, in case of abort (option #4), I'd say that the message should not be removed from $tmpdir, so that the user could do something about it, such as, depending on the context: * leave it in $tmpdir until the problem is resolved; * try to mail it to some of his addresses; * some scp; * upload it somewhere, possibly after encryption; * view the message and take a photo; * etc. > Mostly useful in a University setting or similar shared server > environment. Yes, and this may include the $HOME of a VPS (not necessarily shared, but non-local). > Trouble is, the user needs to remember the message got saved > elsewhere and then do something about that later. He can write a note on his smartphone or some piece of paper... -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
