On 10/04/2018 12:19 AM, Henrik Rasmussen wrote:
Currently I am running Mailman version 3.2.0a1 which doesn't seem to have a --periodic option.
3.2.0a1 was never an 'official' release. It could be any HEAD version between June 4, 2017 and Jul 10, 2018. The --periodic option was added April 28, 2018.
When running "docker exec mailman-core mailman digests --send --verbose -l listname@lists.example.com", output is "listname.lists.example.com sent volume 11, number 4" and this increases each time, but even I do approve held mails, none are sent (according to the smtp.log and docker logs posrfix).
Are there accumulated messages for the digest when you run the command?. I.e., is there a var/lists/listname.lists.example.com/digest.mmdf file with messages in it? Are there list members receiving digests? If so, there should be something in Mailman's smtp.log.
As I understand, using --sent should send a digest immediately (except when used with --dry-run).
Correct,if there is one to send.
As the default Digest size threshold was 30KB, making very small digests being sent, I increased this (for test) to 5000 KB (or is it Kilo bits, as the text says "How big in Kb should a digest be before it gets sent out?"?
It is Kilobytes.
Could Digest size threshold have any impact on why no digests are sent even I run "docker exec mailman-core mailman digests --send --verbose -l listname@lists.example.com" or is this an issue in the version I am using?
The digest size threshold has no effect on whether or not a digest is sent by 'mailman digests'.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan