#265:

#265:

> Suppose a user wants to fcc to a file (e.g., /a/b/c) but accidentally
> typed a = before the path name. Mutt will fail to find the =/a/b/c
> folder, display the error message and beep, but immediately erase the
> error message; the mail will be sent even though the fcc failed. (The
> same can be accomplished by accidentally mistyping other parts of the
> path name.) On local systems where screen update is quick, the user
> might not notice the error message at all.
>
> The problem with this behaviour is that the user might have no chance
> to read the error message if the screen update is quick enough; as a
> result (s)he might not notice that the fcc failed.
>
> A related thing (probably can't be classified as a problem) is that if
> fcc fails, the user probably don't want to send the mail out because
> if fcc is requested (s)he probably very much want to keep a copy of
> the sent mail.

Try the following patch.  We keep track of whether or not the fcc
failed with a local var `fcc_error' and perform the same behavior as
if the actual send of the message failed (without really sending)
when the FCC fails, thus giving the user a chance to correct the
error.