* Francesco Ariis <fa...@ariis.it> [2019-06-04 19:52 +0200]: > Hello Grant, > > On Tue, Jun 04, 2019 at 04:46:50PM -0000, Grant Edwards wrote: > > On 2019-06-04, Jack M <j...@forallx.net> wrote: > > > > > The reason (or *a* reason) is that the old way led to the following > > > situation: Fcc first, then try to send, something weird happens, but > > > the user has no idea whether the mail was actually sent or not > > > > How could the user not know? If the send fails, mutt prints an error > > message and stays on the message compose screen. It's pretty > > obvious... > > I have the bad habit of pressing 'q' (exit to menu) after sending. > Also terminal corruption or similar events: you can't be sure whether > the message was actually sent.
With the new order this behaviour might lead to a sent mail without a local copy. If you miss the failure to send, you might as well miss the failure to fcc. HAND Nicolas