On 6/8/24 12:48 PM, Steve Brown wrote:
I'm a list administrator for a list hosted by mailmanlists.net on a server in Germany. Only one member uses the digest option, but she doesn't receive a digest until the Digest size threshold has been exceeded. (I also am subscribed as a member with the Mime Digest option and see the same behavior.) The option for Send Digest Periodically is checked but doesn't trigger a daily digest on the days that there is some activity if the aggregate size doesn't exceed the threshold. I think "periodically" means daily, and the administrator doesn't seem to have any way of checking or changing the periodicity. The hosting service has attempted several fixes, including fiddling with the cron settings, but hasn't found something that works. They even upgraded to ver. 3.3.9 recently, and that didn't fix the problem.
Periodic digests are sent by the mailman digests --periodic command
which should be run daily by cron. That and the mailman notify command
should be run from mailman's crontab. See
https://docs.mailman3.org/en/latest/install/virtualenv.html#setup-cron-jobs
I don't know what "fiddling with the cron settings" means, but if these commands are in mailman's crontab, including
MAILTO=some_human@example.com
at the beginning of the crontab will ensure any diagnostic output is sent to some_human@example.com where it will be seen. Also, putting
LANG=en_US.UTF-8
near the beginning of the crontab may be required in some cases. See the Attention notice at https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/instal...
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan