Mailman 3 August 2024 - Mailman-Users

Mailman 2 Issues With Processing Email
by chris.puchalski＠rtx.com 11 Sep '24

11 Sep '24

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?

3 2

Digests are not sent
by Christian Buser 10 Sep '24

10 Sep '24

Hi all Mailing list running in Mailman 2.1.39 / cPanel. The digest option seems not to work. Users are complaining that they don’t receive the daily digests, and trying to send a digest manually with "send_digest_now" results in the following error message: Bug in Mailman version 2.1.39 We're sorry, we hit a bug! Please inform the webmaster for this site of this problem. Printing of traceback and other system information has been explicitly inhibited, but the webmaster can find this information in the Mailman error logs or the web server logs. Any idea what we could do here? Thank you, Christian -- Christian Buser, Hohle Gasse 6, CH-5507 Mellingen (Switzerland)

2 4

Re: Error Causing Emails To Deliver Extremely Late
by PUCHALSKI, Chris A RTX 30 Aug '24

30 Aug '24

Started getting complaints on slow delivery of emails and looking at headers it appears that emails are getting trapped in the service for a few hours (2-3 hrs) before coming back out. In logs I see this happening about every minute or so: Aug 30 16:28:02 2024 (2301) send_digests() failed: maximum recursion depth exceeded I have restarted most services and after that failed to resolve the issue rebooted the whole server but the error persists. We don't use digests and there has been no changes to the system in some time. Also this is the first time this has occurred. Any clues on how to resolve and possible prevent this from coming back? Also starting to see this in logs: "Failed to unlink/preserve backup file:"

1 0

spamming
by Jim Dory 09 Aug '24

09 Aug '24

I've got a new problem with my mailing list. I run a local announcements/trade list that should be of no interest to non-locals. I started seeing warnings from Yahoo about users marking messages as spam.. (I'm subscribed to Yahoo's Antispam Feedback. I never got other feedback loops from others - like Microsoft - to work). The messages that were being marked as spam by users were the confirmation emails sent by mailman to confirm a signup. To avoid having Yahoo shut down the list as spam (for its subscribers), I set the subscription to be approved by admin, so I could review who was trying to sign up. More and more now I'm seeing what appears to be spammers trying to subscribe, but I can't be sure. I'm seeing emails like: hirofeet0916(a)yahoo.co.jp (doesn't seem local) blvckpvlm(a)gmail.com (not many use user names such as that) fsafwcasgsadf2(a)gwqc.com (obviously not real - couldn't find domain with minimal searching) Plus some that could be local but how would I know. I could take off the "approval by admin" for subscription and just deal with anyone that is a problem afterward, but I do worry that they may be harvesting emails from subscribers, which are available in the reply-to headers. Don't know if there's anything I can do. Anyone else dealing with this? thanks. Jim

8 31

features in Mailman 3 compared to its predecessor, Mailman 2
by Trophy Developers Uganda Best Web Designers 04 Aug '24

04 Aug '24

What are some key improvements and features in Mailman 3 compared to its predecessor, Mailman 2?

3 2