- Mailman-users - lists.mailman3.org

[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

[MM3-users]Moderation Emails & Page
by Douglas R Taber April 21, 2016

April 21, 2016

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) April 20, 2016

April 20, 2016

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 April 19, 2016

April 19, 2016

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 April 17, 2016

April 17, 2016

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

2 1

[MM3-users]Incorrect URLs
by Mark Sapiro April 6, 2016

April 6, 2016

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 April 6, 2016

April 6, 2016

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