Mailman 3 January 2025 - Mailman-Users

Upgrade instructions
by G. Armour Van Horn June 7, 2025

June 7, 2025

I have a couple of Mailman lists on a server happily running 2.1.9 but I am also a moderator on a very active list that's running on 2.1.12. I do not host this list, just volunteer because I have some experience with Mailman. That list has started to get some significant bounces due to the DMARC issue that isn't addressed in this older version. The host intends to upgrade so that we can address that but they report that they haven't been able to make archives searchable in their experimentation with 2.1.16. I don't know if that search function is part of the more recent versions of Pipermail or if they've installed something else. I'm nervous about attempting to upgrade, given the paucity of documentation for that, particularly the fact that it tells me to use the same configuration options I used for the current install and I haven't a clue what those might have been. If I could find some more robust upgrade docs I'd like to try the upgrade in case I could contribute anything to the problem with the large list. Today I had to clear the bounce flags on 47 members. Not all that hard, but tedious. Van -- ---------------------------------------------------------- Sign up now for Quotes of the Day, a handful of quotations on a theme delivered every morning. Enlightenment! Daily, for free! http://www.qotd.org/subscribe.html For photography, web design, hosting, and maintenance, visit Van's home page: http://www.domainvanhorn.com/van/ -----------------------------------------------------------

4 4

DKIM signatures
by jerry.barnabee＠gmail.com Jan. 31, 2025

Jan. 31, 2025

Is there any work around that can add a valid DKIM signature to outgoing mailman 2.x emails.

4 15

upcp error in check_perms
by Webmaster EnergyJustice Jan. 24, 2025

Jan. 24, 2025

Hello, all, I looked through the archives, FAQ, and bug reports, and couldn't find information on this error. [2025-01-22 19:39:30 -0500] E [./check_perms] Traceback (most recent call last): [2025-01-22 19:39:30 -0500] E [./check_perms] File "./check_perms", line 432, in <module> [2025-01-22 19:39:30 -0500] E [./check_perms] checksetuidwrap() [2025-01-22 19:39:30 -0500] E [./check_perms] File "./check_perms", line 324, in checksetuidwrap [2025-01-22 19:39:30 -0500] E [./check_perms] print ('%(wrapper)s must be set-uid'), [2025-01-22 19:39:30 -0500] E [./check_perms] NameError: global name ' ' is not defined [2025-01-22 19:39:30 -0500] E [./check_perms] The “./check_perms -f --noarchives” command (process 1565723) reported error number 1 when it ended. I'm running MM under cPanel. I have reinstalled MM twice, to no avail. My ISP has been no help. Respectfully, requesting ideas and suggestions. Thanks.

2 1

cPanel porting Mailman 2 to Python 3
by Russell Clemings Jan. 14, 2025

Jan. 14, 2025

Just FYI, since I haven't seen this mentioned here. Current roadmap is for a release this quarter: https://features.cpanel.net/tabs/11-planned-roadmap It also looks as if they've decided not to move forward with Mailman 3 for now (it's listed under "unplanned"): https://features.cpanel.net/tabs/12-unplanned ---------- Forwarded message --------- From: cpanel-jared <notifications(a)github.com> Date: Tue, Jan 14, 2025 at 8:51 AM Subject: [jaredmauch/mailman2-python3] cPanel fork of this project. (Issue #14) To: jaredmauch/mailman2-python3 <mailman2-python3(a)noreply.github.com> Cc: Subscribed <subscribed(a)noreply.github.com> Hello, my name is Jared and I'm a developer at cPanel <https://cpanel.net/>. We provide Mailman2 to our users and are also interested in porting Mailman2 to Python3. When researching the effort required to do this port, we found your project on GitHub. We decided it would be a great place to start, as you had already completed a significant amount of work. We appreciate the work done on this project and would like to share our work back to you. We have our fork <https://github.com/cpanel/mailman2-python3> in a state that we are comfortable releasing to our users. We will be maintaining our fork going forward but would also like to contribute back to your project if it is desired. We have two options. cPanel can submit a PR to your project, you can accept or reject it and continue maintaining your project, or we can continue development going forward on cPanel's fork. We would be happy to accept any PR's for issues found. Please let me know your thoughts, or any questions. — Reply to this email directly, view it on GitHub <https://github.com/jaredmauch/mailman2-python3/issues/14>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ANEPMOCPFPMUWTV6ERZKI532K…> . You are receiving this because you are subscribed to this thread.Message ID: <jaredmauch/mailman2-python3/issues/14(a)github.com> -- =============================================== Russell Clemings <rclemings(a)gmail.com> ===============================================

1 0

Using Mailman at Hostmonster - default server IP
by ski＠brytt.net Jan. 13, 2025

Jan. 13, 2025

Help. I have been using mailman at hostmonster many years. Recently, email delivery to external domains stopped (yes, DNS / SPF/ DKIM/ DMARC all good). Hostmonster says it is a IP address issues Hostmonster - "The emails sent via Mailman use the IP address 127.0.0.1, which is the default IP address of the server. Unfortunately, when emails from this address are dropped due to mailing list restrictions, it becomes challenging to lift these restrictions, thereby preventing us from resolving the Mailman-related issues effectively. " Has anyone else experienced this problem? Is there a solution? Thank you, Michael

5 13