On Wed, Aug 03, 2016 at 12:15:43PM -0500, Derek Martin wrote:
> [snip]
>
> So long as Mutt retains the original message, the fact that it could
> not write the message to Fcc is not particularly problematic.  It's
> already been pointed out in this thread that you DO have a local
> copy...  The file was saved to disk by your editor.  This means that
> before Mutt gives up on saving the message, it can offer you any
> number of options for solving the problem of being unable to write it
> to Fcc.  Also already in this thread, several of those options have
> been enumerated, but two that were not included:

But that's only true as long as the computer doesn't crash (mutt
stores mails in /tmp which is either a tmpfs or emptied on
reboot).

I admit the current situation is not perfect, but at least I
won't lose the message no matter what happens once I've pressed
send. Any change of this behavior which might result in lost
messages is something we should really avoid.

Regards
Simon
-- 
+ privacy is necessary
+ using gnupg http://gnupg.org
+ public key id: 0x92FEFDB7E44C32F9

Attachment: signature.asc
Description: PGP signature

Reply via email to