smtpmail-async fails silently

Say you recently changed your SMTP password. You send a message and the log looks like:

Sending...
Mark set [2 times]
Sending via mail...
Sending...done
[mu4e] Message sent

It probably worked right? No way. You never had a chance to enter your new password, so it can not have worked. But, you'll never know until no one replies to you for a few days.

So, async can't ask the interactive questions, clearly, nor can she tell you she timed out waiting for your input.

I'm not sure what's needed here but something.

The async worker could communicate back a failure code to be reported to the user. I'm not sure why it's not doing that already.

Michael Fox [email protected] writes:

Say you recently changed your SMTP password. You send a message and the log looks like:

Sending... Mark set [2 times] Sending via mail... Sending...done [mu4e] Message sent

Here it doesn't mean the message has been sent, mu4e assume you are using a sync smtp, not async.

I'm not sure what's needed here but something.

You have to use a .authinfo.gpg file and a script to allow your backend reading it (offlineimap for me here).

-- Thierry