order of sending mail and saving to fcc

[Felix Finch]

On 20190610, Ben Boeckel wrote:
>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.)

Cat could hit 'q' and then you will have neither Fcc nor send copy.

>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.

Of course this is what I meant.  And when ^C and ^\ do nothing, I consider it
time to kill the tmux session / pane.  I suppose I could open a new terminal
session, in tmux (because tmux is still responding), and killall mutt, but the
distinction is insignificant.

>> 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!

If it is paranoid to consider the ramifications of a change, then the
implementors of said change were also paranoid.

Please be less snarky and more serious.  You do your arguments no favors.

-- 
            ... _._. ._ ._. . _._. ._. ___ .__ ._. . .__. ._ .. ._.
     Felix Finch: scarecrow repairman & wood chipper / felix at crowfix.com
  GPG = E987 4493 C860 246C 3B1E  6477 7838 76E9 182E 8151 ITAR license #4933
I've found a solution to Fermat's Last Theorem but I see I've run out of room o