On Mon, Jun 10, 2019 at 08:40:30 -0700, Felix Finch wrote: > As other(s) have mentioned, power failure, cat jumping on keyboard. I > have also had sends hang seemingly forever, and the only way forward > is tokill the tmux session. Then I have no Fcc copy. I can root > around /tmp to find the message, but I shouldn''t have to.
Doe mutt do the right fsync dance for power failure anyways? How would a cat jumping on the keyboard possibly a failure mode *anyone* can *plan* for? (I've had mine swat the power strip switch before which is at least intersecting with other failure modes.) Killing the tmux session seems overkill. You couldn't kill just the pane holding mutt? Tmux being completely unresponsive sounds like either a sendmail or tmux bug. > For me, the difference is that having extra Fcc copies is nowhere near > as bad as not having any. If you're this paranoid, the only real fix is to have your editor save a backup somewhere before handing it off to mutt in the first place anyways. After all, mutt could segfault and lose it before the Fcc! --Ben
