On Mon, Nov 2, 2026 at 3:18 PM alain williams <addw@phcomp.co.uk> wrote:

I receive several of these a day, not one an hour.

• What are they ? (what do they mean)

• How do I stop them ? (or should I do something with what they are telling me)

This is from a Debian 13 (Trixie) machine running mailman as installed from the Debian package.

You have two options:

1. Reading the documentation for the MM3 Debian's package and asking for support from the pkg maintainers, or
2. Opt to install MM3 using virtualenv - and we'll endeavor to answer your questions.

-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

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

...

...

...

...

"alain" == alain williams <addw@phcomp.co.uk> writes:

alain> I receive several of these a day, not one an hour. • What are alain> they ? (what do they mean)

these are output from your hourly cron job,

For some reason your 'manage.py runjobs hourly' is generating INFO priority messages. This particular message comes from Django; but is controlled by the settings in /etc/mailman3/mailman3-web.py

I'm running the Debian mailman3 suite but on sid, not trixie, and do not see these messages.

However, the simplest way to gt rid of them is to lower the logging level to WARN instead of INFO.

Every time I try to change Django parameters I get tied up in knots, but something like:

LOGGING['handlers']['console']['level'] = 'WARNING'

in /etc/mailman3/mailman3-web.py *might* work ... take a look in /usr/share/mailman3-web/settings.py for the logging settings.

Peter C