My experiences with Mutt to date: Suggestions for overcoming some issues
boB Stepp
robertvstepp at gmail.com
Sun Feb 14 07:10:41 UTC 2021
On 21/02/13 08:03PM, Sam Kuper wrote:
>On Fri, Feb 12, 2021 at 01:30:04PM +0100, Angel M Alganza wrote:
>> I did the same myself for years and also switched to ssmtp. But I
>> belive ssmtp was discontinued, and now I'm using msmtp:
>>
>> https://marlam.de/msmtp/
>>
>> I couldn't be happier!
>
>A queue script is included with msmtp, so you can have the best of both
>worlds :)
>
>https://git.marlam.de/gitweb/?p=msmtp.git;a=blob_plain;f=scripts/msmtpq/README.msmtpq;hb=HEAD
I went ahead tonight and compiled msmtp from source to get version 1.8.14. I
was previously on 1.8.8. I did the steps suggested in the link you provided.
Everything worked well. Then I thought I would test this queuing
functionality. I disconnected from my network and sent a test email. It
promptly popped up in the queue directory. So far so good. I reconnected to
my network and waited expectantly for the queued mails to be sent. They just
sat there. I looked through the source of the msmtpq script and AFAICT queued
emails will *not* be sent until the next attempt to send a mail.
So I tested this and sure enough the queue flushed itself and my earlier
queued email was sent. As I do not consider myself competent in shell
scripting, am I reading the source correctly? Is there an obvious way forward
to check periodically for regaining the network connection and flushing the
queue? If there is built-in functionality to do this, I am not finding it.
TIA!
--
Wishing you only the best,
boB Stepp
More information about the Mutt-users
mailing list