Random Posts Received by List, and Archived, But Not Sent to Members

I’ve got a strange question, that hopefully someone can point me in the right direction.
We’ve got a Mailman 2.1.26 server, with Postfix 3.3.0 as the MTA which has been running for several years; however, recently we’ve been noticing random cases where posts sent to a list (it can be any list hosted by the server), are received by Postfix, handed off to Mailman, appear in the list’s archives, but are never sent back out to the list members.
In an effort to troubleshot this we have a scheduled task on another sever that sends an hourly “heartbeat” message to a specific list. We’re seeing the following random patterns:
- Some days every hourly message arrives to the list, is archived, and is successfully sent to list members.
- Some days several of the hourly messages arrives to the list, is archived, and is successfully sent to list members, only to be followed by some (random 1-3) hourly messages that are archived but not sent out, then delivery resumes as expected.
There is no consistency with time of day regarding to which messages are not being received by list members. Checking both the Postfix mail.log, and Mailman post log files we notice that the messages which are received by the list members is record within both files; however, the missing messages are only recorded within the Postfix log file, the matching entry in the Mailman post log is absent.
Digging through this list’s archives I found a similar post<https://mail.python.org/archives/list/mailman-users@python.org/thread/3FACVS...> from years ago; however, no resolution appeared to have been identified. Working through the “4.78 Troubleshooting: No mail going out to lists members<https://wiki.list.org/DOC/4.78%20Troubleshooting-%20No%20mail%20going%20out%20to%20lists%20members>” doesn’t appear to have identify any likely causes/fixes.
Any suggestions on how to track down this gremlin?
Have a great day, Chris
-- Chris Axtell Enterprise Applications Engineer Information Technology Services University of Alaska Anchorage 3190 Alumni Drive, SSB 120 Anchorage, Ak 99508 email: chris.axtell@alaska.edu<mailto:chris.axtell@alaska.edu> Teams: cbaxtell@alaska.edu<https://teams.microsoft.com/l/chat/0/0?users=cbaxtell@alaska.edu>

On 10/6/22 11:16, Chris Axtell wrote:
I’ve got a strange question, that hopefully someone can point me in the right direction.
We’ve got a Mailman 2.1.26 server, with Postfix 3.3.0 as the MTA which has been running for several years; however, recently we’ve been noticing random cases where posts sent to a list (it can be any list hosted by the server), are received by Postfix, handed off to Mailman, appear in the list’s archives, but are never sent back out to the list members.
Are they in the shunt
queue? What's in Mailman's error
log? What's
in Mailman's qrunner
log, i.e. evidence that OutgoingRunner is dying
and restarting?
Because the post
log entry is written by OutgoingRunner when the
outgoing message has been delivered.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

On 10/6/22 11:16, Chris Axtell wrote:
I’ve got a strange question, that hopefully someone can point me in the right direction.
We’ve got a Mailman 2.1.26 server, with Postfix 3.3.0 as the MTA which has been running for several years; however, recently we’ve been noticing random cases where posts sent to a list (it can be any list hosted by the server), are received by Postfix, handed off to Mailman, appear in the list’s archives, but are never sent back out to the list members.
Are they in the shunt
queue? What's in Mailman's error
log? What's
in Mailman's qrunner
log, i.e. evidence that OutgoingRunner is dying
and restarting?
Because the post
log entry is written by OutgoingRunner when the
outgoing message has been delivered.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (2)
-
Chris Axtell
-
Mark Sapiro