On Wed, Jul 30, 2025 at 5:28 PM Stephan Krinetzki < krinetzki@itc.rwth-aachen.de> wrote:
Hi all,
I'm running into an issue with Mailman 3. Mails sent to a list are being held due to moderation settings — which is expected — but after approving them, they are not delivered to list members.
The message does not end up in the shunt queue, and nothing is delivered.
Here's what I see in the Mailman log:
Jul 30 16:12:23 2025 (213300) HOLD: mm@lists.example.com post from sender@sub.example.com held, message-id=< 20250730141221.5VVrn%sender@sub.example.com>: The message is not from a list member Jul 30 16:12:39 2025 (213338) held message approved, message-id: < 20250730141221.5VVrn%sender@sub.example.com>
In the mail log, I only see the message arriving — there's no sign of it being sent out.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ This here does not make sense. the queue?
- You approve/UNHOLD the message - what then do you see in /opt/mailman/mm/var/logs/smtp.log?
- The mail is handed over to your MTA, and you see evidence of that in mail.log, but it is not sent out. Doesn't that mean you have the mails in
Any ideas on what could be going wrong or where else I should look?
What is the output from running the mailq command?
If the post has not reached the subscribers, then I suppose the emails are
stuck in the Postfix queue for some reason.
Mailman Core-Version GNU Mailman 3.3.10 (Tom Sawyer) Mailman Core API-Version 3.1 Mailman Core Python-Version 3.11.11 (main, Jun 20 2025, 00:00:00) [GCC 11.5.0 20240719 (Red Hat 11.5.0-5)]
OS: Rocky 9 with Postfix MTA, installed as venv
Do you know if the list has been working, or is this a new install?
-- 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]