On Wed, 9 Aug 2017 15:45:48 -0700 Mark Sapiro <mark@msapiro.net> wrote:
On 08/09/2017 02:35 PM, Abhilash Raj wrote:
Hi,
On Wed, 9 Aug 2017 13:42:20 -0700 Mark Sapiro <mark@msapiro.net> wrote:
[...]I wasn't aware that Core needed cron jobs too, is that true for 3.1 release as well?
It's only that one and whether it's needed or not depends on list configuration. The list has attributes digest_send_periodic and digest_size_threshold. When a post is received it is added to the list's digest mbox, and if that causes the size of the mbox to reach digest_size_threshold K bytes, a digest is sent. Additionally, if digest_send_periodic is true, a digest is sent periodically whether or not it has reached digest_size_threshold.
However, the sending of periodic digests depends on cron running something periodically to actually trigger the sending.
Can this be done using the REST API? If not, maybe we should do that so that Postorius can take of the periodic tasks?
I am thinking mostly about the container images because the mailman-core container runs nothing else other than Core. I'd have to another cron for this which isn't a lot of overhead but since mailman-web container already has periodic tasks, it would be great if I could trigger it from there.
Note: I've just looked at the code and there seems to be an issue with using 'mailman digests --send' to send the periodic digests. It appears that if a list's digest mbox has any messages, 'mailman digests --send' will send a digest even if digest_send_periodic is false. I've just reported <https://gitlab.com/mailman/mailman/issues/384> for this issue.
Also, it seems that Postorius doesn't have any way to set
digest_send_periodic and only has a setting to set the max_threshold for the
digest. I opened another issue
(https://gitlab.com/mailman/postorius/issues/211) to add this feature.
-- thanks, Abhilash Raj