alain williams writes:
I receive several of these a day, not one an hour.
? What are they ? (what do they mean)
Dunno. Never heard of these before. They're from the cron daemon, which runs repeating jobs on a regular schedule. They appear to basically be log messages saying "There was work to do and it has been delgated to an appropriate process."
? How do I stop them ? (or should I do something with what they are telling me)
The "enqueued" part doesn't sound like crond, crond *is* a queue. My guess is that's the output from the job that cron is running. I believe there are ways to tell cron not to mail you about them (man crontab to learn more). You can also tell Django that it should only emit messages when something's wrong (change the log level from INFO to the next level, WARN IIRC). I don't know how to do that specifically. Probably you can do it in settings.py, but you might need to edit the files that define the jobs.
Since I've not heard of the issue before, I suspect this is a "feature" of Debian, and you should get in touch with the Debian maintainers of their Mailman 3 package (probably the HyperKitty subpackage, Mailman core doesn't use Django and Postorius has few or no cron jobs). Specifically, in Debian installations our virtualenv installation Mailman has root run the cronjobs as the mailman user from the /etc/cron.d/mailman3 (or maybe mailmanweb) crontab include file. However, this
Subject: Cron <www-data@bf****> [ -f /usr/bin/django-admin ] && systemctl is-active --quiet mailman3-web && flock -n /var/run/mailman3-web/cron.hourly /usr/share/mailman3-web/manage.py runjobs hourly
appears to say it's being run as the mailman3-web user, which might explain the difference between virtualenv behavior (no such emails) and Debian trixie behavior (annoying emails).
Steve
-- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan