- Mailman-users - lists.mailman3.org

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

Issue with Held Messages
by Jean-Luc Wasmer Aug. 20, 2016

Aug. 20, 2016

Hi, No matter what action I set for member posts (Hold for moderator, Reject) they are always delivered. When I tried from a non-member email address, the message got held but when I try to see it I get a Server Error (500) page. The log files shows: ERROR 2016-08-18 01:04:30,231 base 21026 34722993152 Internal Server Error: /mailman3/lists/test.mydomain.com/held_messages Traceback (most recent call last): File "/usr/local/mailman/mailman-bundler/eggs/Django-1.8.14-py2.7.egg/django/core/handlers/base.py", line 132, in get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/local/mailman/mailman-bundler/eggs/Django-1.8.14-py2.7.egg/django/views/generic/base.py", line 71, in view return self.dispatch(request, *args, **kwargs) File "/usr/local/mailman/mailman-bundler/eggs/postorius-1.0.3-py2.7.egg/postorius/views/generic.py", line 67, in dispatch return super(MailingListView, self).dispatch(request, *args, **kwargs) File "/usr/local/mailman/mailman-bundler/eggs/Django-1.8.14-py2.7.egg/django/views/generic/base.py", line 89, in dispatch return handler(request, *args, **kwargs) File "/usr/local/mailman/mailman-bundler/eggs/Django-1.8.14-py2.7.egg/django/utils/decorators.py", line 34, in _wrapper return bound_func(*args, **kwargs) File "/usr/local/mailman/mailman-bundler/eggs/postorius-1.0.3-py2.7.egg/postorius/auth/decorators.py", line 81, in wrapper return fn(*args, **kwargs) File "/usr/local/mailman/mailman-bundler/eggs/Django-1.8.14-py2.7.egg/django/utils/decorators.py", line 30, in bound_func return func.__get__(self, type(self))(*args2, **kwargs2) File "/usr/local/mailman/mailman-bundler/eggs/postorius-1.0.3-py2.7.egg/postorius/views/list.py", line 387, in get held_messages = utils.paginate(request, self.mailing_list.held, 20) File "/usr/local/mailman/mailman-bundler/eggs/mailmanclient-1.0.1-py2.7.egg/mailmanclient/_client.py", line 443, in held moderation_reasons=entry['moderation_reasons'], KeyError: u'moderation_reasons' Cheers, Jean-Luc

2 5

Does this get archive headers?
by Mark Sapiro Aug. 2, 2016

Aug. 2, 2016

Sorry for the noise. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 0

[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

[MM3-users]Request for assistance for fresh install of Mailman 3.0.3 and Python 3.4
by Rubén Rivero Capriles June 1, 2016

June 1, 2016

Hello World! Very nice to meet you all this afternoon! In order to avoid compatibility issues, I reinstalled CentOs 7. Firewalld, Apache and BIND are operational. I also installed Python 3.4 at http://www.codeghar.com/blog/install-latest-python-on-centos-7.html; however I understand that Python 2.7 is still available and am confused about usage of each version. I downloaded the tarball for mailman 3.0.3. I will greatly appreciate if you quickly let me know how to install it. I do not wish to use mailman bundler.

5 15

[MM3-users]Re: Request for assistance for fresh install of Mailman 3.0.3 and Python 3.4
by Rubén Rivero Capriles May 31, 2016

May 31, 2016

Hi Simon, Richard and Mark: Thanks for directing me to man crontab. I'm sure I'll work the issue out within reasonable time. Yes, indeed awstats reads postfix logs, the main reason I'm installing it is because it's helpful for analyzing website traffic. There are limitations: for example, there is an Apache GeoIP plugin for matching IP addresses with countries. My IP address and domains are registered in the USA but I live in Venezuela and my websites, although being bilingual, are very geared to Venezuelan issues. Probably millions of other people worldwide share this kind of background. So how effective is it to rely on those statistics anyway? I look forward to comparing awstats with Mailman Daily Status Report. I was honored to receive an email today from Thomas Woerner of Fedora, chief developer of the firewalld project, requesting to the Firewalld Users Discussion list to download today's release of 0.4.2. It is supposed to have fixed the various bugs we have recently dealt with. Which method should I use to download it? Am interested in upgrading firewalld immediately because the old version conflicted with ebtables and my OS python 2.7 got confused because of that last week. You have taught me to be be careful about managing simultaneously Python 2 & 3 or Mailman 2 & 3. Here are enclosed details of firewalld upgrade. My installed version of firewalld is 0.3.9 and yum doesn't provide any updates. Until yesterday both 0.4 and 0.4.1.2 were available from sources; and 0.4.2 was released today. "Thomas Woerner <twoerner(a)redhat.com> <twoerner(a)redhat.com> Para Firewalld users discussion list <firewalld-users(a)lists.fedorahosted.org>Firewalld development list <firewalld-devel(a)lists.fedorahosted.org> Hoy a las 14:44 The new firewalld version 0.4.2 is available with several enhancements, bug fixes and huge speed ups. The main changes of firewalld-0.4.2 are New transaction model --------------------- Changes are done in one big transaction instead of smaller ones. This speeds up firewalld start and restart tremendously. The start is done up to in six or nine calls to the restore commands depending on the configuration. This depends on ipset and also direct configuration usage. Also all other actions benefit from this change. Enhanced handling of connections and interfaces ----------------------------------------------- For interfaces that are handled by NetworkManager, requests to add or change bindings are directed to NetworkManager in the firewall-cmd and firewall-config tools. For interfaces on Fedora and RHEL systems that are not handled by NM, there is a new mechanism that changes the ifcfg file if there is one using the interface. This makes zone interface bindings more consistent. Usability enhancements for firewall-config ------------------------------------------ firewall-config has a new side bar with the active bindings of connections, interfaces and also sources. With this side bar it is possible to change the binding assignments in a simple way. A new overlay message window if the connection to firewalld could not be established or if it is lost. Speed ups for view changes runtime to permanent and back by introduction of new D-Bus methods in firewalld. The resize behavior has been fixed to be more expected. Enhanced runtime to permanent migration --------------------------------------- The enhanced migration is not saving interfaces that are under control of NetworkManager to the permanent configuration. Zones, services etc. are only migrated if there are changes compared to current permanent configuration. New ICMP block inversion ------------------------ The ICMP block is now completely handled per zone. With the new ICMP block inversion flag in the zone it is possible to invert the ICMP block. That means that the enabeld ICMP blocks are allowed and all others are blocked. In a drop zone these remaining types are dropped and not blocked. The logging of denied rules have been added to icmp-blocks. Source port support in zones, services and rich rules ----------------------------------------------------- Additionally to ports is it also now possible to allow source ports in a zones and also in a service in a similar way as existing ports. There is a new flag source-port for this. Source ports can also be used in rich rules as elements. The source ports can be combined with logging, limiting and also an action. Rich rules with destination only* *------------------------------------- Destination addresses can now be used in rich rules without an element. This enabled the use of rich rules containing destination addresses combined with an action and logging only. There are also several other bug fixes or enhancements and code optimizations. ------------------------------------------------------------------------ The new firewalld version 0.4.1.2 is available here: https://fedorahosted.org/released/firewalld/firewalld-0.4.2.tar.bz2 Also on github: https://github.com/t-woerner/firewalld/releases/tag/v0.4.2 And in the github repository: https://github.com/t-woerner/firewalld/ <https://github.com/t-woerner/firewalld/> <https://github.com/t-woerner/firewalld/tree/v0.4.0> _______________________________________________ Rubén Rivero Capriles http://www.rubenrivero.net (blog global - español) http://www.rroopstr.com (global blog - English) http://www.riverocooper.com (art & mining)

1 0

[MM3-users]Is is possible to allow all users Create List functionality?
by Carrie Knox May 27, 2016

May 27, 2016

Hello, My company is evaluating mailman3 as an option for a company internal list server. One of the requirements is that any registered user be allowed to create and maintain lists. Is this possible? If so, how? Does a "create list" role need to be added as a default role during account creation? Thanks, Carrie

1 0