May 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

[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

[MM3-users]Re: Installation issues
by Hellings Simon (EAST KENT HOSPITALS UNIVERSITY NHS FOUNDATION TRUST) May 17, 2016

May 17, 2016

Hi Simon I have tried to re-install MM3 this morning but am now facing a different error message: Output from DJANGO log as follows: ERROR Internal Server Error: /mailman3/lists/ Traceback (most recent call last): File "/opt/mailman/mailman-bundler/eggs/Django-1.8.12-py2.7.egg/django/core/ha ndlers/base.py", line 132, in get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/opt/mailman/mailman-bundler/eggs/postorius-1.0.3-py2.7.egg/postorius/vi ews/list.py", line 511, in list_index lists = sorted(List.objects.all(only_public=only_public), File "/opt/mailman/mailman-bundler/eggs/postorius-1.0.3-py2.7.egg/postorius/mo dels.py", line 144, in all objects = getattr(get_client(), self.resource_name_plural) File "/opt/mailman/mailman-bundler/eggs/mailmanclient-1.0.1-py2.7.egg/mailmanc lient/_client.py", line 158, in lists response, content = self._connection.call('lists') File "/opt/mailman/mailman-bundler/eggs/mailmanclient-1.0.1-py2.7.egg/mailmanc lient/_client.py", line 105, in call response, content = Http().request(url, method, data, headers) File "/opt/mailman/mailman-bundler/eggs/httplib2-0.9.2-py2.7.egg/httplib2/__in it__.py", line 1609, in request (response, content) = self._request(conn, authority, uri, request_uri, metho d, body, headers, redirections, cachekey) File "/opt/mailman/mailman-bundler/eggs/httplib2-0.9.2-py2.7.egg/httplib2/__in it__.py", line 1351, in _request (response, content) = self._conn_request(conn, request_uri, method, body, he aders) File "/opt/mailman/mailman-bundler/eggs/httplib2-0.9.2-py2.7.egg/httplib2/__in it__.py", line 1307, in _conn_request response = conn.getresponse() File "/usr/lib/python2.7/httplib.py", line 1051, in getresponse response.begin() File "/usr/lib/python2.7/httplib.py", line 415, in begin version, status, reason = self._read_status() File "/usr/lib/python2.7/httplib.py", line 379, in _read_status raise BadStatusLine(line) BadStatusLine: '' ERROR Internal Server Error: /mailman3/lists/ Traceback (most recent call last): File "/opt/mailman/mailman-bundler/eggs/Django-1.8.12-py2.7.egg/django/core/ha ndlers/base.py", line 132, in get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/opt/mailman/mailman-bundler/eggs/postorius-1.0.3-py2.7.egg/postorius/vi ews/list.py", line 511, in list_index lists = sorted(List.objects.all(only_public=only_public), File "/opt/mailman/mailman-bundler/eggs/postorius-1.0.3-py2.7.egg/postorius/mo dels.py", line 144, in all objects = getattr(get_client(), self.resource_name_plural) File "/opt/mailman/mailman-bundler/eggs/mailmanclient-1.0.1-py2.7.egg/mailmanc lient/_client.py", line 158, in lists response, content = self._connection.call('lists') File "/opt/mailman/mailman-bundler/eggs/mailmanclient-1.0.1-py2.7.egg/mailmanc lient/_client.py", line 105, in call response, content = Http().request(url, method, data, headers) File "/opt/mailman/mailman-bundler/eggs/httplib2-0.9.2-py2.7.egg/httplib2/__in it__.py", line 1609, in request (response, content) = self._request(conn, authority, uri, request_uri, metho d, body, headers, redirections, cachekey) File "/opt/mailman/mailman-bundler/eggs/httplib2-0.9.2-py2.7.egg/httplib2/__in it__.py", line 1351, in _request (response, content) = self._conn_request(conn, request_uri, method, body, he aders) File "/opt/mailman/mailman-bundler/eggs/httplib2-0.9.2-py2.7.egg/httplib2/__in it__.py", line 1307, in _conn_request response = conn.getresponse() File "/usr/lib/python2.7/httplib.py", line 1051, in getresponse response.begin() File "/usr/lib/python2.7/httplib.py", line 415, in begin version, status, reason = self._read_status() File "/usr/lib/python2.7/httplib.py", line 379, in _read_status raise BadStatusLine(line) BadStatusLine: '' [25/Apr/2016 06:21:10] "GET /mailman3/lists/ HTTP/1.1" 500 121854 Any ideas? Kind regards Simon ******************************************************************************************************************** This message may contain confidential information. If you are not the intended recipient please inform the sender that you have received the message in error before deleting it. Please do not disclose, copy or distribute information in this e-mail or take any action in reliance on its contents: to do so is strictly prohibited and may be unlawful. Thank you for your co-operation. NHSmail is the secure email and directory service available for all NHS staff in England and Scotland NHSmail is approved for exchanging patient data and other sensitive information with NHSmail and GSi recipients NHSmail provides an email address for your career in the NHS and can be accessed anywhere ********************************************************************************************************************

2 1

[MM3-users]mailman 2 vs. mailman 3: what happened to multipart/digest?
by John Hein May 14, 2016

May 14, 2016

Digest delivery in mailman 2 encapsulated the individual message/rfc822 messages in a multipart/digest container. This allowed email clients to show the messages in the particular digest in a threaded view. It seems like the various digest options that I have tried [1] in mailman 3.1.0 (as implemented for the fedora-users mailing list) no longer encapsulate messages in multipart/digest. Is this intentional? Is it a bug - feature that was lost in translation from 2 to 3? Is there a delivery option I'm missing that will turn that back on? [1] Mime Digests & Summary Digests - I didn't see any difference for those two options. Here is a sample of mime types that I used to get with mime digest delivery in mailman 2 (notice the multipart/digest): Content-Type: multipart/mixed; boundary="===============1472225091712365472==" Content-Type: text/plain; charset="utf-8" Content-Type: text/plain; charset="utf-8" Content-Type: multipart/digest; boundary="===============6619260109017411105==" Content-Type: message/rfc822 Content-Type: text/plain; charset=US-ASCII Content-Type: message/rfc822 Content-Type: text/plain; charset="UTF-8" Content-Type: message/rfc822 Content-Type: text/plain; charset="utf-8"; format=flowed Content-Type: message/rfc822 Content-Type: multipart/alternative; boundary=001a11c3cab0b7b2d5052f6fcd1e Content-Type: text/plain; charset=UTF-8 Content-Type: text/html; charset=UTF-8 Content-Type: message/rfc822 Content-Type: text/plain; charset=UTF-8 . . Content-Type: text/plain; charset="utf-8"

4 12

[MM3-users]Sass and where to find core rest logs
by Andrew Hodgson May 5, 2016

May 5, 2016

Hi guys, Finally got a server I can mess about with MM3 on. Only took a year :(! Anyway, I have compiled Mailman3, and the web interface is coming up. Bringing up the list of lists initially gave me an exception, and I saw a 5xx error in the mailman.log file in /opt/mailman/var/logs. I read up on this and as a result downgraded Falcon<1.0 in the Python 3.4 venv. I am still unable to browse the list of lists with a 500 error, only this time I am not getting an entry in the mailman.log indicating there is an issue, and I am wondering if there are more detailed logs that can be switched on? The other question I have is on Sassc. I believe the default Mailman web interface has now switched to the Ruby implementation of Sass, but is this correct? The documentation on the Mailman-Bundler site seems to suggest that Sassc is still the default. Thanks, Andrew.

3 2

[MM3-users]Where to find core logs and Sass
by Andrew Hodgson May 5, 2016

May 5, 2016

Hi guys, Tried sending this via email but got NDR each time. Sending via web instead. Finally got a server I can mess about with MM3 on. Only took a year :(! Anyway, I have compiled Mailman3, and the web interface is coming up. Bringing up the list of lists initially gave me an exception, and I saw a 5xx error in the mailman.log file in /opt/mailman/var/logs. I read up on this and as a result downgraded Falcon<1.0 in the Python 3.4 venv. I am still unable to browse the list of lists with a 500 error, only this time I am not getting an entry in the mailman.log indicating there is an issue, and I am wondering if there are more detailed logs that can be switched on? The other question I have is on Sassc. I believe the default Mailman web interface has now switched to the Ruby implementation of Sass, but is this correct? The documentation on the Mailman-Bundler site seems to suggest that Sassc is still the default. Thanks, Andrew.

2 1