On Sun, Nov 19, 2023 at 04:56:27PM +0000, John Rouillard wrote:
> 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...

Yes, this is the method I'm using in one of the containerized instances
I'm running.

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

Yes, but this is the same for other imap installations.

Running the mailgw inside the delivery chain is problematic since
maintenance of the system is harder. And I don't know about
infrastructures where this is possible anymore, most companies (even
small ones) have a dedicated mail server and will not be able to deliver
some mailboxes via a dedicated transport.

> 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.

Could be possible but this is not a use-case I see in my installations.
So we're usually stuck with polling the mail system via imap (or even
pop3).

But if this is a use-case you're seeing it's certainly a good idea to
make it work...

Ralf
-- 
Dr. Ralf Schlatterbeck                  Tel:   +43/2243/26465-16
Open Source Consulting                  www:   www.runtux.com
Reichergasse 131, A-3411 Weidling       email: office@runtux.com