> Umm, not really. You can have multiple cron jobs scheduled running
> under one cron binary.

Yes, we can have multiple cron jobs, but if we want to get credentials or time from somewhere else, we need to write another wrapper to configure the crontab.

But mounting crontab using a docker/podman secret looks like a some solution. For example, it can be templated with Ansible.

> I'm not sure what you mean by asynchronous process. Do you mean the
> ability to schedule each tracker separately?

Something like a queue for each mailbox, independent of the others.

> Not sure what you mean here. Would you create a new rest endpoint that
> triggers mailgw when called?

I think we have several implementation options that we can think about.

For example, we can just create new issues using POST requests with authorization. But in this case we need to process emails on the poller side. It might be better to split the roundup package into roundup-www and roundup-mailgw so that they can be use separately, but I think that would require a lot of work.

Another option is to have some endpoint that will accept the serialized messages from the poller and pass it to mailgw for processing. In this case, the poller must perform preprocessing to serialize emails.

If we are trying to use the REST API, it looks like the poller needs to have its own configuration. But maybe this is a better way. It would also be nice to be able to allow requests from the poller URL.

> The roundup docker image doesn't have roundup installed in a mounted
> volume.  The mounted volume is strictly for the tracker homes.

Yes, but I should be able to create custom image where I can mount full virtual environment if I wish. And the poller should be able to work with this.

> The docker image already supports number of subcommands (admin, shell,
> demo ..). Adding one more for email would be possible.  Then you would
> run the single docker image in two modes (and two containers). Default
> mode (which runs roundup-server) and email mode which runs imapServer.

Yes, that's an option. At least it requires a less work than in other cases.

But maybe it would be nice to teach mailgw and trackers to communicate via REST API?