Immediate notification to the administrator
Hello In Mailman, I have all the lists marked with the "Immediate notification to the administrator" option. Should list moderators receive immediate notification of new requests as well as daily reminders about the pending ones? List moderators (and list administrators) receive daily reminders of pending requests for approval, such as subscriptions to a moderated list or submissions that are held for some reason. Enabling this option results in immediate notifications being sent upon the arrival of new requests.
When there's a message being held because it needs approval, it automatically sends an email to the list owners. However, it also states that it sends a daily reminder if the email remains unapproved, but it's not doing that. I'll show you how I have /etc/postfix/transport configured. I receive the first "owner" email, but not the daily one.
list-owner@llistes.csuc.cat relay:[ip]:25 list@llistes.csuc.cat .. list-admin@llistes.csuc.cat ... list-bounces@llistes.csuc.cat ... list-confirm@llistes.csuc.cat ... list-join@llistes.csuc.cat ... list-leave@llistes.csuc.cat ... list-request@llistes.csuc.cat ... list-subscribe@llistes.csuc.cat ...
pau.baiges@csuc.cat writes:
When there's a message being held because it needs approval, it automatically sends an email to the list owners. However, it also states that it sends a daily reminder if the email remains unapproved, but it's not doing that.
Did it send the daily reminder before, and then stop? Or did it never send the daily reminder?
The immediate notification is triggered by the receipt of the moderated mail. However, once that happens, the Mailman daemon no longer pays attention to it. Instead, there is a cron job that runs once a day that checks the held queue and sends daily reminders.
The most likely reason is that the cron job is not running.
I'll show you how I have /etc/postfix/transport configured. I receive the first "owner" email, but not the daily one.
This is irrelevant. The same Mailman function is used to send both the immediate notification and the daily reminder, and it does not use the list-owner alias to do so. The difference is only whether it is run from the Mailman runner daemon or from a one-shot process started by cron. It consults the list configuration directly when composing the email.
Steve
I have checked that the following cron could be created to make the checks.
0 8 * * * /path/to/mailman notify
But the mailman notify command itself shows the following error:
Usage: mailman [OPTIONS] COMMAND [ARGS]... Try "mailman -h" for help.
Error: No such command "notify".
On 11/2/23 15:04, pau.baiges@csuc.cat wrote:
I have checked that the following cron could be created to make the checks.
0 8 * * * /path/to/mailman notify
But the mailman notify command itself shows the following error:
Usage: mailman [OPTIONS] COMMAND [ARGS]... Try "mailman -h" for help.
Error: No such command "notify".
Which version of mailman do you have?
"mailman notify" command was added in v3.3.0 ~4 years ago.
-- thanks, Abhilash Raj (maxking)
On Thu, Nov 2, 2023 at 2:14 PM <pau.baiges@csuc.cat> wrote:
mailman3.2.2 ... Is there no other option?
pip install -U mailman ??
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]
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
On 11/2/23 07:48, Stephen J. Turnbull wrote:
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
This Mailman 3.2.2 cron/crontab.in.in file is is an artifact from Mailman 2.1. Nothing there is relevant to any Mailman 3 version
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 11/2/23 10:05, Stephen J. Turnbull wrote:
Mark Sapiro writes:
This Mailman 3.2.2 cron/crontab.in.in file is is an artifact from Mailman 2.1. Nothing there is relevant to any Mailman 3 version
So there was no daily notification at all in Mailman 3.2.2?
Correct. There was no daily notification at all prior to Mailman 3.3.0.
See https://gitlab.com/mailman/mailman/-/issues/258
That kinda sucks for this user.
Yes it does. I *think* the user could just copy
<https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/commands/cli_notify.py>
to the installed mailman/commands/ directory to implement the mailman notify command. This also requires copying
<https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/templates/en/list:admin:notice:pending.txt>
to the installed mailman/templates/en/ directory.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (5)
-
Abhilash Raj -
Mark Sapiro -
Odhiambo Washington -
pau.baiges＠csuc.cat -
Stephen J. Turnbull