- Mailman-users - lists.mailman3.org

Mailman 3 Social Auth Configuration
by emonical＠misfitlabs.org 13 Oct '16

13 Oct '16

Hello. I am a new Mailman 3 user and have just gotten an environment configured using the Mailman bundler. The setup is almost complete, but, there's still Persona authorization. I was reading the your setup here from (https://wiki.list.org/DOC/Mailman%203%20installation%20experience) and was wondering if someone might have some insight as to how to remove the Persona log in to keep it locked down entirely to localized user registration.

2 1

Email commands
by Jean-Luc Wasmer 22 Sep '16

22 Sep '16

Hi, I wasn't able to find documentation about the currently support email commands for Mailman 3. The following command doesn't work for me (mailman bundler 3.0.0): subscribe address=$<$ADDRESS$>$ Will this be supported later on? Cheers, Jean-Luc

2 1

lists.mailman3.org web site.
by Mark Sapiro 30 Aug '16

30 Aug '16

I have just upgraded the lists.mailman3.org Mailman 3 installation to the heads of the GitLab mailman* branches. A major change is the switch from Persona to Django Allauth. This requires some configuration which isn't yet complete. Hopefully it will all be working very soon. In the mean time if you want to log in to Hyperkitty/Postorius you should be able to log in with your email address. The first time you do this, Mailman probably won't even know your password so you'll have to request a reset. Once you have reset your password, you should be able to log in. I hope to have several social auth choices working very soon. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 4

Mailman 3 Installation Packaging
by ddw David Wilson 30 Aug '16

30 Aug '16

Salutations; I understand that work is in progress to provide a convenient installation tool to facilitate getting the suite of requisite programs installed and working harmoniously with a minimum of hassle? I assume that involves some combination of containers and/or virtual environments to insulate and isolate issues and facilitate portability. In addition, it would entail Mailman 3, Hyperkitty, Posterius and also Django, etc. The database selection of PostgreSQL or other. Other optionals to be configured would be the email utilities such as Postfix, etc Personally, my server of choice would run Centos. I gather Mark Sapiro was working on this as well? *Is there sufficient progress to warrant believing that such a capability might exist in the 2016 August - September time frame as was suggested some time back? Or are there any revised time-frames? Or an approximate estimated road-map?* Best regards. Dave Wilson

2 1

Mailman3 in AWS
by Andrew Hodgson 23 Aug '16

23 Aug '16

Hi Guys, Just looking at options for running Mailman3 in AWS. Here are some thoughts: - DB backend can be done in AWS RDS using Amazon Aurora DB with MySQL driver, or PostgreSQL. - What files (if any) get stored on the web servers and updated dynamically? Has load balancing been done for the websites before? - Any issues with runner processes being ran on more than one machine talking to the same DB backend? Just some initial thoughts to stem discussion. Andrew.

3 2

Broken paths
by Jean-Luc Wasmer 22 Aug '16

22 Aug '16

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 20 Aug '16

20 Aug '16

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 02 Aug '16

02 Aug '16

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 31 Jul '16

31 Jul '16

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 13 Jul '16

13 Jul '16

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 11 Jul '16

11 Jul '16

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 05 Jul '16

05 Jul '16

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 01 Jun '16

01 Jun '16

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 31 May '16

31 May '16

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 27 May '16

27 May '16

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) 17 May '16

17 May '16

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 14 May '16

14 May '16

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 05 May '16

05 May '16

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 05 May '16

05 May '16

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

[MM3-users]Moderation Emails & Page
by Douglas R Taber 21 Apr '16

21 Apr '16

Hey All- Having a bit of a problem, hoping maybe someone can provide some insight. I’m running the current MM3 from the bundler on RHEL7, and most things seem to be working properly. However, when i go to the moderation queue from the web interface, i’m presented with a 500 error instead of a page listing the messages being held. The error in the log (and on the page if i enabled debug) is: ERROR 2016-04-20 14:58:05,959 base 3256 140375419246336 Internal Server Error: /mailman3/lists/listname/held_messages Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/django/core/handlers/base.py", line 132, in get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python2.7/site-packages/django/contrib/auth/decorators.py", line 22, in _wrapped_view return view_func(request, *args, **kwargs) File "/usr/lib/python2.7/site-packages/postorius/auth/decorators.py", line 77, in wrapper return fn(*args, **kwargs) File "/usr/lib/python2.7/site-packages/postorius/views/list.py", line 413, in list_moderation paginator_class=utils.MailmanPaginator) File "/usr/lib/python2.7/site-packages/postorius/utils.py", line 89, in paginate results = paginator.page(1) File "/usr/lib/python2.7/site-packages/postorius/utils.py", line 62, in page number = self.validate_number(number) File "/usr/lib/python2.7/site-packages/django/core/paginator.py", line 39, in validate_number if number > self.num_pages: File "/usr/lib/python2.7/site-packages/django/core/paginator.py", line 86, in _get_num_pages if self.count == 0 and not self.allow_empty_first_page: File "/usr/lib/python2.7/site-packages/postorius/utils.py", line 75, in _get_count result = self.function(count=1, page=1) File "/usr/lib/python2.7/site-packages/mailmanclient/_client.py", line 681, in get_held_page return Page(self._connection, url, HeldMessage, count, page) File "/usr/lib/python2.7/site-packages/mailmanclient/_client.py", line 333, in __init__ self._create_page() File "/usr/lib/python2.7/site-packages/mailmanclient/_client.py", line 363, in _create_page self._connection, entry['self_link'], entry) KeyError: u’self_link' Anyone have any insight on what be causing the error? Thus far it only seems to be this page that is causing the issue, and only when messages are actually being held in the moderation queue. Semi-related, is there anyway to include the link to the moderation page from the moderation emails, similar to MM2? Thanks.

2 1

[MM3-users]Installation issues
by Hellings Simon (EAST KENT HOSPITALS UNIVERSITY NHS FOUNDATION TRUST) 20 Apr '16

20 Apr '16

Hi folks I was speaking to someone last night on the IRC chat room @ http://webchat.freenode.net/ who suggested sending an email to this address to try and find a solution to my issues. I have been trying to get Mailman 3 installed on an Ubuntu 14.04 server. I thought I had followed the instructions from https://wiki.list.org/DEV/Mailman%203.0/Mailman%203.0%20Suite%20Install%20o… and http://mailman-bundler.readthedocs.org/en/latest/ but am getting an error 500 when I try and browse to http://x.x.x.x:8000/mailman3. I can open http://x.x.x.x:8000/archives and the login button seems to work, but when I click manage lists I get an error 500 again. The entire process I followed is below: * sudo apt-get update * sudo apt-get install git python3-dev python3-pip python-dev python-pip python-virtualenv * sudo apt-get install nodejs npm * sudo npm install -g less * sudo ln -s /usr/bin/nodejs /usr/bin/node * created new user 'mailmanuser' * 'mkdir /opt/mailman' * 'sudo chown mailmanuser:mailmanuser mailman' * 'su mailman' * 'cd /opt/mailman' * git clone https://gitlab.com/mailman/mailman-bundler.git * virtualenv -p /usr/lib/python2.7 venv * source venv/bin/activate * changed password in mailman_web/testing.py * cd mailman-bundler * pip install zc.buildout * buildout * sudo apt-get install ruby-sass * ./bin/mailman-post-update * ./bin/mailman-web-django-admin createsuperuser * ./bin/mailman start * ./bin/mailman-web-django-admin runserver 0.0.0.0:8000 I have attached the django and mailman logs and the top of the page I get back from the server I must have missed something but I don't really know where to go from here... Please can you review and advise if there is anything that I have missed? I look forward to hearing from you in due course. Any pointers greatly received. 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 ********************************************************************************************************************

5 7

[MM3-users]Subscribing via email
by Andrew Hodgson 19 Apr '16

19 Apr '16

Hi, I subscribed to this list the other day via email, and I didn't get any email back suggesting I was subscribed. I logged in today via Google accounts, and it said I was subscribed to the list, but all the options for receiving list traffic, my own posts etc weren't filled in - I had to fill them in manually. Is something up here? Thanks. Andrew.

3 2

[MM3-users]We are being mirrored on Gmane
by Barry Warsaw 17 Apr '16

17 Apr '16

This should be the first post that gets mirrored to Gmane. -Barry

2 1

[MM3-users]Incorrect URLs
by Mark Sapiro 06 Apr '16

06 Apr '16

There are various URLs exposed in various emails from the list, many of which are wrong. The underlying issue is there are generic replacements such as $listinfo_uri and $user_options_uri in various templates such as the welcome.txt list welcome message and the footer-generic.txt message and digest footer. Now that the Mailman 3 core engine has been separated from the web UI, the core doesn't know what these replacements should be and there is not yet an interface to get them from Postorius or whatever the web UI is. In the mean time, I have made list specific versions of welcome.txt (done before announcing the list) and footer-generic.txt (just now) with the correct URLs hard coded. The purpose of this post is two-fold. To explain the issue, and to test the footer. There are probably more of these incorrect replacements and I will fix them as I notice them or they are pointed out to me. Note that I am aware that the https URLs in the List-Subscribe: and List-Unsubscribe: headers added to posts are wrong, but I haven't got a handle on this yet. The mailto: links in those headers are correct as are the Archived-At: and List-Archive: URLs as there is an interface to get those from the archiver. -- 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]New Mailman 3 users list
by Mark Sapiro 06 Apr '16

06 Apr '16

I'm happy to announce a new list for Mailman 3 users and others interested in Mailman 3. This list is running on a new Mailman 3 installation at lists.mailman3.org. The list's posting address is <mailman-users(a)mailman3.org>. The list's info page is <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> and its archives are at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/>. The top level Postorius page is <https://lists.mailman3.org/mailman3/> and the HyperKitty archiver is at <https://lists.mailman3.org/archives/>. You can subscribe by email by sending a blank message to <mailman-users-join(a)mailman3.org> and responding to the resulting confirmation request. You can also subscribe by going to the info page at <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/>, logging in and subscribing. Log in offers three options. There are Google and Facebook OAuth2 login links on the log in page to log in with a Google or Facebook account, and there is a 'Login by email' link to login via Persona with any address you register and confirm with Persona. This is a new installation of Mailman 3 so there are still kinks to work out, and any issues can be discussed on the list or reported to the trackers at <https://gitlab.com/mailman/postorius/issues>, <https://gitlab.com/mailman/hyperkitty/issues> or <https://gitlab.com/mailman/mailman/issues> as appropriate. Enjoy! -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 3

[Mailman-users] Initial post
by Mark Sapiro 05 Apr '16

05 Apr '16

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

1 0