- Mailman-users - lists.mailman3.org

Users, members, accounts and subscribers
by Cameron Smith Aug. 24, 2017

Aug. 24, 2017

Oh my! In an attempt to introduce a friend to MailMan3, I had her subscribe to a couple of lists that I set up and we exchanged a few messages via the email interface. Then I introduced her to the web interface and we were both confused when she could not log-in/sign-in and was told that her email address was not recognized. It was only later that I realized that while she was a subscriber, she hadn’t yet signed up for an account. What is the point of “accounts"? Why can someone become a subscriber, but not have an account? I find the user/member/subscriber explanation at http://mailman.readthedocs.io/en/latest/src/mailman/docs/architecture.html to be very confusing. Cameron Smith

3 3

Setting default Mailman admin (Django superuser) password in Docker-mailman
by Henrik Rasmussen Aug. 23, 2017

Aug. 23, 2017

I just upgraded to Docker-mailman 0.1.1 and prior to that for some reason I had to somewhat start over, deleting my database. At both on my first and second attempt I wondered what the Django admin password would be. According to https://github.com/maxking/docker-mailman/ and https://github.com/maxking/docker-mailman/blob/master/web/README.md, setting MAILMAN_ADMIN_USER and MAILMAN_ADMIN_EMAIL in docker-compose.yaml will create a username for the admin user by default, but it doesn't mentioning setting a variable for the password. Creating a superuser using docker exec -it mailman-web python manage.py createsuperuser would normally request the password for the user indicated, but user "mailman" has already been registred. So to get to know the superuser password, I reset it using https://stackoverflow.com/questions/6358030/how-to-reset-django-admin-passw…. Why don't the installation guide on https://github.com/maxking/docker-mailman/ mention anything about how to set the password in the docker-compose.yaml file? -- Henrik Rasmussen <her(a)adm.ku.dk<mailto:her@adm.ku.dk>> Copenhagen, Danmark

2 1

Possible bug in Mailman 3.1 (Docker-mailman 0.1)
by Henrik Rasmussen Aug. 21, 2017

Aug. 21, 2017

Mailman 3.1, docker-mailman 0.1 While I was trying to automate distribution of the files in /opt/mailman/core/var/data/postfix_domains I found what I think must be a bug. Adding a new mail list (or deleting one) _does_ update the Postfix files /opt/mailman/core/var/data/ ,but adding a new mail domain does not. This is OK. But deleting a mail domain that have lists associated to it * does not issue a warning other than "Are you sure you want to permanently delete this domain?" which is not different from deleting mail domains without lists associated to it. * the associated lists disappears both from the web interface Lists view and from the output of the "docker exec -it mailman-core mailman lists" command * the files in /opt/mailman/core/var/data/ is not updated even the lists is being deleted. 1. Deleting a mail domain with associated lists should issue a warning that it has lists associated to it. 2. The files in /opt/mailman/core/var/data/ should be updated according to the deleted lists / domains. 3. Actually I think it should be impossible to accidentally delete a mail domain with lists associated to it. Regards Henrik Rasmussen

2 2

Re: Which documentation to follow for installation
by Ruben Ibanez Aug. 20, 2017

Aug. 20, 2017

Hi Abhilash, Thanks for your reply. The point is, I think I'm missing something. I'm just a sysadmin who wants to deploy Mailman 3.x to be used for an operational environment, like any other software. Is this software actually ready for that? Of course, I'm not asking for .rpm, .deb, etc... because I understand that's quite complex, but I tried it following all available guides, including the Contributor's Guide, and it seems impossible to get it running at the first time (or just to get it running) without getting crazy or fixing lots of unexpected errors during installation. Have you tried to deploy Mailman 3.x strictly following the documentation? By the way, many thanks for your hard work! Cheers, RI From: "Abhilash Raj" <maxking(a)asynchronous.in> To: ribanez(a)sciops.esa.int Cc: mailman-users(a)mailman3.org Sent: Saturday, August 19, 2017 8:55:20 AM Subject: Re: [MM3-users] Which documentation to follow for installation On Fri, 18 Aug 2017 09:40:37 -0000 ribanez(a)sciops.esa.int wrote: > Hi everyone, > > I'm trying to deploy Mailman 3.1, but it seems there isn't a clear place to > look for documentation. I found two different sites: > > https://mailman.readthedocs.io/en/latest/ > http://docs.mailman3.org/en/latest/ Both of the above are actually latest documentation, docs.mailman3.org should be the one to look for installations guidelines for the entire Mailman 3.x Suite, mailman.readthedocs.io is the documentation of Mailman 3 Core, which handles the mail. http://docs.mailman3.org/en/latest/prodsetup.html This should be the best place to start, be sure to look at the Pre-Installation Guide if you are new to the Python ecosystem. > > Do you know which one should be followed? Both at the same time? I find it > quite unclear... and this installation will be for an operational environment. > > Also, there are some (official?...) docker images, but all images are for > mailman 3.0 but not mailman 3.1, and of course updates are not guaranteed. It is meant for Mailman 3.X series and is maintained by me. It currently includes the latest releases for all the Mailman's sub-projects, also Mailman 3.1. Hope that helps! -- thanks, Abhilash Raj This message and any attachments are intended for the use of the addressee or addressees only. The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its content is not permitted. If you received this message in error, please notify the sender and delete it from your system. Emails can be altered and their integrity cannot be guaranteed by the sender. Please consider the environment before printing this email.

2 1

Which documentation to follow for installation
by ribanez＠sciops.esa.int Aug. 19, 2017

Aug. 19, 2017

Hi everyone, I'm trying to deploy Mailman 3.1, but it seems there isn't a clear place to look for documentation. I found two different sites: https://mailman.readthedocs.io/en/latest/ http://docs.mailman3.org/en/latest/ Do you know which one should be followed? Both at the same time? I find it quite unclear... and this installation will be for an operational environment. Also, there are some (official?...) docker images, but all images are for mailman 3.0 but not mailman 3.1, and of course updates are not guaranteed. Thanks in advance! Regards, ribanez

2 1

Issues with starting mailman 3 outside of a virtualenv
by Leon Aug. 16, 2017

Aug. 16, 2017

Hello, I wonder if this issue(https://gitlab.com/mailman/mailman/issues/3) was fixed? I try to set up a mailing list on aws ec2(ubuntu). In the instruction( http://docs.mailman3.org/en/latest/prodsetup.html) it doesn't require to install mailman in a virtual env. However, when I tried to run `mailman start`, it produces `/usr/bin/python3: can't open file '/usr/bin/master': [Errno 2] No such file or directory`. -- Best wishes, Leon

3 5

Mailman3 on FreeBSD
by John Poltorak Aug. 14, 2017

Aug. 14, 2017

I'm trying to install Mailman3 on FreeBSD using http://docs.mailman3.org/en/latest/prodsetup.html The install runs but 'mailman info' returns errors. Can anyone suggest where I should look to get this sorted out?

6 13

Postgresql
by John Poltorak Aug. 13, 2017

Aug. 13, 2017

What is involved in setting up Postgres to store Mailman msgs?

2 1

Mailman home
by John Poltorak Aug. 13, 2017

Aug. 13, 2017

I'm still in my early stages of getting Mailman 3 up and running, and am still not sure how and where it should be installed, but what I've noticed is that the Mailman subdirectory tree gets install in the current directory when running 'mailman list'... Is that would should happen?

2 1

hyperkitty won't list more than 5 posts and shows empty grey Activity Summary box
by Cyprian Laskowski Aug. 11, 2017

Aug. 11, 2017

Hi, On our new installation of Mailman 3, which seems to be otherwise working fine (thanks!), the "More..." link doesn't work, such that the list continues to only show 5 posts, even though it's clear that hyperkitty is aware of more (if I click on August, for example). Also, nothing is shown in the grey box under Activity Summary (the <svg class="chart-data"> element), although I'm not sure what's supposed to be shown there. The public archived list is here: http://seznami.cjvt.si/hyperkitty/list/test@seznami.cjvt.si/. I'd appreciate any pointers. Regards, Cyprian

5 9

Mailman3 on FreeBSD
by John Poltorak Aug. 11, 2017

Aug. 11, 2017

Has anyone managed to install Mailman 3 on FreeBSD?

2 2

Telling Mailman/Hyperkitty where sass is
by Erin Justice Aug. 11, 2017

Aug. 11, 2017

Hi all, Another issue that's cropped up when I am trying to run Mailman 3 on apache. I've downloaded and installed Mailman core, Django, Postorius & Hyperkitty. I'm using the mailman-suite django project from https://gitlab.com/mailman/mailman-suite/tree/master <https://gitlab.com/mailman/mailman-suite/tree/master>. When I run the site using Django's development server everything works. However when I run the site from apache it's not finding sass. Specifically I'm getting errors like: FilterError at /accounts/login/ /bin/sh: sass: command not found I triple checked that sass is installed which sass /Applications/MAMP/Library/bin/sass /Applications/MAMP/Library/bin/ is in $PATH when I checked that and I was thinking that it maybe wasn't getting to python properly. However pprint(sys.path) contains the same items whether I start the site from the dev server or apache. Any pointers would be appreciated. -Erin

4 3

Mailman container images v0.1.1
by Abhilash Raj Aug. 10, 2017

Aug. 10, 2017

Hi All, Version 0.1.1[1] of the container images are now available for download. There are several new changes that make working with the container easier. Please have a look at the release notes[1] for upgrading to this version. Most notable changes are: * Now you MUST specify SECRET_KEY environment variable that Django uses. The default value was removed to make sure people set a different value for each installation * Hyperkitty has been updated to latest 1.1.1 release * Mailman-web image has been moved to alpine 3.6 base image form Debain The NEWS[2] contains an exhaustive list of all the changes that has gone into this release. Thanks to all the contributors who contributed patches and reported issues for this new release! [1]: https://github.com/maxking/docker-mailman/releases/tag/v0.1.1 [2]: https://asynchronous.in/docker-mailman/NEWS.html -- thanks, Abhilash Raj

4 5

Typo in List Creation screen
by Henrik Rasmussen Aug. 10, 2017

Aug. 10, 2017

There is a typo in the list creation screen in Mailman 3. The owner's address field says "Inital list owner address", which should be "Initial" with an extra 'i'. Regards Henrik Rasmussen

2 1

Setup Mailman 3 using Apache/Mod_WSGI
by Erin Justice Aug. 8, 2017

Aug. 8, 2017

Hi all, I'm trying to setup Mailman 3 to run using apache. I've downloaded and installed mailman core, django, Postorius & Hyperkitty I'm using the mailman-suite django project from https://gitlab.com/mailman/mailman-suite/tree/master <https://gitlab.com/mailman/mailman-suite/tree/master>. When I run the site using Django's development server everything works. However I've been unsuccessful in getting the site to run via apache w/ Mod_WSGI. Note: I have a number of virtual hosts setup for various PHP sites and am trying to add the mailman install as another virtual host. I'm using MAMP for managing my website setup on my local machine. The addition to the virtual hosts file is: <VirtualHost *:80> #Mailman3 stuff ServerName mailman.local Alias /static /Applications/MAMP/Library/lib/python2.7/site-packages/mailman-suite/mailman-suite_project/static <Directory "/Applications/MAMP/Library/lib/python2.7/site-packages/mailman-suite/mailman-suite_project/static"> Order deny,allow Allow from all </Directory> WSGIScriptAlias / /Applications/MAMP/Library/lib/python2.7/site-packages/mailman-suite/mailman-suite_project/wsgi.py <Directory "/Applications/MAMP/Library/lib/python2.7/site-packages/mailman-suite/mailman-suite_project"> <Files wsgi.py> Order deny,allow Allow from all </Files> </Directory> </VirtualHost> I also have the following in my https.conf. WSGIPythonPath /Applications/MAMP/Library/lib/python2.7/ The 500 and related Errors I'm getting in Apache are: [Thu Aug 03 14:18:55 2017] [info] mod_wsgi (pid=80044): Create interpreter 'mailman.local|'. [Thu Aug 03 14:18:55 2017] [info] mod_wsgi (pid=80044): Adding '/Applications/MAMP/Library/lib/python2.7/' to path. [Thu Aug 03 14:18:55 2017] [info] [client ::1] mod_wsgi (pid=80044, process='', application='mailman.local|'): Loading WSGI script '/Applications/MAMP/Library/lib/python2.7/site-packages/mailman-suite/mailman-suite_project/wsgi.py'. [Thu Aug 03 14:18:55 2017] [error] [client ::1] mod_wsgi (pid=80044): Target WSGI script '/Applications/MAMP/Library/lib/python2.7/site-packages/mailman-suite/mailman-suite_project/wsgi.py' cannot be loaded as Python module. [Thu Aug 03 14:18:55 2017] [error] [client ::1] mod_wsgi (pid=80044): Exception occurred processing WSGI script '/Applications/MAMP/Library/lib/python2.7/site-packages/mailman-suite/mailman-suite_project/wsgi.py'. [Thu Aug 03 14:18:55 2017] [error] [client ::1] Traceback (most recent call last): [Thu Aug 03 14:18:55 2017] [error] [client ::1] File "/Applications/MAMP/Library/lib/python2.7/site-packages/mailman-suite/mailman-suite_project/wsgi.py", line 38, in <module> [Thu Aug 03 14:18:55 2017] [error] [client ::1] application = get_wsgi_application() [Thu Aug 03 14:18:55 2017] [error] [client ::1] File "/Applications/MAMP/Library/lib/python2.7/site-packages/django/core/wsgi.py", line 13, in get_wsgi_application [Thu Aug 03 14:18:55 2017] [error] [client ::1] django.setup(set_prefix=False) [Thu Aug 03 14:18:55 2017] [error] [client ::1] File "/Applications/MAMP/Library/lib/python2.7/site-packages/django/__init__.py", line 22, in setup [Thu Aug 03 14:18:55 2017] [error] [client ::1] configure_logging(settings.LOGGING_CONFIG, settings.LOGGING) [Thu Aug 03 14:18:55 2017] [error] [client ::1] File "/Applications/MAMP/Library/lib/python2.7/site-packages/django/conf/__init__.py", line 56, in __getattr__ [Thu Aug 03 14:18:55 2017] [error] [client ::1] self._setup(name) [Thu Aug 03 14:18:55 2017] [error] [client ::1] File "/Applications/MAMP/Library/lib/python2.7/site-packages/django/conf/__init__.py", line 41, in _setup [Thu Aug 03 14:18:55 2017] [error] [client ::1] self._wrapped = Settings(settings_module) [Thu Aug 03 14:18:55 2017] [error] [client ::1] File "/Applications/MAMP/Library/lib/python2.7/site-packages/django/conf/__init__.py", line 110, in __init__ [Thu Aug 03 14:18:55 2017] [error] [client ::1] mod = importlib.import_module(self.SETTINGS_MODULE) [Thu Aug 03 14:18:55 2017] [error] [client ::1] File "/Applications/MAMP/Library/lib/python2.7/importlib/__init__.py", line 37, in import_module [Thu Aug 03 14:18:55 2017] [error] [client ::1] __import__(name) [Thu Aug 03 14:18:55 2017] [error] [client ::1] ImportError: No module named settings Any thoughts would be greatly appreciated. Thank you, -Erin Justice

3 3

Docker, Mailman 3, templates and list user accounts
by Henrik Rasmussen Aug. 8, 2017

Aug. 8, 2017

I used Docker to installed Mailman 3. The top header of the web interface says "Example.Com" while linking to the correct site URL (I believe coming from SERVE_FROM_DOMAIN). In a post[1], Mark Sapiro referred to the template system in Mailman 3 by pointing out that "a custom template can be put in var/templates/site/en/welcome.txt or var/templates/domains/example.com/en/welcome.txt<http://var/templates/domains/example.com/en/welcome.txt> or var/templates/lists/listname.example.com/en/welcome.txt<http://var/templates/lists/listname.example.com/en/welcome.txt> where var is Mailman's configured var_dir". I believe this refers to the mail templates. 1) Where do I change the similar template system, for the web interface, without breaking a laver upgrade? 2) How do I change the site name in the top of the web interface on Mailman 3 to my subside and ? [1] https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… The Mailman command in Mailman Core doesn't seem to have a command for listing the accounts users have created by using Sign up in the web interface, so I believe that accounts may be created in the webinterface. Is there similar commands for the web interface like the mailman commands for the Mailman core? Regards, Henrik Rasmussen

3 3

config incoming email in my domain cpanel
by Rafael Mora Aug. 4, 2017

Aug. 4, 2017

Hello, I created a test list called: testlist1(a)labbrands.com How do I do in order to redirect the incoming emails to that direction to my server with MM3 ?? Thanks -- Atentamente / Best Regards Ing. Rafael Mora

5 24

Installing mailman 3
by Rafael Mora Aug. 2, 2017

Aug. 2, 2017

Hello, I want to install mailman 3 in a centos 7 virtual machine. I'm following these steps and I cannot make it work: 1. `cd ~` 2. `git clone https://gitlab.com/mailman/mailman.git` 3. `cd mailman` 4. `virtualenv -p python3 venv` 5. `source venv/bin/activate` 6. `python setup.py develop` 7. I am pretty sure this setup command will place a configuration file into `~/mailman/var/etc/mailman.cfg`. Edit this file. https://mailman.readthedocs.io/en/latest/src/mailman/config/docs/config.html 8. `mailman info` can confirm which configuration file is in use 9. `mailman start` will start up Mailman 3 Core. This is what the parent background process command looks like in `ps -ef`: `/home/ubuntu/mailman/venv/bin/python /home/ubuntu/mailman/venv/bin/master -C /home/ubuntu/mailman/var/etc/mailman.cfg` I also tried the steps on the website https://wiki.list.org/DEV/SetupDevEnvironment but it doesn't work either What do you suggest? This is what I get from console: [root@localhost ~]# cd dev/ [root@localhost dev]# cd mailman/ [root@localhost mailman]# source venv3/bin/activate (venv3) [root@localhost mailman]# cd mailman/ (venv3) [root@localhost mailman]# ls conf.py COPYING data README.rst src unittest.cfg contrib coverage.ini MANIFEST.in setup.cfg template.py copybump.py cron port_me setup.py tox.ini (venv3) [root@localhost mailman]# cd .. (venv3) [root@localhost mailman]# mailman start Starting Mailman's master runner /root/dev/mailman/venv3/bin/python: can't open file '/sbin/master': [Errno 2] No such file or directory (venv3) [root@localhost mailman]# Thank you -- Atentamente / Best Regards Ing. Rafael Mora

8 151

Ready to try installation: use "normal" install or docker.
by Tom Browder Aug. 1, 2017

Aug. 1, 2017

The mm3 installation instructions have been somewhat fluid over the development period, butI'm finally ready to dig in and give it a shot and need some last-minute advice. I'm leaning toward installing using the docker method but I would appreciate any recent thoughts about which method to choose. Thanks so much to the MM3 dev team! Best, -Tom

2 4

LMTP runner keeps crashing
by Mark Lindsay Aug. 1, 2017

Aug. 1, 2017

Hl mailman-users! The LMTP runner on my Mailman 3 install (3.1.0b4) has started silently crashing. The parent process and all of the other runners stay up. Nothing interesting seems to be written to the logs. I've been finding out about it when exim4 (running on the same server) starts sending out "retry timeout exceeded" bounce emails to list participants: From: Mail Delivery System [mailto:Mailer-Daemon@lists.mysite.org] > Sent: Monday, July 31, 2017 12:39 PM > To: some_participant(a)mysite.org > Subject: Mail delivery failed: returning message to sender > This message was created automatically by mail delivery software. > A message that you sent could not be delivered to one or more of its > recipients. This is a permanent error. The following address(es) failed: > listname(a)lists.mysite.org > retry timeout exceeded > Action: failed > Final-Recipient: rfc822;listname(a)lists.mysite.org > Status: 5.0.0 After hearing about the bounces from participants, I then SSH to the lists server and attempt to `telnet localhost 8024` but get no response. The LMTP runner is not listed in `ps -ef`. After restarting all of mailman (`mailman stop; mailman start`) I get the `220` response from LMTP on port 8024. I see the LMTP runner in `ps -ef`. Does anyone have any ideas on how I could start debugging this? Thank you, Mark

2 1

Installation guide
by Loring July 31, 2017

July 31, 2017

So I am looking to install the latest mailman 3, however I can find no complete guide as to how to install it. I have found some pages for instance http://mailman.readthedocs.io/en/latest/src/mailman/docs/install.html# This however gives me no instructions on how to install mailman3.x, can anyone point me in the righ direction please. -- Richmond Loring rloring(a)bnl.gov Advanced Systems Engineer

2 1

MM3 statistics
by Tom Browder July 28, 2017

July 28, 2017

Are there any plugins or programs for mm3 statistics? Thanks. -Tom

3 4

Mailman 3 Status Update Please?
by ddw David Wilson July 26, 2017

July 26, 2017

Mailman 3 Status Update Please I have been following the progress and difficulties with great interest as many struggle to implement the new version of the great Mailman 3 list-server software. Last year about this time I posed some questions regarding the current development status and recognize that many additional problems seem to get in the way of actually working on long term big picture issues. From my perspective of being an senior (ie overaged) person desirous of implementing fully-featured, capable, scalable, reliable, secure applications such as Mailman, I am convinced that I am thoroughly over my head. From my limited perspective, it would seem to me that a 'nice to have' system would incorporate the following. 1. An open container standard configurable system install, compatible with different web & mail servers, DB utilities, etc; 2. Python 3 version Django utilities for archiving and mail list name management; 3. A design/plan from an inside expert perspective stating costs, time and resources to implement the plan, incorporating crowdfunding to pay for project. 4. As a backup incentive to the crowdfunding plan might be the offer of an expert to set up a system for each significant amount donated, say US$1,000, such as might be accomplished by an SSL session on the target computer/server after the user has specified all necessary detail as required in a template. I am sure that the program author and other major contributors could greatly enhance this list. In summary, I guess what I am requesting is an overview forecast by half year period and out for the next two years? Please share the big picture? Thank you in advance and best regards. Dave Wilson

6 7

MM3.1 templates
by Matt Richards July 20, 2017

July 20, 2017

I've managed, to setup MM3.1 using the docker images from http://github.com/maxking/docker-mailman. I would like to start customizing the templates MM3.1 uses for the footer and confirmation emails. Is there any mailman site admin or list admin documentation on how to customize email templates in MM3.1? I've found this template doc at https://gitlab.com/mailman/mailman/tree/master/src/mailman/rest/docs, but I'm not clear how this works.. and it appears postorius doesn't have template support yet? I am new to python and django.. -- --Matt

2 1

AH01102: error reading status line from remote server 172.19.199.3:8000
by Henrik Rasmussen July 20, 2017

July 20, 2017

I've just installed Mailman 3.1 on RHEL7 (Docker-Mailman3) and to get the right CSS layout I installed Apache on the Mailman server outside Docker, as advised by Abhilash Raj and Alexander Klotz. My Mailman server is on a secured network and the https connection from Internet will be handled by proxy servers, so I will be using http (port 80) between proxy-servers and Mailman server. But when I sign in (currently via an SSH tunnel to the Mailman server from my workstation) I get "Internal error: [client ::1:41912] AH01102: error reading status line from remote server 172.19.199.3:8000, referer: http://localhost/accounts/login/?next=%2Fpostorius%2Flists%2F" If I type a wrong password, I am just warned about that, so the problem appears when log in is accepted. I expect that it is because I connect to localhost:80 through SSH tunnel. What do I miss in my Apache configuration on the Mailman server to avoid this problem? <VirtualHost *:80> ErrorLog /var/log/httpd/error_log LogLevel warn CustomLog /var/log/httpd/access_log combined ServerAdmin root(a)example.foo ServerName list.foo.bar Alias /static /opt/mailman/web/static Alias /favicon.ico /opt/mailman/web/static/hyperkitty/img/favicon.ico ProxyPassMatch ^/static/.* ! ProxyPass / http://172.19.199.3:8000/ ProxyPassReverse / http://172.19.199.3:8000/ <Directory /> Allow from all Require all granted </Directory> <Directory /opt/mailman/web/static/hyperkitty/img/> Allow from all Require all granted </Directory> # ssl config here ... </VirtualHost> Thanks, Henrik Rasmussen

2 3

List of "site admin" commands in Mailman 3.1 docker-mailman
by Henrik Rasmussen July 18, 2017

July 18, 2017

I am new to all of Python, Django, Docker, Docker-compose and everything else used by docker-mailman. I have managed to get a webinterface of Mailman 3.1, I installed using Docker and Docker-Compose from github.com/maxking/docker-mailman, but my config is still bogues (probably just my Apache-config). I'm quite confused about Mailman 3 documentation regarding those commands the site admin would do in Mailman 2 like list_members, config_list -o etc.)., and I have been trying to figure out what documentation regards the development of Mailman 3, what regards the final version 3.1 and what I am supposed to do regarding Docker. 1) Should I enter the container using "docker exec -it mailman-web bash" and run "python" in order to get a python prompt, and from there run commands like those documented at mailman.readthedocs.io/en/latest/src/mailman/commands/docs/control.html ?. 2) Where do I define the what was previously known as the site admin user and site admin e-mail? On another note: Is it a setting in the mailman-users(a)mailman3.org list setup that make each of my postings to the list come back with the note "This sender failed our fraud detection checks and may not be who they appear to be."? Thanks Henrik Rasmussen

4 3

Re: Found error in docker-container
by Abhilash Raj July 17, 2017

July 17, 2017

Hi Alex, On Wed, Jul 5, 2017, at 03:21 AM, Alexander Klotz wrote: > Hi, > > one of our developers wanted to point out an error he found in mailman > 3.1, docker container maxking/mailman-core-0.1 > > The entries in /opt/mailman/core/var/data/postfix_lmtp are not set > correctly, example: > > /^testlist(a)mailman\.example\.com$/ lmtp:[172.19.199.2# IP > Address of mailman-core container]:8024 > > this actually should look like this: > > /^testlist(a)mailman\.example\.com$/ lmtp:[172.19.199.2]:8024 Can you send a copy of your Mailman configuration that you added at `/opt/mailman/core/mailman-extra.cfg`? I think this is mostly because the configuration parser doesn't understand the in-line comments. So, if you are using the configuration exactly as it is mentioned in the documentation, it could be the cause of this problem. Solution to that would be to just remove all the in-line comments. [mta] incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: 172.19.199.2 # IP Address of mailman-core container lmtp_port: 8024 smtp_host: 172.19.199.1 # IP Address of host where postfix is. smtp_port: 25 configuration: /etc/postfix-mailman.cfg Like the two comments seen in the configuration above. I will update the documentation too so that others don't get caught in something like this. Thanks! -- thanks, Abhilash Raj

2 4

postfix, dovecot and MM3
by Matt Richards July 15, 2017

July 15, 2017

This is a bit of a lengthy post, but I wanted to make sure I had enough detail to document the problem I'm experiencing. The quick summary is, I'm having a problem with postfix, dovecot and mailman3.. routing Problem: Postfix mail routing is mostly working correctly with the execpetion of handling test-confirm+157fcaf78907a2bbf21b36aaf349386e09e801a8(a)example.com emails. As you can see below in my postfix config, I have defined recipient_delimiter.. I'm not sure what else is going wrong.. For example, if I email test-confirm(a)example.com, the mail will route over to MM correctly as postfix is able to find this exact email address in the postfix_lmtp transport file. However, if I reply to a mm confirmaion email, test-confirm+157fcaf78907a2bbf21b36aaf349386e09e801a8(a)example.com, postfix will fail to deliver the email correctly due postfix trying to lookup the test-confirm(a)example.com in dovcot's virtual mailbox tables. I hope this is enough information... My research seems to indicate I might need to change something with virtual_alias_maps, however from my testing, changing this setting to include MM3's geneated postfix_lmtp file, it'll cause more problems.. I've also considered using a sub-domain, for example lists.example.com instead of my primary domain for mm3, this may fix a lot of my issues. Setup overview: Integrated mailcow-dockerized (https://github.com/andryyy/mailcow-dockerized) & docker-mailman (https://github.com/maxking/docker-mailman) - all I have done is merged the containers from the docker-mailman docker-compose.yml into mailcow's docker-compose.yml - updated the network settings for docker-mailman to use mailcow's internal network if needed, I can provide my docker-compose file. mx1.example.com = An internal eMail firewall and security server Below is the reject log from postfix: Jul 15 18:11:22 mx10 postfix/smtpd[418]: NOQUEUE: reject: RCPT from mx1.example.com[xxx.xxx.xxx.xxxx]: 550 5.1.1 < test-confirm+157fcaf78907a2bbf21b36aaf349386e09e801a8(a)example.com>: Recipient address rejected: User unknown in virtual mailbox table; from=< xxxx(a)gmail.com> to=< test-confirm+157fcaf78907a2bbf21b36aaf349386e09e801a8(a)example.com> proto=ESMTP helo=<mx1.example.com> Below is my postfix configs: ##Postfix main.cnf biff = no append_dot_mydomain = no smtpd_tls_cert_file = /etc/ssl/mail/cert.pem smtpd_tls_key_file = /etc/ssl/mail/key.pem smtpd_use_tls=yes smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache smtpd_relay_restrictions = permit_mynetworks permit_sasl_authenticated defer_unauth_destination alias_maps = hash:/etc/aliases alias_database = hash:/etc/aliases relayhost = [mx1.example.com]:25 mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128 10.0.0.0/8 172.16.0.0/12 192.168.0.0/16 [fd4d:6169:6c63:6f77::]/64 mailbox_size_limit = 0 recipient_delimiter = + inet_interfaces = all inet_protocols = all bounce_queue_lifetime = 1d broken_sasl_auth_clients = yes disable_vrfy_command = yes maximal_backoff_time = 1800s maximal_queue_lifetime = 1d message_size_limit = 26214400 milter_default_action = accept milter_protocol = 6 minimal_backoff_time = 300s plaintext_reject_code = 550 postscreen_access_list = permit_mynetworks, cidr:/opt/postfix/conf/postscreen_access.cidr, tcp:127.0.0.1:10027 postscreen_bare_newline_enable = no postscreen_blacklist_action = drop postscreen_cache_cleanup_interval = 24h postscreen_cache_map = proxy:btree:$data_directory/postscreen_cache postscreen_dnsbl_action = enforce postscreen_dnsbl_sites = b.barracudacentral.org=127.0.0.2*7 dnsbl.inps.de=127.0.0.2*7 bl.mailspike.net=127.0.0.2*5 bl.mailspike.net=127.0.0.[10;11;12]*4 dnsbl.sorbs.net=127.0.0.10*8 dnsbl.sorbs.net=127.0.0.5*6 dnsbl.sorbs.net=127.0.0.7*3 dnsbl.sorbs.net=127.0.0.8*2 dnsbl.sorbs.net=127.0.0.6*2 dnsbl.sorbs.net=127.0.0.9*2 zen.spamhaus.org=127.0.0.[10;11]*8 zen.spamhaus.org=127.0.0.[4..7]*6 zen.spamhaus.org=127.0.0.3*4 zen.spamhaus.org=127.0.0.2*3 hostkarma.junkemailfilter.com=127.0.0.2*3 hostkarma.junkemailfilter.com=127.0.0.4*1 hostkarma.junkemailfilter.com=127.0.1.2*1 wl.mailspike.net=127.0.0.[18;19;20]*-2 hostkarma.junkemailfilter.com=127.0.0.1*-2 postscreen_dnsbl_threshold = 8 postscreen_dnsbl_ttl = 5m postscreen_greet_action = enforce postscreen_greet_banner = $smtpd_banner postscreen_greet_ttl = 2d postscreen_greet_wait = 3s postscreen_non_smtp_command_enable = no postscreen_pipelining_enable = no proxy_read_maps = proxy:mysql:/opt/postfix/conf/sql/ mysql_virtual_sender_acl.cf, proxy:mysql:/opt/postfix/conf/sql/ mysql_tls_enforce_out_policy.cf, proxy:mysql:/opt/postfix/conf/sql/ mysql_tls_enforce_in_policy.cf, $local_recipient_maps $mydestination $virtual_alias_maps $virtual_alias_domains $virtual_mailbox_maps $virtual_mailbox_domains $relay_recipient_maps $relay_domains $canonical_maps $sender_canonical_maps $recipient_canonical_maps $relocated_maps $transport_maps $mynetworks $smtpd_sender_login_maps queue_run_delay = 300s relay_domains = proxy:mysql:/opt/postfix/conf/sql/ mysql_virtual_relay_domain_maps.cf relay_recipient_maps = proxy:mysql:/opt/postfix/conf/sql/ mysql_relay_recipient_maps.cf sender_dependent_default_transport_maps = proxy:mysql:/opt/postfix/conf/sql/ mysql_tls_enforce_out_policy.cf smtp_tls_CAfile = /etc/ssl/certs/ca-certificates.crt smtp_tls_cert_file = /etc/ssl/mail/cert.pem smtp_tls_key_file = /etc/ssl/mail/key.pem smtp_tls_loglevel = 1 smtp_dns_support_level = dnssec smtp_tls_security_level = dane smtpd_data_restrictions = reject_unauth_pipelining, permit smtpd_delay_reject = yes smtpd_error_sleep_time = 10s smtpd_hard_error_limit = ${stress?1}${stress:5} smtpd_helo_required = yes smtpd_proxy_timeout = 600s smtpd_recipient_restrictions = permit_sasl_authenticated, permit_mynetworks, check_recipient_access proxy:mysql:/opt/postfix/conf/sql/ mysql_tls_enforce_in_policy.cf, reject_invalid_helo_hostname, reject_unknown_reverse_client_hostname, reject_unauth_destination smtpd_sasl_auth_enable = yes smtpd_sasl_authenticated_header = yes smtpd_sasl_path = inet:dovecot:10001 smtpd_sasl_type = dovecot smtpd_sender_login_maps = proxy:mysql:/opt/postfix/conf/sql/ mysql_virtual_sender_acl.cf smtpd_sender_restrictions = reject_authenticated_sender_login_mismatch, permit_mynetworks, reject_sender_login_mismatch, permit_sasl_authenticated, reject_unlisted_sender, reject_unknown_sender_domain smtpd_soft_error_limit = 3 smtpd_tls_auth_only = yes smtpd_tls_dh1024_param_file = /etc/ssl/mail/dhparams.pem smtpd_tls_eecdh_grade = strong smtpd_tls_exclude_ciphers = ECDHE-RSA-RC4-SHA, RC4, aNULL smtpd_tls_loglevel = 1 smtp_tls_mandatory_protocols = !SSLv2, !SSLv3 smtp_tls_protocols = !SSLv2, !SSLv3 lmtp_tls_mandatory_protocols = !SSLv2, !SSLv3 lmtp_tls_protocols = !SSLv2, !SSLv3 smtpd_tls_mandatory_protocols = !SSLv2, !SSLv3 smtpd_tls_protocols = !SSLv2, !SSLv3 smtpd_tls_mandatory_ciphers = high smtpd_tls_security_level = may tls_ssl_options = NO_COMPRESSION tls_high_cipherlist = EDH+CAMELLIA:EDH+aRSA:EECDH+aRSA+AESGCM:EECDH+aRSA+SHA256:EECDH:+CAMELLIA128:+AES128:+SSLv3:!aNULL:!eNULL:!LOW:!3DES:!MD5:!EXP:!PSK:!DSS:!RC4:!SEED:!IDEA:!ECDSA:kEDH:CAMELLIA128-SHA:AES128-SHA transport_maps = regexp:/opt/mailman/core/var/data/postfix_lmtp local_recipient_maps = regexp:/opt/mailman/core/var/data/postfix_lmtp proxy:mysql:/opt/postfix/conf/sql/mysql_virtual_mailbox_maps.cf virtual_alias_maps = proxy:mysql:/opt/postfix/conf/sql/ mysql_virtual_alias_maps.cf, proxy:mysql:/opt/postfix/conf/sql/ mysql_virtual_spamalias_maps.cf, proxy:mysql:/opt/postfix/conf/sql/ mysql_virtual_alias_domain_maps.cf, proxy:mysql:/opt/postfix/conf/sql/ mysql_virtual_alias_domain_catchall_maps.cf virtual_gid_maps = static:5000 virtual_mailbox_base = /var/vmail/ virtual_mailbox_domains = proxy:mysql:/opt/postfix/conf/sql/ mysql_virtual_domains_maps.cf virtual_mailbox_maps = regexp:/opt/mailman/core/var/data/postfix_lmtp proxy:mysql:/opt/postfix/conf/sql/mysql_virtual_mailbox_maps.cf virtual_minimum_uid = 104 virtual_transport = lmtp:inet:dovecot:24 virtual_uid_maps = static:5000 smtpd_milters = inet:rspamd:9900 non_smtpd_milters = inet:rspamd:9900 milter_mail_macros = i {mail_addr} {client_addr} {client_name} {auth_authen} mydestination = localhost.localdomain, localhost #content_filter=zeyple # Prefere IPv4, useful for v4-only envs smtp_address_preference = ipv4 smtp_header_checks = pcre:/opt/postfix/conf/mailcow_anonymize_headers.pcre unknown_local_recipient_reject_code = 550 owner_request_special = no Note: I've replaced my real domain name with example.com, as I don't wish to have my server information publicly archived for spam and security reasons. I have also masked any external IP addreses. I'm also aware my email setup is a bit more complicated than the usual as I have an email firewall/security server in the mix. I've tried my best to accurately describe what I have configured. If you need any actual logs or configs, please contact me directly off this list for this information. -- --Matt

1 0

Does hyperkitty show JPEGs in line and what about attachments?
by Jason Glazer July 13, 2017

July 13, 2017

I run several MailMan 2.1 mailing lists and some subscribers are frustrated by the way pipermail deals with JPEGs that are embedded in the messages and also with how attachments are handled. Does hyperkitty in Mailman 3.1 do better on these issues. Assuming this message gets archived, I am going to try embedding a small picture right here: Hopefully that shows up in the archive. I won't add an attachment because the list may not allow it but I'm curious how those are handled. Thanks Jason -- Jason Glazer, P.E., BEMP, GARD Analytics, 90.1 ECB chair, 209 chair Admin for onebuilding.org building performance mailing lists

4 8

Docker Mailman3 installation frustration
by ccsmith＠cetsi.com July 13, 2017

July 13, 2017

I've been working on installing Mailman3 for several weeks now, with limited success. I have tried various installation methods following instructions on numerous different web pages. My experience has been that the instructions are often conflicting and never complete. My best success has been with the Docker version, so that's what I'm going to concentrate on here. I'm running Ubuntu 16.04 (under Citrix XenServer), with Apache httpd and postfix. Following the instructions on https://asynchronous.in/docker-mailman/, I did the following: * created the directories "/opt/mailman/core" and "/opt/mailman/web", * created "/opt/mailman/core/mailman-extra.cfg" and inserted the suggested [mta] directives, * inserted the "transport_maps", "local-recipient_maps", and "relay_domains" entries in the /etc/postfix/main.cf file, * created the necessary apache config files, * cloned "https://github.com/maxking/docker-mailman", * ran "docker-compose up -d" At this point, I am able to connect with Postorius. All of the text and icons show up properly; all is well. It tells me (correctly) that "There are currently no mailing lists." When I click on the "Login" link at the top right, the "Sign In" page displays correctly. (Aside: Why do so many apps/sites have difficulty with choosing between "login" and "sign in" and, in fact, use both terms? It can really be off-putting to non-tech users... and me.) If I input an incorrect login, I receive (correctly) the message "The username and/or password you specified are not correct." However, if I input the correct sign-in, I receive: "Server Error (500)". Running "sudo docker exec -it mailman-web cat ../mailman-web-data/logs/mailmanweb.log" shows me: ERROR 2017-07-12 20:34:25,073 25 django.request Internal Server Error: /accounts/login/ Traceback (most recent call last): File "/usr/local/lib/python2.7/site-packages/django/core/handlers/exception.py", line 39, in inner response = get_response(request) ... more stuff ... File "/usr/local/lib/python2.7/smtplib.py", line 747, in sendmail raise SMTPRecipientsRefused(senderrs) SMTPRecipientsRefused: {u'pacetechadmin(a)cetsi.com': (451, '4.3.0 <pacetechadmin(a)cetsi.com>: Temporary lookup failure')} On the Docker host (ubuntuServer2), /var/log/mail.log shows: Jul 12 13:48:53 ubuntuServer2 postfix/smtpd[19931]: error: open /opt/mailman/core/var/data/postfix_domains: No such file or directory Jul 12 13:48:53 ubuntuServer2 postfix/smtpd[19931]: error: open /opt/mailman/core/var/data/postfix_lmtp: No such file or directory Jul 12 13:48:53 ubuntuServer2 postfix/smtpd[19931]: connect from unknown[172.19.199.3] Jul 12 13:48:53 ubuntuServer2 postfix/trivial-rewrite[19843]: warning: regexp:/opt/mailman/core/var/data/postfix_domains is unavailable. open /opt/mailman/core/var/data/postfix_domains: No such file or directory Jul 12 13:48:53 ubuntuServer2 postfix/trivial-rewrite[19843]: warning: relay_domains: regexp:/opt/mailman/core/var/data/postfix_domains: table lookup problem Jul 12 13:48:53 ubuntuServer2 postfix/trivial-rewrite[19843]: warning: relay_domains lookup failure Jul 12 13:48:53 ubuntuServer2 postfix/trivial-rewrite[19843]: warning: regexp:/opt/mailman/core/var/data/postfix_domains is unavailable. open /opt/mailman/core/var/data/postfix_domains: No such file or directory Jul 12 13:48:53 ubuntuServer2 postfix/trivial-rewrite[19843]: warning: relay_domains: regexp:/opt/mailman/core/var/data/postfix_domains: table lookup problem Jul 12 13:48:53 ubuntuServer2 postfix/trivial-rewrite[19843]: warning: relay_domains lookup failure Jul 12 13:48:53 ubuntuServer2 postfix/smtpd[19931]: NOQUEUE: reject: RCPT from unknown[172.19.199.3]: 451 4.3.0 <pacetechadmin(a)cetsi.com>: Temporary lookup failure; from=<postorius(a)localhost.local> to=<pacetechadmin(a)cetsi.com> proto=ESMTP helo=<mailman-web> Jul 12 13:48:54 ubuntuServer2 postfix/smtpd[19932]: error: open /opt/mailman/core/var/data/postfix_domains: No such file or directory Jul 12 13:48:54 ubuntuServer2 postfix/smtpd[19932]: error: open /opt/mailman/core/var/data/postfix_lmtp: No such file or directory Jul 12 13:48:54 ubuntuServer2 postfix/smtpd[19932]: connect from unknown[172.19.199.3] Jul 12 13:48:54 ubuntuServer2 postfix/trivial-rewrite[19843]: warning: regexp:/opt/mailman/core/var/data/postfix_domains is unavailable. open /opt/mailman/core/var/data/postfix_domains: No such file or directory Jul 12 13:48:54 ubuntuServer2 postfix/trivial-rewrite[19843]: warning: relay_domains: regexp:/opt/mailman/core/var/data/postfix_domains: table lookup problem Jul 12 13:48:54 ubuntuServer2 postfix/trivial-rewrite[19843]: warning: relay_domains lookup failure Jul 12 13:48:54 ubuntuServer2 postfix/trivial-rewrite[19843]: warning: regexp:/opt/mailman/core/var/data/postfix_lmtp is unavailable. open /opt/mailman/core/var/data/postfix_lmtp: No such file or directory Jul 12 13:48:54 ubuntuServer2 postfix/trivial-rewrite[19843]: warning: regexp:/opt/mailman/core/var/data/postfix_lmtp lookup error for "root@localhost" Jul 12 13:48:54 ubuntuServer2 postfix/trivial-rewrite[19843]: warning: transport_maps lookup failure Jul 12 13:48:54 ubuntuServer2 postfix/smtpd[19932]: NOQUEUE: reject: RCPT from unknown[172.19.199.3]: 451 4.3.0 <root@localhost>: Temporary lookup failure; from=<root(a)localhost.local> to=<root@localhost> proto=ESMTP helo=<mailman-web> Jul 12 13:48:54 ubuntuServer2 postfix/smtpd[19932]: disconnect from unknown[172.19.199.3] ehlo=1 mail=1 rcpt=0/1 rset=1 quit=1 commands=4/5 Jul 12 13:48:54 ubuntuServer2 postfix/smtpd[19931]: lost connection after RSET from unknown[172.19.199.3] Jul 12 13:48:54 ubuntuServer2 postfix/smtpd[19931]: disconnect from unknown[172.19.199.3] ehlo=1 mail=1 rcpt=0/1 rset=1 commands=3/4 And /var/log/mail.err is filling up with: Jul 12 13:48:53 ubuntuServer2 postfix/smtpd[19931]: error: open /opt/mailman/core/var/data/postfix_domains: No such file or directory Jul 12 13:48:53 ubuntuServer2 postfix/smtpd[19931]: error: open /opt/mailman/core/var/data/postfix_lmtp: No such file or directory Jul 12 13:48:54 ubuntuServer2 postfix/smtpd[19932]: error: open /opt/mailman/core/var/data/postfix_domains: No such file or directory Jul 12 13:48:54 ubuntuServer2 postfix/smtpd[19932]: error: open /opt/mailman/core/var/data/postfix_lmtp: No such file or directory Any thoughts on what the problem is? Have I missed a step?

3 3

Confirm on mass subscription
by David Krantz July 7, 2017

July 7, 2017

Hi, Is there a way of requiring all mass subscribed users to confirm their email adress? I have an use case where we have a current mail list but when moving it to mailman I for different reasons would like to confirm all subscribers. Some very shallow testing suggests that if I just add them using mass subscribe, they will not have to confirm at all. I have yet to upgrade to 3.1 but I will do so in due time. cheers // David

3 2

Changing display name with "mailman withlist"
by Mark Ziranski July 5, 2017

July 5, 2017

Hello, I am looking for a way to change the display name of a mailing list on command line. As written in "mailman withlist --details" I have created a script named "change.py". When executing the script as written in the manual, I get the following error: (venv-3.5) [root@localhost mailman]# mailman withlist -r change example(a)example.org 'new display name' usage: mailman [-h] [-v] [-C CONFIG] {help,aliases,conf,create,digests,import21,info,inject,lists,members,qfile,remove,reopen,restart,shell,start,status,stop,unshunt,version,withlist} ... mailman: error: unrecognized arguments: new display name According to the manual it should be possible to pass arguments in withlist: mailman withlist [options] listname [args ...] while " mailman withlist -h" says: usage: mailman withlist [-h] [-i] [-r RUN] [--details] [LISTNAME] Mailman version: GNU Mailman 3.2.0a1 (La Villa Strangiato) Btw. I know that there is an interactive shell to execute the script but I need a solution that can be run in a shell script. Thank you.

2 1

Problem with docker and css
by Alexander Klotz July 5, 2017

July 5, 2017

Hi everyone, we are experiencing some issues trying to run mailman3 on our server. First, when starting docker-compose up -d the mailman-web container is not started. The log shows: mailman-web | useradd: user 'mailman' already exists If we start the container with docker-compose up (without -d), all containers start accurately. Are there other files integrated / processed when starting docker-compose up with -d? Secondly, no css and javascript-elements, as well as images are embedded in the web surface. In the mailman-web log we can see they aren't found (Error 404), but trying with docker-compose exec -T mailman-web ls /opt/mailman-.../static/.../... they actually can be found. Can anybody tell me why these problems appear and how to solve them? Any help would be highly appreciated. Thanks & Regards, Alex Klotz (culturebase editorial staff)

3 6

Found error in docker-container
by Alexander Klotz July 5, 2017

July 5, 2017

Hi, one of our developers wanted to point out an error he found in mailman 3.1, docker container maxking/mailman-core-0.1 The entries in /opt/mailman/core/var/data/postfix_lmtp are not set correctly, example: /^testlist(a)mailman\.example\.com$/ lmtp:[172.19.199.2# IP Address of mailman-core container]:8024 this actually should look like this: /^testlist(a)mailman\.example\.com$/ lmtp:[172.19.199.2]:8024 Regards, Alex

1 0

REST API notes
by tlhackque＠yahoo.com June 29, 2017

June 29, 2017

As a beginner with the REST API, I found it necessary to read code and experiment to figure out how to get things done. There are a number of implementation choices that are unusual. There is some documentation in src/mailman/rest/docs. It's oriented toward Python and intermixes the mailman client & REST API, apparently trying to show equivalence. Here are some notes that may help others to avoid repeating my research. They reflect Mailman 3.1. Some reflect issues that I've opened, but I think it's worth knowing how things work today. I attempted to tie together some of pieces that are in the documentation - and note some things that aren't. I may have some things wrong, but this reflects my current understanding. (And client code.) The REST API has a hybrid interface: Requests are made with application/x-www-form-urlencoded POST, PUT, PATCH and delete http requests. Requests are also accepted as parameter strings. The responses are JSON. (This is rather surprising - one would expect JSON requests - and I hope someday they'll be accepted, as the split complicates clients. I suspect this evolved to simplify the initial Web GUI client (Postorious), but it precludes using standard JSON-in/JSON-out client libraries.) Error responses are often misidentified as content-type: application/json, but actually contain a text/plain error message. This isn't universally true; for example the 401 response actually IS JSON. A client has to guess and handle decoding exceptions. The API presents resources hierarchically, rooted at '/'. The top level resources include /users, /lists. /addresses, /domains, /system The next level is a resource id. There is a an id which is stable for the lifetime of an object, and a current name (which can be changed). For example, a list has a name like mylist(a)example.com, and a list_id of mylist.example.com. But if you change the list name, it becomes mynewname(a)example.net, while the list_id remains mylist.example.com. Lists are associated with "domains", which are the "domain part" of the list's address. That is, the part after the @. This is sometimes referred to as the "mail host", but there need not be a real host. Just something on the left side of a DNS MX record. Also, don't confuse the use of "mail host" with that of "SMTP Server", which is how Mailman sends mail. The domain is where Mailman expects to receive it. A fully qualified list name is the list name + domain - e.g. its posting address. One domain can (and usually does) support more than one list. If you delete the domain, all its lists go away too. A domain has to be created before you can create a list with an address in that domain. Resources are created with a POST to their top-level resource. To create a domain, post to /domains with mail_host => the domain, and (optionally) description => a description for the GUI. The response isn't JSON as one would expect. In fact, it's an empty application/json response with a 201 status. To create a list, one POSTs to /lists. This post takes a restricted set of parameters; in the case of a list, just its fqdn_listname, (and an optional style - which isn't well defined). The response isn't JSON as one would expect. The Location header of the response contains a URL of the new list. To configure the list, you have to follow up with a PUT or PATCH to that URL + /config This is where you can set the description, posting policy, etc. It's unrealistic to do a PUT; even if you're cloning another list, there's no programatic way to determine which attributes are writable. PATCH what you know... Members are associated with e-mail addresses - which belong to Users. You create a user by posting to /users with email => the email address, and optionally display_name => the name string. (A user can also be implicitly created by subscribing an e-mail address, but that gets confusing.) The e-mail address is the primary email address for the user. More later. Again, you get a Location header in the response, which you can use to PATCH /preferences to set delivery_status, etc. .These preferences are part of a hierarchy - many have a system default, a list default, the user default, and a subscription to that list value. You can find the User associated with a list by a GET of /addresses/address(a)example.net. This GET returns two URLs: user => the user owning this address, and self_link => the address object. Note also that there are both an email and original_email attribute. The latter preserves case. The former is used internally by Mailman as a resource key, etc. (Though exactly what happens if John(a)example.net and john(a)example.net both subscribe is unclear.) Once a list is configured, you can add members. This requires the list_id - which you don't (officially) have. So you do a GET on the list resource, to get the list_id. Then you can subscribe a member with list_id => (the list id), subscriber => email address. Optionally you can pre_verify/confirm/approve the member and/or add a display_name.. POST to /members. Again, you get a Location header back. You can't specify everything you might like. as a creation attribute. So you may have to PATCH the member to, for example, set the moderation_status. You may also need to PATCH the member /preferences if you want to set list-level delivery status, etc. Consider adding at least an owner when creating a list. One challenge is that almost everything requires multiple REST operations to set up. But REST (by definition) is stateless. So the best you can do is order operations & hope. The mailman client examples refer to transactions (e.g in users.rst, there is 'transaction.commit(); - but REST can't hold state. It does appear that the server uses DB transactions to ensure that any given REST operation is ACID, but the composite operations (e.g. create a list and set it's config) can not be Atomic. This is an architectural flaw in the API. Symbolic names (which are required) for attributes are in the src/mailman/interfaces/(class).py. What you can get/set comes from src/mailman/rest/(class).py.

3 2

Some doc updates from Fedora install experience
by tlhackque＠yahoo.com June 26, 2017

June 26, 2017

Trying to get mailman3 setup round three. Some notes from a first timer that I hope will be of use. These are in order of experience, and unfiltered. I'm a bit confused about why you have a release that pip should be able to install, but the advice I get is to pretend I'm developing from git. But off we go: Following http://docs.mailman3.org/en/latest/devsetup.html: I'm using Fedora 25. Packaged Python is 2.7.13-2, 3.6.3-6, 2-setuptools 25.1.1-1, 2-virtualenv 15.0.3-2 nodejs-less 2.7.1-1 sassc 3.4.1-1 a) fedora now uses dnf rather than yum (and has for some time). Specify dnf install rather than yum install b) sassc is packaged - just add it to the end of the dnf install string. I'm using sendmail. Directly outbound. Inbound, a custom LMTP client. It is possible to setup sendmail to use LMTP for local delivery - but if you do, it's the ONLY local delivery (or you're into some serious sendmail configuration hacking). Most installations use procmail and/or pipes. I could probably extract a pipe -> lmtp script from my project - but it's Perl, not Python. The current install process assumes a lot of Python knowledge/interaction, which is a barrier to adoption. Documentation should note that the virtualenv commands create directories of those names (I'm not a Python person, so everything is a surprise.) To save typing, I defined: alias p0='[ -n "$_OLD_VIRTUAL_PATH" ] && deactivate;cd ~mailman3' alias p2='[ -n "$_OLD_VIRTUAL_PATH" ] && deactivate;cd ~/mailman3 && source venv-2.7/bin/activate' alias p3='[ -n "$_OLD_VIRTUAL_PATH" ] && deactivate;cd ~/mailman3 && source venv-3.5/bin/activate' I suggest using mailman3 as the top level in your examples, since there's also a mailman directory in the path, and mailman is easily confused with mailman/mailman Also, if you have mailman2 - or your distro has provision for it - 'mailman' has other semantics. (Including, but not limited to things like SeLinux contexts...) I got tracebacks when I got to the "mailman info" command. After some experimentation/digging, resolved with dnf install python3-dateutil This was confusing because Python/pip seemed to think dateutil was installed - perhaps it fell back to the Python2 version? mailman info works! >> You can edit your mailman.cfg file But which one? there's one in src/mailman/config and one in var/etc/mailman.cfg. Should specify. But var looks like the one to modify, the other. The suggestion to look at the one in src for doc isn't very helpful, there are virtually no comments. So, look at the schema. To get started, I set the following: [mailman] site_owner: admin(a)example.net [devmode] enabled: yes [mta] smtp_host: smtp.example.net smtp_port: 587 #smtp_user: #smtp_pass: lmtp_host: 192.168.148.19 lmtp_port: 8024 ### Note: LMTP needs security, preferably SSL.. Thiis is probably a bunch of config items that get fed into the Python library (e.g. use ssl, cert files (current openssl includes key w/cert, but often multiple certs - rsa + ecdsa) verify client, ca bundle, ca path, client ca.) Despite the list, these are all pass-through parameters, so should not be much work. Once you have SSL, a simple shared secret (e.g. password) can be used. Or (my preference) client verification (certificate). Maybe a proxy, but who needs another process to manage? FWIW, my MTA runs on a separate VM from the MM instance, so assuming "localhost" is secure doesn't work. It also doesn't work on a multiuser machine. mailman start got some things running. Telnet & LHLO wakes up LMTP! I guess I should try to setup my first list. More as it develops.

3 6

Mailman 3 Container Images v0.1
by Abhilash Raj June 26, 2017

June 26, 2017

Hi Everyone, I have been working on containerizing Mailman 3 so that it becomes easier to test and try Mailman 3. There are two images in total: * maxking/mailman-core : This consists of Mailman Core and includes the plugin to enable the Hyperkitty Archiver. * maxking/mailman-web : This consists of a full Django installation and run the Mailman's Web UI components. It has Mailman Client, Postorius & Hyperkitty. The images are built from the Dockerfiles hosted on Github[3] in case you want to look at it. You can find most of the documentation about these images at https://asynchronous.in/docker-mailman/. The version of the internal components included in each image is available here[7]. The images are versioned and the process is documented[4], please have a look before you use them. Also, the images are signed and I encourage you to verify them before using. The process of how-to verify is also documented. Docker Compose is a tool written in Python makes is very easy to deploy connected-images and take the pain out of writing long long commands for spinning of containers. There is a sample `docker-compose.yml` file in the Github repository mentioned above which is kind-of tested to be able to spin off these images in vanilla condition (without any customization/configuration). You can report issues, comments or concerns in the Github repo[6]. [1]: https://hub.docker.com/r/maxking/mailman-core/ [2]: https://hub.docker.com/r/maxking/mailman-web/ [3]: https://github.com/maxking/docker-mailman [4]: https://asynchronous.in/docker-mailman/#release [5]: http://semver.org/ [6]: https://github.com/maxking/docker-mailman/issues [7]: https://github.com/maxking/docker-mailman/wiki -- thanks, Abhilash Raj

1 0

API Question: map list -> UI URL?
by tlhackque＠yahoo.com June 24, 2017

June 24, 2017

Using the REST API, how do I get from a list / list configuration to the URL of the management GUI? I've looked through the data returned by the API and even the SQL schemas; I don't see the path. Am I missing something, or do I need to log an issue for this? I'm not particularly interested in the subscriber pages, but it ought to be possible to get there too... Thanks.

1 0

Topics? First bug...
by tlhackque June 21, 2017

June 21, 2017

Hi, I'd like to deploy a new project on Mailman 3, which I prototyped on 2.1). Unfortunately, it's organized as one mailing list with ~ 120 topics. (The project follows another source, and it's much easier to spin up (or down) a new topic than to instantiate & manage a new list.) I see that the latest Mailman 3 release (Congrats!) doesn't support topics yet. Where is that on your todo list? First bug: Looking at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/. If I set "results per page" to a large number & switch months, results per page reverts to the default (10). It should stick with whatever I select... It also would be nice to have an account preference for this, so it doesn't have to be set on each visit.

2 2

Re: Http/Https
by Abhilash Raj June 15, 2017

June 15, 2017

Excerpts from Simon HANNA's message of June 14, 2017 1:06 pm: > You are supposed to force https in the webserver, serving postorius and hyperkitty. Especially in postorius almost all pages contain sensitive information. > > On June 14, 2017 10:05:59 PM GMT+02:00, Bill <bill3(a)uniserve.com> wrote: >>Hi folks, >> >>We're setting up Mailman 3.1 and so far installation has been good and >>we're now in the testing phase. >> >>We've run into a snag with the account signup function on Postorius. >> >>When Postorius sends an email to the user to confirm their address, it >>displays a link using the https protocol. This doesn't work. But, if we >> >>manually change the protocol to http it will work, confirm the address >>and take us back to Postorius. >> >>Is this a known bug or have we committed a configuration error? I agree to Simon's suggestion that you should use HTTPS for all communications for Postorius. However, if you really want to, it is possible to change the behavior using a configuration parameter in django-allauth which is what controls the user signup and email verification. ACCOUNT_DEFAULT_HTTP_PROTOCOL (=”http”) If you set the above to "http" in your django's settings.py, it should then generate urls with http. [1]: https://django-allauth.readthedocs.io/en/latest/configuration.html Message-ID: <draft-878tktptc9.fsf(a)gmail.com> Date: Thu, 15 Jun 2017 01:07:18 -0700 X-Notmuch-Emacs-Draft: True -- thanks, Abhilash Raj

1 0

Http/Https
by Bill June 14, 2017

June 14, 2017

Hi folks, We're setting up Mailman 3.1 and so far installation has been good and we're now in the testing phase. We've run into a snag with the account signup function on Postorius. When Postorius sends an email to the user to confirm their address, it displays a link using the https protocol. This doesn't work. But, if we manually change the protocol to http it will work, confirm the address and take us back to Postorius. Is this a known bug or have we committed a configuration error? All assistance appreciated. Bill -- Sent using Icedove on Debian GNU/Linux.

2 1

Re: "Private archives" aren't private
by Simon Liebold June 6, 2017

June 6, 2017

Am 06.06.2017 um 22:25 schrieb Abhilash Raj: > Excerpts from Simon Liebold via Mailman-users's message of June 6, > 2017 1:20 pm: >> >> AttributeError: type object 'BaseCommand' has no attribute >> 'option_list' > > It was reported recently on the bug tracker, you can track the > progress here[1]. > > > [1]: https://gitlab.com/mailman/hyperkitty/issues/135#note_31529582 Thanks Abhilash for the pointer. Simon

1 0

(Email|Thread) matching query does not exist ?
by Simon Liebold June 6, 2017

June 6, 2017

I am seeing these errors: mailman-suite_project$ python manage.py qcluster 19:27:52 [Q] INFO Q Cluster-11541 starting. 19:27:52 [Q] INFO Process-1:1 ready for work at 11546 19:27:52 [Q] INFO Process-1:2 ready for work at 11547 19:27:52 [Q] INFO Process-1 guarding cluster at 11545 19:27:52 [Q] INFO Process-1:4 pushing tasks at 11549 19:27:52 [Q] INFO Q Cluster-11541 running. 19:27:52 [Q] INFO Process-1:3 monitoring at 11548 19:27:52 [Q] INFO Process-1:1 processing [rebuild_email_cache_votes] 19:27:52 [Q] INFO Process-1:2 processing [rebuild_thread_cache_votes] 19:27:52 [Q] INFO Process-1:1 processing [rebuild_email_cache_votes] 19:27:52 [Q] ERROR Failed [rebuild_email_cache_votes] - Email matching query does not exist. 19:27:52 [Q] ERROR Failed [rebuild_email_cache_votes] - Email matching query does not exist. 19:27:52 [Q] ERROR Failed [rebuild_thread_cache_votes] - Thread matching query does not exist. Should I need to worry? I recently deleted some test emails from the archive. Don't know if this has anything to do with it. Simon

1 0

"Delete this thread" -> 'HTTP-500 -> NoneType' object has no attribute 'all'
by Simon Liebold May 30, 2017

May 30, 2017

Is deleting threads from the archive (via Hyperkitty) currently supported? I am getting the error indicated above if I click on "Delete this thread". Is there another way to delete whole threads or individual posts? Simon

3 7

Editing "automatic responses" tab i Postorius does not work
by David Krantz May 26, 2017

May 26, 2017

Hi, I am trying to change e.g. the value of "notify admin on membership changes" through postorius. This is not possible as I have no URLs for the various templates (all templates are using defaults stored on the server). Is this something that can be circumvented or fixed? I can of course change admin_notify_mchanges in the "mailman withlist" interface, but this is less than ideal. best regards // David

2 4

ANNOUNCE: Mailman 3.1.0 final!
by Barry Warsaw May 26, 2017

May 26, 2017

Hello Mailpeople! On behalf of the entire team and all our wonderful contributors, I'm happy to announce the release of GNU Mailman 3.1 final. My deep thanks go to all the Mailman project sprinters at Pycon 2017 for getting us over the line! Two years after the original release of Mailman 3.0, this version contains a huge number of improvements across the entire stack. Many bugs have been fixed and new features added in the Core, Postorius (web u/i), and HyperKitty (archiver). Upgrading from Mailman 2.1 should be better too. We are seeing more production sites adopt Mailman 3, and we've been getting great feedback as these have rolled out. Important: mailman-bundler, our previous recommended way of deploying Mailman 3, has been deprecated. Abhilash Raj is putting the finishing touches on Docker images to deploy everything, and he'll have a further announcement in a week or two. Feedback is welcome: https://github.com/maxking/docker-mailman What is GNU Mailman? GNU Mailman is free software for managing electronic mail discussion and e-newsletter lists. Mailman is integrated with the web, making it easy for users to manage their accounts and for list owners to administer their lists. Mailman supports built-in archiving, automatic bounce processing, content filtering, digest delivery, and more. Mailman 3 is released under the terms of the GNU General Public License, version 3. The best places to start for all things related to this release: http://docs.mailman3.org/ http://www.list.org/ https://gitlab.com/mailman (Note: due to timezone skew, some of the tarballs may not be available on PyPI until tomorrow.) Happy Mailman Day, -Your friendly neighborhood cabal An overview of what's new in Mailman 3.1 ======================================== Feature parity with Mailman 2.1 ------------------------------- * You should be able to do just about everything that you could do in Mailman 2.1 *except* for topics and sibling/umbrella lists. Core ---- * Added support for Python 3.5 and 3.6 * MySQL is now an officially supported database * Many improvements with importing Mailman 2.1 lists * DMARC mitigations have been added, based on, but different than the same feature in Mailman 2.1 * The REST API requires HTTP/1.1 * A new REST API version (3.1) has been added which changes how UUIDs are interpreted, fixing the problem for some JavaScript libraries * Many new REST resources and methods have been added * Individual mailing lists can augment the system's header matching rules * `mailman create` now creates missing domains by default * `mailman digests` now has `--verbose` and `--dry-run` options * `mailman shell` now supports readline history * `mailman members` can filter members based on their subscription roles * A new template system has been added for all messages originating from inside Mailman. * The Message-ID-Hash header replaces X-Message-ID-Hash * New placeholders have been added for headers and footers * Unsubscriptions can now be confirmed and/or moderated Postorius/HyperKitty -------------------- * General U/I and U/X improvements * Many more features from the Core's have been plumbed through * We've adopted Django social auth logins and dropped Persona (since it's no longer supported upstream). You can now log in via Facebook, Google, GitHub, and GitLab. Backward incompatibilities -------------------------- * Core/REST: Held message resources now have an `original_subject` key that is not RFC 2047 decoded. `subject` is now RFC 2047 decoded. * Core/REST: If you've run pre-release versions from git head, and stored welcome and goodbye templates via REST, the template key names have changed backward incompatibility.

2 1

Multiple header_checks in mailman.cfg. How?
by Simon Liebold May 20, 2017

May 20, 2017

Hello, What is the correct syntax if I wanted to perform multiple header checks? header_checks: X-Spam: (yes|maybe) header_checks: x-another-header: (some|any)thing or: header_checks: X-Spam: (yes|maybe) x-another-header: (some|any)thing or: header_checks: ['X-Spam: (yes|maybe)', 'x-another-header: (some|any)thing'] Or something completely different? I don't think it is the first two because "mailman conf -s antispam" shows only a single header_checks. But the 3rd variant doesn't work either. Simon Hello, What is the correct syntax if I wanted to perform multiple header checks? header_checks: X-Spam: (yes|maybe) header_checks: x-another-header: (some|any)thing or: header_checks: X-Spam: (yes|maybe) x-another-header: (some|any)thing or: header_checks: ['X-Spam: (yes|maybe)', 'x-another-header: (some|any)thing'] Or something completely different? I don't think it is the first two because "mailman conf -s antispam" shows only a single h= eader_checks. But the 3rd variant doesn't work either. Simon

2 1

Character set for postorius
by David Krantz May 18, 2017

May 18, 2017

Hi, I'd like to have my descriptions of maillists with the correct characters for my languages... Where is the character set for this determined? If I input e.g. 'è' (è) or 'ö' (ö) it is substituted with a '?'. Of course the html entities are not allowed either, the ampersand '&' is escaped somewhere between output and input. Cheers // David

2 1

HyperKitty needs regis, really?
by Simon Liebold May 15, 2017

May 15, 2017

Hi I am seeing a whole bunch of error messages in mailmansuite.log whenever a new message is sent to be archived: ERROR 2017-05-14 15:41:41,261 13634 django.request Internal Server Error: /hyperkitty/api/mailman/archive ... File "/opt/mailman/venv-2.7/local/lib/python2.7/site-packages/redis/connection.py", line 442, in connect raise ConnectionError(self._error_message(e)) ConnectionError: Error 111 connecting to localhost:6379. Connection refused. I didn't see this mentioned anywhere. Does HyperKitty need a running regis server to work? What am I missing? Simon

2 2

So, why are css & js files only served with "DEBUG = yes" ?
by Simon Liebold May 7, 2017

May 7, 2017

Hello List, I did see this discussed in #180 <https://gitlab.com/mailman/postorius/issues/180>, but I didn't quite understand if this is an issue or not. Why is it that I can run the development server just fine. [07/May/2017 13:23:47] "GET /static/postorius/libs/bootstrap/css/bootstrap.min.css HTTP/1.1" 304 0 [07/May/2017 13:23:47] "GET /static/postorius/css/style.css HTTP/1.1" 304 0 [07/May/2017 13:23:47] "GET /static/postorius/libs/bootstrap/js/bootstrap.min.js HTTP/1.1" 304 0 [07/May/2017 13:23:47] "GET /static/django-mailman3/js/main.js HTTP/1.1" 304 0 [07/May/2017 13:23:47] "GET /static/postorius/libs/jquery/jquery-1.11.3.min.js HTTP/1.1" 304 0 [07/May/2017 13:23:47] "GET /static/django-mailman3/css/main.css HTTP/1.1" 304 0 [07/May/2017 13:23:47] "GET /static/postorius/js/script.js HTTP/1.1" 304 0 [07/May/2017 13:23:47] "GET /static/postorius/img/mailman_logo_small_trans.png HTTP/1.1" 304 0 And as soon as I comment out # SECURITY WARNING: don't run with debug turned on in production! # DEBUG = True in mailman-suite/mailman-suite_project/settings.py and restart it 404s on me. [07/May/2017 13:41:36] "GET /static/postorius/libs/bootstrap/css/bootstrap.min.css HTTP/1.1" 404 127 [07/May/2017 13:41:36] "GET /static/django-mailman3/css/main.css HTTP/1.1" 404 109 [07/May/2017 13:41:36] "GET /static/postorius/css/style.css HTTP/1.1" 404 104 [07/May/2017 13:41:36] "GET /static/django-mailman3/js/main.js HTTP/1.1" 404 107 [07/May/2017 13:41:36] "GET /static/postorius/libs/bootstrap/js/bootstrap.min.js HTTP/1.1" 404 125 [07/May/2017 13:41:36] "GET /static/postorius/libs/jquery/jquery-1.11.3.min.js HTTP/1.1" 404 123 [07/May/2017 13:41:36] "GET /static/postorius/js/script.js HTTP/1.1" 404 103 [07/May/2017 13:41:36] "GET /static/postorius/img/mailman_logo_small_trans.png HTTP/1.1" 404 123 So the choice is insecure vs. ugly? Neither of those sounds very tempting. I guess, I am missing something, or no? Simon

3 3

reason for breaching max_message_size is "N/A"
by David Krantz May 1, 2017

May 1, 2017

Hi. Today I learned to things: The default max_message_size is 40kB. Messages larger than that are blocked (expected) with the reason "N/A" (not expected). The reason would be helpful to me as admin. Also: Is there any way to set a server default for this as it is a bit of a hassle to change it from the command line for each new list. I can of course find where in the code to change but that seems the wrong way to me. Cheers // David

2 1

Any good ideas on how to troubleshoot django allauth
by David Krantz April 27, 2017

April 27, 2017

Hi again. Allauth works for me... sometimes... For google logins it works most of the time. For facebook it almost never works. When it does not work, I get an error page with the error "An error occurred while attempting to login via your social network account." (or the equivalent in my locale). If I then reload the page, I get logged in! In some cases I get the error and the little green popup saying that I am logged in at the same time. Strange. So... If there is any documentation for how to set up or how to troubleshoot django allauth I am all ears (eyes, really). I have tested the "missing howto..." and updated version of that without enough success. Cheers // David The only thing I find is in the Apache log: (I have removed all cryptovalues and other things that should be uninteresting to others) [LOCAL_IP] - - [19/Apr/2017:00:00:39 +0000] "GET /accounts/facebook/login/?process=login&next=%2Farchives%2F HTTP/1.1" 302 706 "https://lists.example.com/accounts/login/?next=/archives/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36 Edge/15.15063" [LOCAL_IP] - - [19/Apr/2017:00:00:53 +0000] "GET /accounts/facebook/login/callback/?code=[LONG CRYPTO-LOOKING STRING] HTTP/1.1" 200 2129 "https://www.facebook.com/login/reauth.php?app_id=[MY_APP_ID_I_THINK]&signed…" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36 Edge/15.15063"

3 5

Patch/kludge suggestion and a question on adding accepted addresses
by David Krantz April 25, 2017

April 25, 2017

Hi. I found out that I had a broken email in one of my held messages queues). That gave a HTTP 500 error although that should be fixed . After some digging I found out that where the error occured. I'd suggest adding a catch for AttributeError similar to the one for KeyError in _HeldMessageBase in rest/post_moderation.py. It solved my immediate problem at least. I run the version from git with the tag 263711b3b7988c7c474e3b8952dc7e0f02f04fa2 The message causing this was probably one where I had sent a minimal email via telnet to the SMTP port and forgot the MessageID-header or something similarily silly. But it prevented me from seeing the held messages-list in postorius. I have another question: In the old mailman you could add accepted senders without adding them to the list. Is that possible in Mailman 3/Postorius? cheers. // David

3 3

502 Bad Gateway??? Trying to change stuff
by am April 23, 2017

April 23, 2017

I am trying to change my email address, but forgot password. The screen for reset gets 502 Bad Gateway ------------------------------ nginx/1.4.6 (Ubuntu) any way someone can fix this????

2 2

Remove footer link
by David Terni April 23, 2017

April 23, 2017

Hi, I need to remove footer message like "to unsubscribe etc etc" from all lists. How i can do it or edit text? Thanks alot for any suggestion. David

2 1

Fwd: Incoming command emails (i.e. listname-leave) routed to list itself
by Abhilash Raj April 22, 2017

April 22, 2017

Hi Mark, Excerpts from Mark Lindsay's message of April 20, 2017 5:37 pm: <snip> Here are some baffling lines from /var/log/exim4/mainlog from the incoming > potato-leave(a)lists.mydomain.org email: > > 2017-04-21 00:25:03 1d1MNj-0007OQ-5r DKIM: d=nervous-org.20150623. > gappssmtp.com s=20150623 c=relaxed/relaxed a=rsa-sha256 [verification > succeeded] > 2017-04-21 00:25:03 1d1MNj-0007OQ-5r <= redacted(a)nervous.org H= > mail-qk0-f170.google.com [209.85.220.170] P=esmtp S=2466 id= > CABPy5zyQtJHXtCgrN37GHCUOjuo3J=DO_j0ZD03zm8gk+4shww(a)mail.gmail.com > 2017-04-21 00:25:03 1d1MNj-0007OQ-5r => potato(a)lists.mydomain.org < > potato-leave(a)lists.mydomain.org> R=mailman3_router T=mailman3_transport > H=localhost [127.0.0.1] C="250 Ok" > 2017-04-21 00:25:03 1d1MNj-0007OQ-5r Completed > > Why does it say `potato(a)lists.mydomain.org <potato-leave(a)lists.mydomain.o > rg > >> `? >> > > I think this is actually an exim4 problem, so if the solution is to just > switch to postfix, then I will definitely do that. But I'm just asking in > case someone had a similar issue with exim4 and was able to work through > it. > > Yes, I had the exact same problem very recently and was able to fix it. The updated documentation[1] should fix your problem. The basic gist of the problem is that the exim configuration on the older documentation is missing a critical part. Exim4 by default strips off any prefixes/suffixes when delivering mail to the mailman, which causes mailman to post all the messages to mailing list instead of processing them as commands. `rcpt_include_affixes = true` Adding the above line to the transport fixes that problem. [1]: https://mailman.readthedocs.io/en/latest/src/mailman/docs/mt a.html#exim4-configuration thanks, Abhilash

3 2

Incoming command emails (i.e. listname-leave) routed to list itself
by Mark Lindsay April 21, 2017

April 21, 2017

Hi mailman-users, I'm new to Mailman 3 and Mailman in general, but I've got it up and running, and my external app is communicating quite well with the administrative REST API. Here's the only problem I haven't been able to figure out: Say I have a list called "potato." List members can post to the list by emailing potato(a)lists.mydomain.org. This works fine. However, incoming mail for command addresses (e.g. potato-leave(a)lists.mydomain.org) is routed to the list too. The command email gets sent out to all members, as if the user who wanted to unsubscribe had just written to potato(a)lists.mydomain.org. This is also the case with the potato-request(a)lists.mydomain.org address. I am using exim4 on Ubuntu. I followed the instructions here: http://mailman.readthedocs.io/en/release-3.0/src/mailman/docs/MTA.html. The only change I had to make to the exim4 config files in the readthedocs instructions was in this line: MM3_LISTCHK=MM3_HOME/lists/${local_part}@${domain} I had to change it to: MM3_LISTCHK=MM3_HOME/lists/${local_part}.${domain} That is how the subdirectories are named in my lists directory. e.g. potato.lists.mydomain.org. If I use the exact MM3_LISTCHK value from readthedocs, I get 550 Unrouteable bounces. Here are some baffling lines from /var/log/exim4/mainlog from the incoming potato-leave(a)lists.mydomain.org email: 2017-04-21 00:25:03 1d1MNj-0007OQ-5r DKIM: d=nervous-org.20150623. gappssmtp.com s=20150623 c=relaxed/relaxed a=rsa-sha256 [verification succeeded] 2017-04-21 00:25:03 1d1MNj-0007OQ-5r <= redacted(a)nervous.org H= mail-qk0-f170.google.com [209.85.220.170] P=esmtp S=2466 id= CABPy5zyQtJHXtCgrN37GHCUOjuo3J=DO_j0ZD03zm8gk+4shww(a)mail.gmail.com 2017-04-21 00:25:03 1d1MNj-0007OQ-5r => potato(a)lists.mydomain.org < potato-leave(a)lists.mydomain.org> R=mailman3_router T=mailman3_transport H=localhost [127.0.0.1] C="250 Ok" 2017-04-21 00:25:03 1d1MNj-0007OQ-5r Completed Why does it say `potato(a)lists.mydomain.org <potato-leave(a)lists.mydomain.org >`? I think this is actually an exim4 problem, so if the solution is to just switch to postfix, then I will definitely do that. But I'm just asking in case someone had a similar issue with exim4 and was able to work through it. Thanks a lot, Mark

2 1

Memory footprint
by David Krantz April 19, 2017

April 19, 2017

Hi. Now running mailman 3 I am a bit surprised that the memory footprint is so large. I count to 13 processes with each a virtual space of 160-250MB and a reserved space of about 50MB each. Not much, but quite much to run on smaller cloud instances which generally have limited memory. This is (a lot) more than the corresponding postgres installation uses, Is this normal? regards // David

6 6

Installing MM3 requires Django<1.11
by Henrik Rasmussen April 12, 2017

April 12, 2017

Two questions regarding Mailman 3 installation: 1) The Mail server setup at http://docs.mailman3.org/en/latest/devsetup.html#set-up-a-mail-server isn't described yet. Instead it refers to https://docs.djangoproject.com/en/1.10/topics/email/#topic-email-backends, but it doesn't say which file I have to change. According to https://www.webforefront.com/django/setupdjangoemail.html the file is called settings.py, but the only settings.py I can find at this stage is the /opt/mailman/postorius/example_project/settings.py file. According to http://docs.mailman3.org/en/latest/devsetup.html#set-up-and-run-postorius, "Postorius and HyperKitty both come with example_project directories with basic configuration so you can try them out. For this tutorial, however, we'll be using a project that combines both instead.". In what file should I change the mail settings then? 2) While installing Hyperkitty*) I got the error message "Django 1.11rc1 is installed but Django<1.11 is required by {'django-haystack'}". As I have slavishly followed the installation guide including http://docs.mailman3.org/en/latest/devsetup.html#set-up-django-mailman3, I wonder why a non-supported Django version was installed. *) http://docs.mailman3.org/en/latest/devsetup.html#set-up-and-run-hyperkitty Regards Henrik

2 1

Dockerizing Wordpress with Nginx and PHP-FPM on Ubuntu 16.04
by ddw David Wilson April 12, 2017

April 12, 2017

Barry et al; Does the link below provide a model for a complete flexible integrated Docker based install package for Mailman3? Any other progress that might suggest an easier road to enlightenment? Best regards. Dave Wilson https://www.howtoforge.com/tutorial/dockerizing-wordpress-with-nginx-and-ph…

2 1

Deploying mailman3 using containers
by Abhilash April 10, 2017

April 10, 2017

Hi All, I have been working for the past two weeks on trying to create a solution to easily deploy Mailman 3 in production. For those interested, you can find the instructions about how to use my work at http://asynchronous.in/docker-mailman/. I have tried to document the process as much as possible. This is still a work in progress, but I have a working deployment[1] using these containers. I try to keep the deployment updated with the github repo, but there is no automated deploy happening there so sometimes it gets out of sync. While this is aimed to finally become a production ready method to deploy mailman 3, it is still not there. All I can say at this point is that it works. I have tried my best to document everything and I keep updating the documentation whenever I feel anything needs more clarity. I would love some feedback to improve the process or documentation. You can open issues on the github repo[2]. Currently, container images are built from the master branch of the gitlab repos and are thus not branded as stable. I am waiting for 3.1 release to add a stable tag to the images. [1]: https://mail.araj.me/ [2]: https://github.com/maxking/mailman -- thanks, Abhilash Raj

1 0

Mailman 3 api php
by david.terni＠gmail.com March 27, 2017

March 27, 2017

Hi, I apologize if this is't the right place but I don't understand how connect mailman 3 with api and php/CURL. It's possibile to do it? I tried to use the same url used with mailman2 but doesn't work. Someone can help me? Thank's a lot

2 2

How to set up mailman 3
by David Krantz March 26, 2017

March 26, 2017

Hi. I have tried and failed to set up mailman 3 using the mailman_bundle. I get the mailman3 server running correctly, but the problem is the extremely sensitive web user interface... Now when I found this mail list I understand that mailman bundle is depricated and that I must restart from scratch. Is this true? This annoys me quite a lot, can someone responsible within the project please mark the deprecated package as such? Almost none of the documentation is completely correct. It is useful but very incomplete. The mailman_bundle generated configuration examples for e.g. apache simply is wrong or incomplete. That said I got it running using http only, but when I switched to HTTPS the login simply ceased working. I use password+username as the other solution is quite complicated to get running. I could of course switch to e.g. google login, but that would require at least some documentation on how to do that. So, is there any documentation on how to use mailman 3? The error I get now is "Please enter a correct username and password. Note that both fields may be case-sensitive." I know that I enter the correct password as it worked before I added HTTPS. Sorry for the rant, but I am very annoyed by this. I just need a mail list server that works and thought it would be very neat to run mailman3 after running a hoste mailman2 for many years. Best regards // David

4 5

Re: Mm3 - new adventure
by SP2L March 15, 2017

March 15, 2017

Hello Mark. On 14/03/17 18:29, Mark Sapiro wrote: > mailman-bundler is out of date and deprecated. You might find > <https://wiki.list.org/x/17891998> of interest. I appreciate prompt response, indeed. Will follow your suggestion verbatim - thank you. I read this too: http://docs.mailman3.org/en/latest/#documentation And yes, I ran: bin/mailman-post-update python manage.py migrate and some more. Best regards -- Tom - SP2L ------------------------------------ It is nice to be important. But it is more important to be nice!

2 3

Mm3 - new adventure
by SP2L March 14, 2017

March 14, 2017

Greetings. I have up&running Mailman-2.1.23 on my web site. Lately started adventurous journey with Mailman3 which is way, way different already from the beginning. Used Mailman bundler to install GNU Mailman, Postorius and HyperKitty testing instance in virtual environment, mainly relaying on belows recipe: https://gitlab.com/mailman/mailman-bundler/ Present status. Above trio and MySQLServer are "talking" to each other but because there isproper database on MySQLServer I am facing strange and unexpected issues, Hi! Executing last two commands: (venv)$ ./bin/mailman start (venv)$ ./bin/mailman-web-django-admin runserver 0.0.0.0:8000 & I see Postorius and HyperKitty up & runningbut... Belowvery condensed messages from the console: /HyperKitty/ DEBUG = False [12/Mar/2017 18:59:43] "GET /archives/ HTTP/1.1" 200 8002 WARNING Not Found: /static/hyperkitty/libs/jquery/smoothness/jquery-ui-1.10.3.custom.min.css WARNING Not Found: /static/hyperkitty/libs/jquery/smoothness/jquery-ui-1.10.3.custom.min.css WARNING Not Found: /static/hyperkitty/libs/font-awesome/css/font-awesome.min.css WARNING Not Found: /static/CACHE/css/cbbaa5c82a81.css WARNING Not Found: /static/hyperkitty/libs/font-awesome/css/font-awesome.min.css [12/Mar/2017 18:59:43] "GET /static/hyperkitty/libs/jquery/smoothness/jquery-ui-1.10.3.custom.min.css HTTP/1.1" 404 146 WARNING Not Found: /static/hyperkitty/libs/icomoon/icomoon.css WARNING Not Found: /static/CACHE/css/cbbaa5c82a81.css WARNING Not Found: /static/hyperkitty/libs/jquery/jquery-ui-1.10.3.custom.min.js WARNING Not Found: /static/CACHE/js/e6cc5c334937.js WARNING Not Found: /static/hyperkitty/libs/icomoon/icomoon.css WARNING Not Found: /static/hyperkitty/libs/jquery/jquery-ui-1.10.3.custom.min.js [12/Mar/2017 18:59:43] "GET /static/hyperkitty/libs/font-awesome/css/font-awesome.min.css HTTP/1.1" 404 134 WARNING Not Found: /static/CACHE/js/e6cc5c334937.js [12/Mar/2017 18:59:43] "GET /static/CACHE/css/cbbaa5c82a81.css HTTP/1.1" 404 107 [12/Mar/2017 18:59:43] "GET /static/hyperkitty/libs/jquery/jquery-ui-1.10.3.custom.min.js HTTP/1.1" 404 134 [12/Mar/2017 18:59:43] "GET /static/hyperkitty/libs/icomoon/icomoon.css HTTP/1.1" 404 116 [12/Mar/2017 18:59:43] "GET /static/CACHE/js/e6cc5c334937.js HTTP/1.1" 404 105 WARNING Not Found: /static/hyperkitty/img/logo.png WARNING Not Found: /static/hyperkitty/img/logo.png [12/Mar/2017 18:59:43] "GET /static/hyperkitty/img/logo.png HTTP/1.1" 404 104 WARNING Not Found: /static/hyperkitty/libs/jquery/jquery-ui-1.10.3.custom.min.js WARNING Not Found: /static/hyperkitty/libs/jquery/jquery-ui-1.10.3.custom.min.js [12/Mar/2017 18:59:43] "GET /static/hyperkitty/libs/jquery/jquery-ui-1.10.3.custom.min.js HTTP/1.1" 404 134 WARNING Not Found: /static/CACHE/js/e6cc5c334937.js WARNING Not Found: /static/CACHE/js/e6cc5c334937.js [12/Mar/2017 18:59:43] "GET /static/CACHE/js/e6cc5c334937.js HTTP/1.1" 404 105 DEBUG = True [12/Mar/2017 19:01:49] "GET /archives/ HTTP/1.1" 200 8762 [12/Mar/2017 19:01:49] "GET /static/hyperkitty/libs/bootstrap/javascripts/bootstrap.min.js HTTP/1.1" 304 0 [12/Mar/2017 19:01:49] "GET /static/hyperkitty/libs/jquery.expander.js HTTP/1.1" 304 0 [12/Mar/2017 19:01:49] "GET /static/hyperkitty/libs/d3.v2.min.js HTTP/1.1" 304 0 [12/Mar/2017 19:01:49] "GET /static/hyperkitty/libs/jquery.hotkeys.js HTTP/1.1" 304 0 [12/Mar/2017 19:01:49] "GET /static/hyperkitty/js/hyperkitty-common.js HTTP/1.1" 304 0 [12/Mar/2017 19:01:49] "GET /static/hyperkitty/js/hyperkitty-index.js HTTP/1.1" 304 0 [12/Mar/2017 19:01:49] "GET /static/hyperkitty/js/hyperkitty-overview.js HTTP/1.1" 304 0 [12/Mar/2017 19:01:49] "GET /static/hyperkitty/js/hyperkitty-thread.js HTTP/1.1" 304 0 [12/Mar/2017 19:01:49] "GET /static/hyperkitty/js/hyperkitty-userprofile.js HTTP/1.1" 304 0 [12/Mar/2017 19:01:49] "GET /static/hyperkitty/libs/icomoon/icomoon.css HTTP/1.1" 200 699 [12/Mar/2017 19:01:49] "GET /static/hyperkitty/libs/jquery/smoothness/jquery-ui-1.10.3.custom.min.css HTTP/1.1" 200 18334 [12/Mar/2017 19:01:49] "GET /static/hyperkitty/libs/jquery/jquery-ui-1.10.3.custom.min.js HTTP/1.1" 200 58173 [12/Mar/2017 19:01:49] "GET /static/CACHE/css/hyperkitty.fe05f9db56f4.css HTTP/1.1" 200 196499 [12/Mar/2017 19:01:49] "GET /static/hyperkitty/libs/font-awesome/css/font-awesome.min.css HTTP/1.1" 200 17780 [12/Mar/2017 19:01:49] "GET /static/hyperkitty/img/logo.png HTTP/1.1" 200 21168 /mailman3/ DEBUG = False Server Error (500) DEBUG = True HTTP Error 500: A server error occurred. Please contact the administrator. Exception Location: /var/lib/mailman3/mailman-bundler/eggs/mailmanclient-1.0.1-py2.7.egg/mailmanclient/_client.py in call, line 109 Then VERY, verylong list... By means of PhpMyAdmin I created manually mailman3 database and few tables (looking at 0001_initial.py) , but it is not working O.K. This handmade table is not doing it's job. How I can export skeleton of Mm3 database to MySQLServer, please? How to solve Server Error (500)? Where to look first? Best regards. -- Tom - SP2L ------------------------------------ It is nice to be important. But it is more important to be nice!

2 1

Domain in welcome message
by Jean-Luc Wasmer Feb. 20, 2017

Feb. 20, 2017

Hi, The welcome message contains the wrong URL ("example.com") for the list: Welcome to the "Test" mailing list! (...) If you ever want to unsubscribe or change your options (eg, switch to or from digest mode, change your password, etc.), visit your subscription page at: http://example.com/jean-luc.wasmer@domain.com ---------^^^^^^^^^^^ Cheers, Jean-Luc

3 3

Mailman 3 Status Update Please?
by ddw David Wilson Feb. 1, 2017

Feb. 1, 2017

Barry et al; I have been eagerly looking forward to a comprehensive install script for Mailman3 since the originally stated target date of Aug Sept and wondered if any new dates have been proposed? Furthermore, I wonder if either of the two following projects have been proposed for Google Summer of Code applications: 1) the afore mentioned comprehensive install script for Mailman3 on various targeted hardware; and/or; 2) updated for Python 3 and the latest P3 compatible Django utilities for archiving and email list collection, along with any new appropriate features? Many thanks in advance for all your efforts in this extremely worthwhile OSS project. Best regards. Dave Wilson

3 3

HTTP-500, create_http_method_map(resource, None, None) ?
by Sim Dec. 18, 2016

Dec. 18, 2016

Previously posted on mailman-users(a)python.org. But this seems to be a better place for it. ---------- Hello List, I was following the [mailman-bundler](https://gitlab.com/mailman/mailman-bundler/) installation instructions. After starting Django for the first time (before changes to the Postfix configuration and without any pre-existing lists) I received an HTTP-500 from http://127.0.0.1:8000/mailman3. Traceback (most recent call last): File "/usr/lib/python3.4/wsgiref/handlers.py", line 137, in run self.result = application(self.environ, self.start_response) File "/opt/mailman/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/database/transaction.py", line 57, in wrapper rtn = function(*args, **kws) File "/opt/mailman/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/rest/wsgiapp.py", line 65, in __call__ environ, start_response) File "/opt/mailman/mailman-bundler/venv-3.4/lib/python3.4/site-packages/falcon/api.py", line 180, in __call__ responder, params, resource = self._get_responder(req) File "/opt/mailman/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/rest/wsgiapp.py", line 135, in _get_responder method_map = create_http_method_map(resource, None, None) TypeError: create_http_method_map() takes 1 positional argument but 3 were given ERROR Internal Server Error: /mailman3/ To make it work I changed In file venv-3.4/lib/python3.4/site-packages/mailman/rest/wsgiapp.py: method_map = create_http_method_map(resource, None, None) into method_map = create_http_method_map(resource) Is this a bug or should I have created an initial list from the command line (similar to Mailman 2) before accessing this page? Simon

2 2

Mailman 3.1 beta coming soon
by Barry Warsaw Dec. 13, 2016

Dec. 13, 2016

Hello Mailman 3 users and developers! It's been a long slog but I think we are finally ready to begin the release process for Mailman 3.1. I am pretty happy about the state of the Core, and Florian is going to do some more integration testing with HyperKitty and Postorius. We still have a few issues and a merge proposal or two to address, but I am planning to spin a beta of Core this weekend to facilitate testing. Here is the Core's 3.1 milestone page: https://gitlab.com/mailman/mailman/milestones/2 If your favorite issue or merge request isn't on that list, please do get in touch. Otherwise it will be deferred to 3.2. I'm also not entirely promising I'll get to all of these; I really want to release 3.1 in 2016 so if we run out of time, it will get deferred. Here's the project-wide list of 3.1 issues: https://gitlab.com/groups/mailman/issues?scope=all&state=opened&utf8=%E2%9C… and merge requests: https://gitlab.com/groups/mailman/merge_requests?scope=all&state=opened&utf… Except that HyperKitty isn't on this list. Please do test whatever you can and let us know how it goes. Cheers, -Barry _______________________________________________ Mailman-Developers mailing list Mailman-Developers(a)python.org https://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/mark%40msapiro.n… Security Policy: http://wiki.list.org/x/QIA9

5 11

Re: [Mailman-Users] Find a smtp server to send out emails
by Mark Sapiro Dec. 8, 2016

Dec. 8, 2016

On 12/07/2016 06:56 PM, Leon wrote: > This is tricky. I have to turn on the anonymous list, but it makes > subscribers cannot directly reply to sender. Or you can install the patch at <https://gitlab.com/mailman/mailman/merge_requests/215.diff> This will enable you to set from_is_list to FromIsList.munge_from which will set the From: header to the list address without anonymizing the post. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 0

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

Mailman 3 Social Auth Configuration
by emonical＠misfitlabs.org Oct. 13, 2016

Oct. 13, 2016

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 Sept. 22, 2016

Sept. 22, 2016

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 Aug. 30, 2016

Aug. 30, 2016

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 Aug. 30, 2016

Aug. 30, 2016

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 Aug. 23, 2016

Aug. 23, 2016

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 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

[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

[Mailman-users] Initial post
by Mark Sapiro April 5, 2016

April 5, 2016

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