July 2016 - Mailman-users - lists.mailman3.org

[MM3-users]Is it possible to grant all users the ability to Create List
by Carrie Knox July 13, 2021

July 13, 2021

Hello, Our company is evaluating mailman3 as an option for company internal list serving. One of the requirements is that anyone with access to the list server be allowed to create and manage lists. Is this possible? If so, how? Is there a "create list" role that can be added for all registered users? Thanks

5 5

Docker files for mailman
by Simon Hanna Nov. 19, 2016

Nov. 19, 2016

Hi, I started working on docker files for Mailman. I created three repositories: - https://github.com/simonsmiley/postorius-docker Holds the files needed to create a postorius container - https://github.com/simonsmiley/mailman-docker Holds the files needed to create a core container - https://github.com/simonsmiley/mailman-compose Holds docker-compose files that greatly simply the process of running the containers * The mailman repo currently lacks documentation * Currently no emails can be sent. I still have to figure out what the best way is... * Hyperkitty will be added next (together with a complete "bundler" install) I pushed two images to the docker hub. Their names are thelinuxguy/postorius and thelinuxguy/mailman I created two organizations mailman on docker hub and gnu-mailman on github https://github.com/gnu-mailman https://hub.docker.com/u/mailman/ I know we shouldn't use github, but there is no way around github/bitbucket for automated builds on docker hub. I post here to inform you about the docker images and I also to ask if I'm allowed to keep these two organizations and move my images/repos there. I'll happily give push/owner access to additional people if requested. The repositories could be mirrored to the gitlab mailman group, sadly the process doesn't work the other way round just yet. In case this request gets denied, I'll just remove the organizations and let the images be "unofficial". cheers, Simon

3 3

Broken paths
by Jean-Luc Wasmer Aug. 22, 2016

Aug. 22, 2016

Hi, Is there a way to change where mailman looks for files? I've run into many issues with the default config: - mailman is specifically calling Python 3.4, ignoring the fact that I have Python 3.5 - shell scripts expect bash to be at /bin/bash (mine is at /usr/local/bin/bash) - mailman expects postmap to be at /usr/sbin/postmap (mine is at /usr/local/sbin/postmap) Please CC me in your reply as I wasn't able to join this mailing list (I login by email, get the login.persona.org pop-up, click sign in, the pop-up closes... but I'm still not logged in). Cheers, Jean-Luc

5 10

[MM3-users]Re: [Mailman-Users] Mailman3 administration
by Mark Sapiro July 31, 2016

July 31, 2016

On 06/17/2016 12:16 PM, Bill wrote: > Hi, > > I'm looking for some information on Mailman3 administration. I've found > that it's not yet packaged by any of the common Linux distros - Debian, > Ubuntu, Mint, RedHat, Centos, Fedora, Suse, Arch etc so I have some > concerns about the amount of upkeep that running Mailman3 will entail. > > I know that Mailman2 is available as a package on the above distros, but > we would really like to take advantage of the kludge-free, virtual > domains feature on Mailman3. > > I've been asked by a local non-profit provider to assist them in moving > their 200+ mailing lists from an outdated Sympa list server to > Debian8/Postfix/Mailman. One of their chief concerns is the amount of > extra administration, over and above normal list administration, that > Mailman3 will require in the form of manual updates and maintenance. > > We are in the evaluation and design stage right now, but could use any > pertinent advice about supportive distros, available packages, the > amount of extra administration involved or perhaps, in a worst case > scenario, alternate list managers supporting a virtual domains feature > similar to Mailman3. > > Thanks for your help, > > Bill McGrath > President, Vancouver Linux Users Group > https://vanlug.bc.ca I've copied this post and set Reply-To: to the Mailman 3 users list <mailman-users(a)mailman3.org>. Please join at <https://lists.mailman3.org/mailman3/lists/mailman-users@mailman3.org/> before replying there. That said, we are working on packaging for a more turn-key installation, but we aren't there yet. I've installed a couple of instances including the one at lists.mailman3.org, and it does require extra work. Some of the work in my case is because I want to run all the Mailman pieces from the heads of their branches rather than what's in PyPI, but even without that, installation is significantly more work than installing a distro's package. I will be writing up my experiences, but that's not done yet either. I will say that once you have Mailman 3 installed and running, updating (which I do frequently, but which doesn't need to be done unless you want specific updates/fixes) is pretty easy. As far as alternatives are concerned There is an up to date Mailman 2.1 branch with better virtual domain support at <https://code.launchpad.net/~msapiro/mailman/vhost>, but I think in the long run, you'd be better off with Mailman 3. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 6

Countdown to the 3.1 release
by Barry Warsaw July 13, 2016

July 13, 2016

Previously I mentioned the three big outstanding branches that I'd like to land for Mailman 3.1 Core, the templates branch, the MySQL support branch, and the unsubscription workflow branch. I've now also gone through all the bugs previously targeted to milestone 3.1, and there are only three left: https://gitlab.com/mailman/mailman/milestones/2 I think these are important enough to fix for 3.1 and I welcome merge requests while the other three branches are ongoing. Please take a look at any other bugs not assigned to milestone 3.1 and let me know if you think any are serious enough to block the 3.1 release. I'll say in advance that I'm going to be brutal in assessing them, because 3.1 really needs to be released soon! Note too that there may be blockers for Postorius, Hyperkitty, and mailman.client, but I haven't looked at those subprojects yet. How close are they to being release ready? Cheers, -Barry

2 2

Templates branch for Mailman 3.1
by Barry Warsaw July 11, 2016

July 11, 2016

Hello developers! There are three big features still in progress for Mailman 3.1, the templates branch, MySQL support, and unsubscription workflow. There is already a merge request for MySQL support and I'm hoping to merge that soon. Abhilash is also working on the unsubscription workflow feature but there's no MR for that yet. The templates feature is very nearly done, so I think now is a good time to ask for testing, feedback, and review. This is a generalization of the welcome_message_uri feature in MM3.0 where you could specify e.g. the welcome message as a URL to download and cache when necessary. This is important because Core doesn't know whether there is even a web ui (e.g. Postorius) involved, or where things like clickable links to unsubscribe would be. Sites also want to customize footers to include information like codes of conduct, etc. Now (or when this branch lands), you will be able to specify a URL to retrieve any template that Mailman uses internally, whether they are confirmation messages, bounce probes, welcome and goodbye messages, etc. These can be templates for administrators, users, and members. Because I'm hoping to get some reviews, I'll point you at the documentation for more details: https://gitlab.com/warsaw/mailman/blob/templates/src/mailman/rest/docs/temp… The branch did end up being much bigger and tentacled than I expected, but it's all hanging together pretty well now, and all the tests pass. There's still a small number of to-dos, but some of them will get punted, and the others won't have a major effect on the overall use and visibility of the feature. https://gitlab.com/warsaw/mailman/blob/templates/TODO.rst Note also that if you interact with the REST API v3.0, nothing changes externally, but the old IMailingList attributes are mapped onto the new templates mechanism. API v3.1 is where you see all the actual new feature end-points exposed. Of course, any MM2 list converted to MM3.1 will use the new templates stuff too. Feedback very much welcome, either here or on the MR: https://gitlab.com/mailman/mailman/merge_requests/170 I'd like to land this some time in the next week or so. Then I'll work on the other two big branches and start to release some betas. Cheers, -Barry

1 0

[MM3-users]Installation documentation.
by Mark Sapiro July 5, 2016

July 5, 2016

I have now done production installations of Mailman 3 on this server (lists.mailman3.org) and mail.python.org. I've attempted to document this experience at <https://wiki.list.org/x/17891998>. Suggestions for improvement and/or direct edits on the wiki are welcome. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 1