On 10/14/26 3:09 PM, Puchalski, Chris via Mailman-Users wrote:
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:


If your out queue is backlogged, see the FAQ article at https://wiki.list.org/x/17892002


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.

The message is not being shunted (attempted to be shunted) because the message is bad. It's because of the failure to queue it in the retry queue.

These errors seem to indicate that the paths /var/spool/mailman/retry/ and /var/spool/mailman/shunt/ don't exist. Do they? Presumably /var/spool/mailman/out/ exists as that is the `out` queue.

The underlying issue behind these messages is for some reason, Mailman is trying to queue the message in the retry queue, but gets the No such file or directory: error so it then tries to shunt the message, but that fails for the No such file or directory: error on the shunt queue.

Do those queue directories exist? If so, I can't explain those errors, but if not, create them with the same ownership and permissions as the others in /var/spool/mailman/, but it's hard to believe that they wouldn't exist in an installation that's been running for some time.

--
Mark Sapiro <[email protected]>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan
------------------------------------------------------
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]

Reply via email to