jkoral@luc.edu writes:
-Mailman was installed using the virtual environment. -Mailman info: -I use systemd to stop and start the services.
OK, this is all about as close to the environment most of the Mailman devs run as you can get. On the one hand, it's easiest for us to understand, but it also makes it more mysterious when something doesn't work ... "works for me", you know.
REST credentials: restadmin:restpass
You should change this. It just makes it a little more annoying for someone unauthorized who gets access to port 8001, but it's very low cost to change.
-Virgin is running: Note: Not sure how to check the queue, but when I run mailman3 notify, the moderator e-mails get sent.
Good. The queues are implemented with Python pickle files in the "queue" subtree, probably /opt/mailman/var/queue in your case, or maybe /opt/mailman/mm/var/queue if you use Mark's preferred setup. You're looking for .pck files in subdirectories of that directory which are older than about 5 minutes.
I don't have a suggestion why the "notify immediately" option isn't working. Both the 'mailman notify' command and the 'notify immediately' option work the same way, by composing the notification and dropping it in the virgin queue.
This should tell you the same thing that Postorius does, but you could try "su - mailman" followed by activating the virtual environment, then type
mailman withlist -l list.with.problem
and then
m.admin_immed_notify
expecting the response True according to your setting. If it comes up False, there's your problem but we need to figure out why that's different from what Postorius is telling you. You should be able to change it as well by typing
m.admin_immed_notify = True commit()
and exiting.
Steve