Roundup Tracker - Issues


Author rouilj
Recipients rouilj, schlatterbeck
Date 2023-11-19.16:56:27
Message-id <>
In-reply-to <>
Hi Ralf:

In message <>,
Ralf Schlatterbeck writes:
>On Sun, Nov 19, 2023 at 05:35:37AM +0000, John Rouillard wrote:
>How about using an IMAP port external to the container for retrieving
>mail? That can either be in its own container or be the mailserver of
>the organisation, or a cloud, ...

Yup, using imap or pop are some of the options I mention at:

But how do you trigger the call to roundup-mailgw? Some service has to
be running to schedule/trigger roundup-mailgw. Running cron as root
inside the container is problematic as is running cron as non-root.

You can use cron on the docker host (assuming it's not just a
dedicated docker/kubernetes host environment) to run:

   docker exec roundup-tracker roundup-mailgw tracker \
         imaps  ...

periodically, but...

Neither of those runs roundup-mailgw in response to an arriving email

So I thought why not run an smtp frontend that drives the
roundup-mailgw on email arrival. The docker container hosting the smtp
server (really receiver) acts similar to a kubernetes sidecar.
Date User Action Args
2023-11-19 16:56:27rouiljsetrecipients: + rouilj, schlatterbeck
2023-11-19 16:56:27rouiljlinkissue2551301 messages
2023-11-19 16:56:27rouiljcreate