Mailman 3 April 2019 - Mailman-Users

REST API user_id and mailman_id are big integers
by Kiffin Gish April 23, 2019

April 23, 2019

Hi there. I'm implementing a frontend for accessing the mailman-core via the REST interface. Two problems arise, and both are related to the fact that in the json response the mailman_id and the user_id are big integers. As the values are greater than the maximum json integer format they appear as exponential values with the last digits truncated. I was just wondering if there is a proper way to handle this and/or it is possible for the REST API to return these values as strings rather than numbers. Kind regards, Kiffin -- Kiffin Gish Gouda, The Netherlands

2 2

Changing non-member message
by Bernie Cosell April 23, 2019

April 23, 2019

Is it possible [at least without hacking the python code] to change the default reject message that gets sent when a not-allowed member posts to a list. the default message is a terse "non-members are not allowed to post to this list", but that confuses a lot of people. they don't think of being on a mailing list as being an "member" of it. And several of my lists are associated with actual clubs and the club-members are confused and irritated to be called a "non member" [the problem is almost always a legit person posting from some different email address]. What I've done [by hand] is send a reject that says This is a closed list and posts from unsubscribed email addresses are not allowed. It'd be nice if I could configure that in, in place of the 'non member' default reject message. /Bernie\ Bernie Cosell bernie(a)fantasyfarm.com -- Too many people; too few sheep --

2 1

Mapping -owners alias to a separate list
by Dennis Carr April 20, 2019

April 20, 2019

Hey, guys. I have a multi-admin list which has a number of administrators that is greater than one who all are volunteer admins. The side effect is that the -owners alias tends to get spammed - and in some cases, it can get spammed quite profusely. (Coming to mind are spams from fqdn qq.com - which I had to block by telling Postfix to bounce everything coming "From: *(a)qq.com".) To this end, I don't wish to do too much more at the MTA level unless it gets bad again, but aliases tends to send it over to 'mailman list admins' which in turn emails the admins as expected - but that means *everything* gets through. So to this end, my thought is to route that mail over to a separate -admins list instead of 'mailman list admins'. The expected side effect is that this will wind up in the -admins list "not-subscribed" trap. Is there a better way to do this, or am I good doing that sort of thing? -Dennis Carr

3 4

Restrict archives to Administrator
by Mark Dale April 19, 2019

April 19, 2019

Hi, I've posted some notes on restricting a list's archive to Administrators only. They may be of use to some folks. It's a hack of Jim Popovitch's code which restricts archive access to unmoderated subscribers. Restrict archives to Administrator only (for Mailman 2.1.29) https://www.postmark.io/mm2/archives_for_admin_only.html Best, Mark

3 5

Disallow posting and alert members about replacement list
by Andy Cravens April 18, 2019

April 18, 2019

Using mailman 2.1.26. I have a list that is going to be retired and I need to stop people from posting to the old list. However, I don’t want to delete the list quite yet. Also, I need to auto-reply to any attempted posters that the list is being replaced with a new list. I have a plan but would like to see if I’m doing this the best way possible. 1) I’m going to put the list in emergency moderation mode so no more posts will go out. 2) Set Discard Held Messages to 1 day so the held messages don’t build up. 3) Configure the Auto-Responder (Auto-response text to send to mailing list posters.) telling them to use the new list. Does this sound reasonable? Is this the best way to achieve this? Thanks, Andy

2 1

creating an announce only list?
by Adam Morris April 14, 2019

April 14, 2019

Hi all, Can someone remind me what I need to do to make an email list announce only opposed to a normal list where people can post and reply to messages. TIA. -- Adam Morris Jaws certified 2016 Email, iMessage & FaceTime adam(a)damorris.com

3 2

Re: [Mailman-Users] Now that Python 2 is dead
by Mike Flannigan April 13, 2019

April 13, 2019

I'm surprised to hear there is so much migration in Python with limited backward compatibility.?? Perl has never had that problem.?? I almost never have to modify my old code.?? I'd recommend you use Perl, but everybody knows Perl is dead :-) Mike On 4/10/2019 6:03 PM, mailman-users-request(a)python.org wrote: > Python 3.4 is not compatible with python 3.6 is not compatible with > python 3.7 -- there is not guarantee you won't have to do the same dance > again and again every couple of years. Quite the opposite, in fact. > > Ada (yes) and Go's the stated goal is to be long-term stable. Something > that basically isn't broken, like MM2, wouldn't need to be fixed > "because 2020". >

7 10

Now that Python 2 is dead in 2020 what are people's plans with mailman2?
by Matthew Goebel April 13, 2019

April 13, 2019

Hey, Now that all support for Python 2 is supposed to go away in 2020 are people going to move off of mailman 2? I've been looking at mailman 3 and finding it hard to grok after using mailman 2 for many years. I haven't seen a discussion about this so I thought I would check and see if people were willing to share their thoughts. I will be bugging the mailman 3 users list about some questions I have about that software. Thanks, Matt -- Matthew Goebel : goebel(a)emunix.emich.edu : Unix Jockey @ EMU : Hail Eris Neo-Student, Net Lurker, Donut consumer, and procrastinating medher... "Always with the negative waves, Moriarty" - Oddball "Comfort the troubled, and trouble the comfortable." - Dietrich Bonhoeffer

10 19

Malformed URLs for some admin web page links
by Jeff Hunter April 10, 2019

April 10, 2019

I have a mailman list that is working correctly, except for some of the links on the base admin web page and it's child pages. The list is at listserv.mydomain.com and all of the links on the list admin page start with that base url, except the link "Go to list archives". That link drops the listserv. from the link (mydomain.com/......). Moving to the Membership Management page, the link "Click here to include the legend for this table." Drops the listserv off, each of the links on the alphabet letters to search for member names also drop the listserv, while the other links all have the listserv.mydomain.com base url. Listserv.mydomain.com is a virtual domain, and the email host is just mydomain.com (not listserv.) My mm_cfg.py has VIRTUAL_HOSTS.clear() # Required when setting any of its arguments. add_virtualhost('listserv.brushchamber.org') VIRTUAL_HOST_OVERVIEW = Off Any idea how to get those malformed links to match the listserv.mydomain.com base URL? Thanks! Jeff Hunter

2 1

Systemctl unit file for MM
by Bryan Blackwell April 10, 2019

April 10, 2019

Hi folks, I'm learning how to use systemd on my Fedora box, since I still had MM as a script startup I thought I'd fix that. Below is a unit file, it starts and stops ok but the rm command doesn't work. Comments welcome. [Unit] Description=Mailman, the GNU Mailing List Manager After=local-fs.target postfix.service [Service] Type=forking ExecStartPre=/bin/rm -f /home/mailman/locks/* ExecStart=/usr/bin/python /home/mailman/bin/mailmanctl -s -q start ExecReload=/usr/bin/python /home/mailman/bin/mailmanctl -q restart ExecStop=/usr/bin/python /home/mailman/bin/mailmanctl -q stop [Install] WantedBy=multi-user.target -- Bryan Blackwell -- Unix Systems Engineer bryan(a)skiblack.com

3 4