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 <m...@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:
> 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


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?


>>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


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 <m...@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-le...@python.org 
https://urldefense.com/v3/__https://mail.python.org/mailman3/lists/mailman-users.python.org/__;!!MvWE!CKoWzOsW1jpyJZ4UfPoSnKViUa9ompzCvW9gXlitG1hhO5HiCpi-h9lejzI_HV4t0JbeLkowkImZ9Go$
Mailman FAQ: 
https://urldefense.com/v3/__http://wiki.list.org/x/AgA3__;!!MvWE!CKoWzOsW1jpyJZ4UfPoSnKViUa9ompzCvW9gXlitG1hhO5HiCpi-h9lejzI_HV4t0JbeLkowrK1Uj7E$
Security Policy: 
https://urldefense.com/v3/__http://wiki.list.org/x/QIA9__;!!MvWE!CKoWzOsW1jpyJZ4UfPoSnKViUa9ompzCvW9gXlitG1hhO5HiCpi-h9lejzI_HV4t0JbeLkowpjit3p0$
Searchable Archives: 
https://urldefense.com/v3/__https://www.mail-archive.com/mailman-users@python.org/__;!!MvWE!CKoWzOsW1jpyJZ4UfPoSnKViUa9ompzCvW9gXlitG1hhO5HiCpi-h9lejzI_HV4t0JbeLkowVSUAvuc$
    
https://urldefense.com/v3/__https://mail.python.org/archives/list/mailman-users@python.org/__;!!MvWE!CKoWzOsW1jpyJZ4UfPoSnKViUa9ompzCvW9gXlitG1hhO5HiCpi-h9lejzI_HV4t0JbeLkow2jsC1vw$
Member address: chris.puchal...@rtx.com
------------------------------------------------------
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
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/mailman-users@python.org/
    https://mail.python.org/archives/list/mailman-users@python.org/
Member address: arch...@jab.org
  • [Mailm... chris.puchalski--- via Mailman-Users
    • [... Mark Sapiro
      • ... PUCHALSKI, Chris A RTX via Mailman-Users

Reply via email to