From: Robert Winkler <robert.winkler.mail@gmail.com>
To: The Sup email client <supmua@googlegroups.com>
Subject: Re: [sup] Delayed sending of emails => offline reading
Date: Thu, 26 Nov 2020 06:45:46 -0800 (PST) [thread overview]
Message-ID: <f8baf45f-6c58-4cce-9ab4-feb812b724cfn@googlegroups.com> (raw)
In-Reply-To: <7b7a64c2-2883-490b-983e-effcdc24b136n@googlegroups.com>
[-- Attachment #1.1: Type: text/plain, Size: 2623 bytes --]
Hi, installed <#user-content-msmtpq-enqueue>msmtpq-enqueue
and msmtpq-flush from
https://gitlab.com/lxkl/msmtpq
and set in the
.sup/config.yaml
:sendmail: "/usr/local/bin/msmtpq-enqueue -oem -ti"
Twice a day, the emails are sent by a cron job, once a day they are
collected:
11 11 * * * /usr/bin/offlineimap >/dev/null 2>&1
16 16 * * * /usr/local/bin/msmtpq-flush >/dev/null 2>&1
10 10 * * * /usr/local/bin/msmtpq-flush >/dev/null 2>&1
This way, my emailing now is discontinuous; 'chat'-like conversations are
avoided.
Best regards, Robert
On Sunday, 23 August 2020 at 10:59:39 UTC-5 Robert Winkler wrote:
> Hi, I solved the problem in a different way: I only call offlineimap
> when starting sup and answer emails => I will not see replies until I start
> sup again ;-).
> On Wednesday, 5 August 2020 at 11:25:20 UTC-5 Robert Winkler wrote:
>
>> Thanks, Iain, you got an answer for everything!
>> The msmtp-queue seems to be the perfect solution. I will try this out and
>> report back.
>> Best, Robert
>>
>> On Wed, 5 Aug 2020 at 09:33, Iain Parris <ipv2...@parris.org> wrote:
>>
>>> Hi Robert,
>>>
>>> Excerpts from Robert Winkler's message of 2020-08-04 13:22:23 -0700:
>>> > Hi, an efficient strategy to reduce email traffic is the delayed
>>> sending of
>>> > emails.
>>> > This also would allow the offline writing of emails.
>>> > Is there a way to do this in sup?
>>>
>>> Sup passes each email message to an external program to send
>>> (config.yaml, option "sendmail").
>>>
>>> For example, I personally use msmtp.
>>>
>>> To queue/delay messages, the solution would be to call an external
>>> program with this functionality built in.
>>>
>>> For example, I haven't used this personally, but perhaps something like
>>> msmtp-queue-scheduler may be of interest?
>>> <https://github.com/parisni/msmtp-queue-scheduler>
>>>
>>> (The README references Mutt, however, this should work with any MUA,
>>> i.e., should work with Sup.)
>>>
>>> Side note: I have received your email from 24 July re: keybindings,
>>> however, haven't yet looked in the detail required. I'll try to look
>>> within approximately the next week if I can, unless someone else on the
>>> mailing list beats me to it. :-)
>>>
>>> Kind regards,
>>> Iain
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "The Sup email client" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to supmua+un...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/supmua/1596637149-sup-5427%40ceres.
>>>
>>
[-- Attachment #1.2: Type: text/html, Size: 4468 bytes --]
prev parent reply other threads:[~2020-11-26 14:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-04 20:22 Delayed sending of emails Robert Winkler
2020-08-05 14:33 ` [sup] " Iain Parris
2020-08-05 16:25 ` Robert Winkler
2020-08-23 15:59 ` [sup] Delayed sending of emails => offline reading Robert Winkler
2020-11-26 14:45 ` Robert Winkler [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f8baf45f-6c58-4cce-9ab4-feb812b724cfn@googlegroups.com \
--to=robert.winkler.mail@gmail.com \
--cc=supmua@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox