pau.baiges@csuc.cat writes:
mailman3.2.2 ... Is there no other option?
Yes. Get yourself a system where the packaged software is upgraded on a timely basis, or install the recent release yourself.
Until then, here's the crontab template distributed with Mailman 3.2.2:
# At 8AM every day, mail reminders to admins as to pending requests. 0 8 * * * @PYTHON@ -S @prefix@/cron/checkdbs # # At 9AM, send notifications to disabled members 0 9 * * * @PYTHON@ -S @prefix@/cron/disabled # # Noon, mail digests for lists that do periodic delivery. 0 12 * * * @PYTHON@ -S @prefix@/cron/senddigests # # Every 5 mins, try to gate news to mail. */5 * * * * @PYTHON@ -S @prefix@/cron/gate_news # # At 3:27am every night, regenerate the gzip'd archive file. Only # turn this on if the internal archiver is used and # GZIP_ARCHIVE_TXT_FILES is false in mm_cfg.py 27 3 * * * @PYTHON@ -S @prefix@/cron/nightly_gzip
Take the parts you need. These scripts should be installed on your system somewhere.
@PYTHON@ is the path to the Python 3 binary which is used by Mailman. It's probably not terribly sensitive if you have multiple Pythons installed, but it's a good idea to use the same one.
@prefix@ is where your Mailman code is installed, typically something like /var/lib/mailman, /var/local/lib/mailman, or /opt/mailman. cron should be a neighbor to queue, lists, and other such directories.
Steve