Óscar Pereira wrote: > One of the accounts I use mutt with is setup with offlineimap to > download the email, and msmtp to send it. Yesterday, the smtp server > I use with that account (gmail's smtp) was unavailable during the > afternoon. However, when I sent an email from mutt, neither mutt nor > msmtp reported an error. In fact, mutt displayed the familiar "Mail > sent" message in the lower left corner. And what's worse, the mail I > was just composing was *gone*! Not sent to the recipient, but also > not stored anywhere locally. This scenario was reproducible, and the > behaviour was always the same.
Do you have $sendmail_wait set to < 0? Looking at the source, if the value is < 0, mutt will return an EX_OK right away, resulting in the "Mail sent" message. The docs say a value other than 0 will put the output in a temporary file and you will be informed in the event of an error. But the source shows that's only for $sendmail_wait > 0 and for the case that the process finishes while mutt is still waiting for it. For the (default) case where $sendmail_wait == 0, it should be pretty bullet proof. I myself have used msmtp for a while and it _has_ returned an error message in the case where the mail could not be sent. -Kevin
signature.asc
Description: Digital signature
