Mailman 2 Issues With Processing Email
![](https://secure.gravatar.com/avatar/26d47d35a5d84bd01f10fefe52f28dbf.jpg?s=120&d=mm&r=g)
I have an issue with mailman v2 where messages are coming in to the service but not coming out. The error logs report:
Aug 30 18:47:26 2024 (9118) send_digests() failed: maximum recursion depth exceeded
and an occasional:
Failed to unlink/preserve backup file: *.bak
From the oldest recoverable logs (before they rotated and got removed) I also have:
Aug 26 03:15:26 2024 (27646) send_digests() failed: maximum recursion depth exceeded Aug 26 03:15:26 2024 (27646) Uncaught runner exception: maximum recursion depth exceeded while pickling an object Aug 26 03:15:26 2024 (27646) 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/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/usr/lib/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/usr/lib/mailman/Mailman/Handlers/ToOutgoing.py", line 55, in process outq.enqueue(msg, msgdata, listname=mlist.internal_name()) File "/usr/lib/mailman/Mailman/Queue/Switchboard.py", line 110, in enqueue msgsave = cPickle.dumps(_msg, protocol) RuntimeError: maximum recursion depth exceeded while pickling an object
Aug 26 03:15:26 2024 (27646) Uncaught runner exception: maximum recursion depth exceeded while pickling an object Aug 26 03:15:26 2024 (27646) 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 110, in enqueue msgsave = cPickle.dumps(_msg, protocol) RuntimeError: maximum recursion depth exceeded while pickling an object
How do I go about finding and correcting the issue?
![](https://secure.gravatar.com/avatar/56f108518d7ee2544412cc80978e3182.jpg?s=120&d=mm&r=g)
On 8/30/24 12:00, chris.puchalski--- via Mailman-Users wrote:
Presumably the actual name is something like 1723478221.1125858+635319880943e83741c1a40db63b5de299575811.bak with different hex digits and not literally *.bak. What is the next line which is the actual reason?
This says that the specific message object can't be pickled, probably because it contains some circular reference. I don't know how that could happen.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
![](https://secure.gravatar.com/avatar/26d47d35a5d84bd01f10fefe52f28dbf.jpg?s=120&d=mm&r=g)
Since I had to wait to rejoin the list due to an email address change I managed to find my answer, or at least an answer that worked to get me back up and running.
I came across an old list posting entitled "Mailman no longer working or working very slowly" that contained my answer. I ran the included withlist command several replies in that you posted about "find_bad" and it found the bad message with the list it was attached to. The quickest way in my case was to simply delete the list involved rather than find the list since that particular one had no real value and could be easily recreated. That got the service back up and running.
So it may not have been the best solution but it was a solution that worked when I was in a tight spot. I think the message was one that was stuck in moderation as there were a few. Trying to delete it in there via the UI proved to be difficult since the list appeared to have a lock on it causing the web UI to time out, the quickest way out was to delete the involved list. Once that list was deleted things just started to work and I just recreated the list with no issues since then to speak of.
Chris P
-----Original Message----- From: Mark Sapiro <mark@msapiro.net> Sent: Tuesday, September 10, 2024 21:04 To: mailman-users@python.org Subject: [External] [Mailman-Users] Re: Mailman 2 Issues With Processing Email
On 8/30/24 12:00, chris.puchalski--- via Mailman-Users wrote:
Presumably the actual name is something like 1723478221.1125858+635319880943e83741c1a40db63b5de299575811.bak with different hex digits and not literally *.bak. What is the next line which is the actual reason?
This says that the specific message object can't be pickled, probably because it contains some circular reference. I don't know how that could happen.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-leave@python.org https://urldefense.com/v3/__https://mail.python.org/mailman3/lists/mailman-u... Mailman FAQ: https://urldefense.com/v3/__http://wiki.list.org/x/AgA3__;!!MvWE!CKoWzOsW1jp... Security Policy: https://urldefense.com/v3/__http://wiki.list.org/x/QIA9__;!!MvWE!CKoWzOsW1jp... Searchable Archives: https://urldefense.com/v3/__https://www.mail-archive.com/mailman-users@pytho... https://urldefense.com/v3/__https://mail.python.org/archives/list/mailman-us... Member address: chris.puchalski@rtx.com
![](https://secure.gravatar.com/avatar/56f108518d7ee2544412cc80978e3182.jpg?s=120&d=mm&r=g)
On 8/30/24 12:00, chris.puchalski--- via Mailman-Users wrote:
Presumably the actual name is something like 1723478221.1125858+635319880943e83741c1a40db63b5de299575811.bak with different hex digits and not literally *.bak. What is the next line which is the actual reason?
This says that the specific message object can't be pickled, probably because it contains some circular reference. I don't know how that could happen.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
![](https://secure.gravatar.com/avatar/26d47d35a5d84bd01f10fefe52f28dbf.jpg?s=120&d=mm&r=g)
Since I had to wait to rejoin the list due to an email address change I managed to find my answer, or at least an answer that worked to get me back up and running.
I came across an old list posting entitled "Mailman no longer working or working very slowly" that contained my answer. I ran the included withlist command several replies in that you posted about "find_bad" and it found the bad message with the list it was attached to. The quickest way in my case was to simply delete the list involved rather than find the list since that particular one had no real value and could be easily recreated. That got the service back up and running.
So it may not have been the best solution but it was a solution that worked when I was in a tight spot. I think the message was one that was stuck in moderation as there were a few. Trying to delete it in there via the UI proved to be difficult since the list appeared to have a lock on it causing the web UI to time out, the quickest way out was to delete the involved list. Once that list was deleted things just started to work and I just recreated the list with no issues since then to speak of.
Chris P
-----Original Message----- From: Mark Sapiro <mark@msapiro.net> Sent: Tuesday, September 10, 2024 21:04 To: mailman-users@python.org Subject: [External] [Mailman-Users] Re: Mailman 2 Issues With Processing Email
On 8/30/24 12:00, chris.puchalski--- via Mailman-Users wrote:
Presumably the actual name is something like 1723478221.1125858+635319880943e83741c1a40db63b5de299575811.bak with different hex digits and not literally *.bak. What is the next line which is the actual reason?
This says that the specific message object can't be pickled, probably because it contains some circular reference. I don't know how that could happen.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-leave@python.org https://urldefense.com/v3/__https://mail.python.org/mailman3/lists/mailman-u... Mailman FAQ: https://urldefense.com/v3/__http://wiki.list.org/x/AgA3__;!!MvWE!CKoWzOsW1jp... Security Policy: https://urldefense.com/v3/__http://wiki.list.org/x/QIA9__;!!MvWE!CKoWzOsW1jp... Searchable Archives: https://urldefense.com/v3/__https://www.mail-archive.com/mailman-users@pytho... https://urldefense.com/v3/__https://mail.python.org/archives/list/mailman-us... Member address: chris.puchalski@rtx.com
participants (3)
-
chris.puchalski@rtx.com
-
Mark Sapiro
-
PUCHALSKI, Chris A RTX