I did get a bit further into the digging and it appears that emails a building
up the outbound queue directory (/var/spool/mailman/out). I have already
confirmed the out running is running (ps -fwwA |grep runner=out) and that lead
me to this in the error log:
Oct 14 12:43:52 2026 (2313) Uncaught runner exception: [Errno 2] No such file
or directory: '/var/spool/mailman/retry/1791980411.545217+fc2a0a88d8708e9$
Oct 14 12:43:52 2026 (2313) Traceback (most recent call last):
File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 120, in _oneloop
self._onefile(msg, msgdata)
File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 191, in _onefile
keepqueued = self._dispose(mlist, msg, msgdata)
File "/usr/lib/mailman/Mailman/Queue/OutgoingRunner.py", line 130, in _dispose
self.__retryq.enqueue(msg, msgdata)
File "/usr/lib/mailman/Mailman/Queue/Switchboard.py", line 136, in enqueue
fp = open(tmpfile, 'w')
IOError: [Errno 2] No such file or directory:
'/var/spool/mailman/retry/1791980411.545217+fc2a0a88d8708e9d96c194e8005b3a2950f4b278.pck.tmp'
Oct 14 12:43:52 2026 (2313) Uncaught runner exception: [Errno 2] No such file
or directory: '/var/spool/mailman/shunt/1791980411.545217+f82f3518db742b2$
Oct 14 12:43:52 2026 (2313) Traceback (most recent call last):
File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 136, in _oneloop
new_filebase = self._shunt.enqueue(msg, msgdata)
File "/usr/lib/mailman/Mailman/Queue/Switchboard.py", line 136, in enqueue
fp = open(tmpfile, 'w')
IOError: [Errno 2] No such file or directory:
'/var/spool/mailman/shunt/1791980411.545217+f82f3518db742b2c8c339a4152e3bf35985e93d7.pck.tmp'
Oct 14 12:43:52 2026 (2313) SHUNTING FAILED, preserving original entry:
1791980411.545217+39b213b664fd0d19037b7050615d6fab71ea6840
Oct 14 12:43:52 2026 (2313) Failed to unlink/preserve backup file:
/var/spool/mailman/out/1791980411.545217+39b213b664fd0d19037b7050615d6fab71ea6840.bak
I have read this could be a bad message, corrupted in some way so I guess
looking for a pointer from here to where to go next.
Chris Puchalski
Prin Spclst, Cyber Defense
C: +1 214-733-7164
[email protected]<mailto:[email protected]>
RTX
Enterprise Services | ES Infrastructure
Arizona Remote Location
The power of Enterprise Scale
RTX.com<https://www.rtx.com/> | LinkedIn<https://www.linkedin.com/company/rtx/>
| X<https://twitter.com/RTX_News> |
Instagram<https://www.instagram.com/rtxcorporation/> |
Facebook<https://www.facebook.com/rtxcorporation/> |
YouTube<https://www.youtube.com/raytheontechnologies>
This message may contain RTX proprietary, business confidential, and/or
privileged in formation. Unless you are the addressee (or authorized to receive
mail for the addressee), you should not use, copy, or disclose to anyone this
message or any information contained in this message . If you have received
this message in error, please advise the sender by reply e-mail and delete this
message; you should not otherwise use, distribute, retransmit , or reproduce
this email. Thank you for your cooperation.
________________________________
From: Washington Odhiambo <[email protected]>
Sent: Wednesday, October 14, 2026 11:51 AM
To: [email protected] <[email protected]>
Cc: Puchalski, Chris (USA) <[email protected]>
Subject: Re: [Mailman-Users] Older Version of Mailman (2.1.12) Suddenly Very
Slow in Delivery
On Wed, Oct 14, 2026 at 8: 40 PM Puchalski, Chris via Mailman-Users
<mailman-users@ python. org> wrote: I have an older version of mailman that
cannot be upgraded due to a number of reasons and recently it appears that
messages sent to the
On Wed, Oct 14, 2026 at 8:40 PM Puchalski, Chris via Mailman-Users
<[email protected]<mailto:[email protected]>> wrote:
I have an older version of mailman that cannot be upgraded due to a number of
reasons and recently it appears that messages sent to the hosted lists seem to
take a very large time once in the server. I can see the messages deliver to
postfix and almost an hour later (maybe more) the messages leave the service to
the list members.
I recently have restarted postfix/mailman and in fact the whole server.
Sometimes that clears things up but today the problem has persisted. I also ran
the check_perms with the -f switch where it caught and corrected an issue
SMTPDirect.pyc about permissions needing to set to 0644. When that same check
was run a second time nothing was caught.
Where else can I dig for a possible cause to my recent issues for what has been
an incredibly system for years?
Dedicated troubleshooting should be easy enough. Employing the services of AI
is need be is okay:)
--
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<https://urldefense.us/v2/url?u=http-3A__www.catb.org_-7Eesr_faqs_smart-2Dquestions.html&d=DwMFaQ&c=MASr1KIcYm9UGIT-jfIzwQg1YBeAkaJoBtxV_4o83uQ&r=YSHnKgNEhiYTYiWfpKvuabk61iV6qMNGur1_1CS1mMM&m=EiT6DTQFogAFrh9t31F5vBwy00p8X-1UcHYYqUIswN7fXmkeaBhc9Q_-AjHMjdb2&s=X_XcbzevzZio0AraialHFO-loPbDLeLyyg2ulaXHano&e=>]
------------------------------------------------------
Mailman-Users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/[email protected]/
https://mail.python.org/archives/list/[email protected]/
Member address: [email protected]
