mutt writes a message to fcc even if $sendmail exits non-zero. I don't think it should do that as it might yield the false impression that a message was sent (e.g. if it was fcc'd to =sent, albeit not actually being sent).
Hello Martin,
Am 2010-06-02 20:56:00, schrieb martin f krafft:
This was already discused and an earlier bugreport closed...
However I fully aggree with you, because I have some tools for automated
processing and if sendmail can not send but the the messages is saved,
it would be local processed from a script even if the message was not
send... and over and over processed if I retry to send the message.
Such bug is more then only annoying.
Thanks, Greetings and nice Day/Evening
Michelle Konzack
also sprach Michelle Konzack <linux4michelle@tamay-dogan.net> [2010.06.04.2358 +0200]: Do you have a reference?
severity 584264 wishlist retitle 584264 option to write fcc only after sendmail exits successfully tags 584264 upstream forwarded 584264 http://dev.mutt.org/trac/ticket/3420 thanks I found #264973, which was indeed wontfix. The gist is that some people want this behaviour, and some the other behaviour. What a surprise! So I am turning this bug report into a wishlist: It would be nice if mutt grew an option that allowed me to toggle between (in shell pseudo-code): a. fcc && sendmail b. sendmail && fcc The current behaviour is (a.), but some of us would really like to only write a $record of a message if it has actually been sent. Thanks for your consideration.
Am 2010-06-13 20:16:31, schrieb martin f krafft:
Now yes! It is Bug #264973 and was from 2004
Thanks, Greetings and nice Day/Evening
Michelle Konzack
The default behavior was changed in Mutt 1.12.0 to fcc after sending (successfully). Mutt version 1.12.1 added an option $fcc_before_send to control the order.