- Mailman-users - lists.mailman3.org

Postorius 1.1.2 security release
by Abhilash Raj Dec. 29, 2017

Dec. 29, 2017

Hi Everyone, I am pleased to announce that Postorius 1.1.2 is released and is up on PyPI[1]. This release fixes a security bug that sets the password of a user in Core to their display name. It is recommended that you upgrade to this version. Postorius (Django) and Mailman Core both have different notion of "user" and "password". When a user account in created in Postorius, it creates a user in Core using the REST API. This bug, causes the password of user created in Core to be set to their display name instead. However, as of now, there are no use cases of the user password in Core and it is present only for historical reasons. So, while this bug is a serious one, it wouldn't result in any real-world exploit. Along with the bug-fix, this release includes a new command that resets *all* user passwords in Core to a random value. Again, there are no use cases of these passwords so resetting *all* of them isn't going to cause any inconvenience to users. This command should be run after the upgrade: $ cd mailman-suite/mailman-suite_project/ $ python manage.py reset_passwords Python 2.7 is the only supported Python version for this release. All versions of Django <=1.11 is supported. For more information about GNU Mailman and Postorius, please see our website: http://list.org The source code is available on Gitlab: https://gitlab.com/mailman/ [1]: https://pypi.org/project/postorius -- thanks, Abhilash Raj

3 4

Schedule for a resolution of #406, #410 and #437
by Henrik Rasmussen Dec. 15, 2017

Dec. 15, 2017

I was wondering when #406<https://gitlab.com/mailman/mailman/issues/406>, #410<https://gitlab.com/mailman/mailman/issues/410> and #437<https://gitlab.com/mailman/mailman/issues/437> could be fixed. It seems that it would not be far, as !322<https://gitlab.com/mailman/mailman/merge_requests/322> is ready to be merged. On another note, why doesn't mailman3.org seem to be affected by these problems, with so many members wide spread across the world, when I have at least three lists with only 1794, 646 and 317 members affected by it. -- Henrik Rasmussen <her(a)adm.ku.dk<mailto:her@adm.ku.dk>> University of Copenhagen, Danmark

3 3

help for new installation.
by claudio.jofre＠yandex.com Dec. 12, 2017

Dec. 12, 2017

Hello everyone. A few days ago, I am trying to install and configure mailman 3, in a Centos7. and the truth has not been achieved. I am already a little desperate. I'll tell you First I install the hyperkitty-el.repo repository and install mailman 3, hyperkitty and postorius. Initially when reviewing and making some minor modifications to the mailman configuration file, the service apparently rises without major problems. The problem occurs when I try to configure the web interfaces. Initially the apache server did not start, with a series of errors. Following the instructions of the document published here: http://www.admin-magazine.com/Archive/2015/29/Mailman-3.0-a-long-time-comin… I managed to eliminate the initial errors, which prevented to raise the Apache server. However, when trying to access the web pages, in the case of hyperkitty, I get an error 500 with an "internal server error". In the case of postorius, I get an error 403 forbidden. In the mail, I receive a log, with the following content: Traceback (most recent call last): File "/ usr / bin / django-admin", line 5, in <module> management.execute_from_command_line () File "/usr/lib/python2.7/site-packages/django/core/management/__init__.py", line 354, in execute_from_command_line utility.execute () File "/usr/lib/python2.7/site-packages/django/core/management/__init__.py", line 303, in execute settings.INSTALLED_APPS File "/usr/lib/python2.7/site-packages/django/conf/__init__.py", line 48, in __getattr__ self._setup (name) File "/usr/lib/python2.7/site-packages/django/conf/__init__.py", line 44, in _setup self._wrapped = Settings (settings_module) File "/usr/lib/python2.7/site-packages/django/conf/__init__.py", line 92, in __init__ mod = importlib.import_module (self.SETTINGS_MODULE) File "/usr/lib64/python2.7/importlib/__init__.py", line 37, in import_module __import __ (name) ImportError: No module named settings In the Apache logs, it also shows the following: [Mon Dec 11 21: 48: 41.875069 2017] [authz_core: error] [pid 15333] [client my-client-ip: 33584] AH01630: client denied by server configuration: / etc / postorius / sites / default / srv when I execute the command: django-admin check throws me the following: django.core.exceptions.ImproperlyConfigured: Requested setting DATABASES, but settings are not configured. You must either define the environment variable DJANGO_SETTINGS_MODULE or call settings.configure() before accessing settings. checking the ports, I can see that python has open ports 8000 in 127.0.0.1, and 8001 in external ip, for more than I have looked for information, documentation, etc, about the procedure of the installation. all the documentation I found, part of the premise of an installation, clean from git, by pip, but none from the yum and rpm. So it is difficult for me to determine what to apply, and what not. apparently no one has installed, or has had problems in the installation from repositories, or I am omitting some step (most likely) that I could not determine. the bad thing, is that in postfix, I have everything configured, with digital signatures, so I would not like to lose all that work, as to start with an installation from 0. If you can help me, it would be very helpful. since I made the request of help in another list, of dev, to which it is supposed that the consultations should be made, according to the historical mails, but I never received answer. Of course, thank you very much for any help and guidance they can give me.

3 7

Re: Starting new thread in Postorius -> disappears
by Cameron Smith Dec. 12, 2017

Dec. 12, 2017

I would suggest that there is something very broken here: there seems to be a problem with communication between the email system (mailman core…?) and HyperKitty. On November 21, I sent the message below, as a part of this very thread, to Thor and cc’d the mailman 3 list. But the message never showed up in HyperKitty [1]. I don’t know if other list members received it in their email inboxes or not. Thor obviously received the message (it was addressed to him directly), because he referenced it in a message that is in the archives [1]. However, I never received an email copy of his message from the list. So, what’s going on? What baffles me is that more people are not complaining about this. Is it just that no one has noticed? Or is it some subtle misconfiguration in my system? And in Thor’s apparently. And maybe in the lists.mailman3.org system as well. [1] https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > On 2017.11.21, at 06:31 , Cameron Smith <ccsmith(a)mail2.cetsi.com> wrote: > > Thor, > > I, too, have been struggling with messages not showing up [1], although the conditions are somewhat different. > > What I have found works to make all of the messages appear is the following, which you might try: > > sudo docker-compose exec mailman-web ./manage.py runjobs yearly > > > [1] https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > > > >> On 2017.11.21, at 04:41 , Thor Atle Rustad <thor.rustad(a)gmail.com> wrote: >> >>> >>> >>>> When I send a message from the Postorius interface, it is neither sent >>> out >>>> or stored. I briefly see this message: "Your reply has been sent and is >>>> being processed.", and then nothing happens. Cameron Smith Nanaimo, BC tel:1.604.803.0051

2 2

Postorius: Dropdown menus problem
by Thor Atle Rustad Dec. 5, 2017

Dec. 5, 2017

In my latest iteration I installed Maxking docker-mailman by downloading the files (git clone https://github.com/maxking/docker-mailman.git) and building the images myself by modifying docker-compose.yaml like this: services: mailman-core: container_name: mailman-core build: context: ./core dockerfile: Dockerfile-alternate Same thing goes for mailman-web. Only modification was changing the uid/gid in the images to make it equal to the local user on the host. Now a few things are not working. In Postorius <server>/postorius/lists/<listname>) there is a menu row (Subscription requests|Held messages|Members|Settings|Mass operations|Banned addresses etc). The two items Members and Mass operations should normally show a drop-down menu when clicked, but here nothing happens. Same thing for the Admin menu (can't access Logout, amongst other things). In Hyperkitty, messages are not loaded properly. In various places on the page I see spinning discs indicating something is loading, but nothing happens. Any ideas? Thor

2 2

Setting up Admin Account
by Pierre Abbat Dec. 1, 2017

Dec. 1, 2017

So I installed a crontab for list and read about configuring the DB (I think I'll use SQLite). I got to http://docs.mailman3.org/en/latest/config-web.html . Because of the dollar sign, I assume that the commands are to be run as list. Here's what I did: root@lists:~# ls root@lists:~# sudo list sudo: list: command not found root@lists:~# su list This account is currently not available. root@lists:~# ls /var/list ls: cannot access '/var/list': No such file or directory root@lists:~# locate mailman-suite_project root@lists:~# mkdir /var/list root@lists:~# chown list.list /var/list root@lists:~# su list This account is currently not available. root@lists:~# man su root@lists:~# su -s /bin/bash list list@lists:/root$ cd list@lists:~$ cd mailman-suite_project bash: cd: mailman-suite_project: No such file or directory list@lists:~$ mkdir mailman-suite_project list@lists:~$ cd mailman-suite_project list@lists:~/mailman-suite_project$ python manage.py createsuperuser python: can't open file 'manage.py': [Errno 2] No such file or directory list@lists:~/mailman-suite_project$ locate manage.py /usr/lib/python2.7/dist-packages/django/conf/project_template/manage.py /usr/lib/python2.7/dist-packages/django/conf/project_template/manage.pyc /usr/local/lib/python2.7/dist-packages/example_project/manage.py /usr/local/lib/python2.7/dist-packages/example_project/manage.pyc /usr/local/lib/python3.5/dist-packages/falcon/bench/dj/manage.py Which manage.py should I use? Pierre -- Lanthanidia deliciosa: What the kiwifruit would be if it weren't so radioactive.

4 4

Where are the subject templates hidden?
by Thor Atle Rustad Nov. 29, 2017

Nov. 29, 2017

Using Docker. Suppose I've overcome https://gitlab.com/mailman/mailman/issues/359 and I can make Mailman use the templates/site/no directory for my customized templates. Yes, it seems to be working, no hickups when national characters are used in the templates. but... the welcome message still says "Welcome to the "listname" mailing list" in English. Is it possible to change that?

3 3

LMTP not listening
by Bartosz Sawicki Nov. 25, 2017

Nov. 25, 2017

Hi everyone :), This is my first post in this group, so let me thank all of the developers for incredible work with Mailman3. Special congratulations goes to new project leader, Abhilash :) I've been using Mailman2 from over 15 years, and recently decided that it is time to upgrade. For several days I'm playing with all of the components of the system. Currently everything looks to be working nicely :) Mailman-core, Mailman-suite (Postorius, Hyperkitty) installed directly, not using docker containers. The last step was integration with MTA. I've configured Postfix and Mailman-core according to: https://mailman.readthedocs.io/en/latest/src/mailman/docs/mta.html#mailman-… But messages send to the list address are not delivered to the list :( I've started to investigate whats happening and realize that Postfix can not connect to mailman using LMTP. It seems that mailman is not listening on port 8024. Nov 24 13:12:31 lists postfix/lmtp[2737]: connect to 127.0.0.1[127.0.0.1]:8024: Connection refused I've checked log files, but haven't realize anything unusual . Any ideas where I could try to find cause of the problem ? My mailman.cfg file MTA section: [mta] incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: localhost lmtp_port: 8024 smtp_host: localhost smtp_port: 25 regrds.

3 2

Understanding solved issues in Running releases of Docker-mailman
by Henrik Rasmussen Nov. 24, 2017

Nov. 24, 2017

Newbie-question: This is more or less a GitHub / GitLab question, but specific to Mailman. Now using Running releases<https://github.com/maxking/docker-mailman/blob/master/README.md#rolling-rel…> of Docker-mailman (and in general using Docker-mailman), I am wondering, how I can tell which issues having been solved in each release? My goal is to understand when issues like (currently, but not limited to) Mailman-core issues #256<https://gitlab.com/mailman/mailman/issues/256>, #322<https://gitlab.com/mailman/mailman/issues/322>, #359<https://gitlab.com/mailman/mailman/issues/359> (all which states Closed in the Mailman-core Issue log) and Mailman-core issues #406<https://gitlab.com/mailman/mailman/issues/406>, #410<https://gitlab.com/mailman/mailman/issues/410> and MR !322<https://gitlab.com/mailman/mailman/merge_requests/322> (which all states Open) have been solved and included in the Docker-mailman latest running release and normal release. I pulled the latest Running release<https://github.com/maxking/docker-mailman/blob/master/README.md#rolling-rel…> today, but as I have never been able to recreate the problems (above stated issues) my users experienced on several lists, I would like to make sure they have been solved, before I make a new attempt migrate my Mailman 2 lists to Mailman 3. -- Henrik Rasmussen <her(a)adm.ku.dk<mailto:her@adm.ku.dk>> University of Copenhagen, Danmark

2 1

Time Stand Still
by Barry Warsaw Nov. 23, 2017

Nov. 23, 2017

Somewhen in the dark recesses of intarweb history, I found myself as the project leader for both Jython (née JPython) and GNU Mailman. I'd been involved with Jython since it was invented by Jim Hugunin around the time he came to work with us at Pythonlabs. I'd been contributing to Mailman since we inherited John Viega's Python-based Dave Matthews Band list server, and put it to use replacing python.org's Majordomo installation. I'd enjoyed both projects, but knew I could not lead both, so I had to make a choice. I chose to turn over Jython to a team that's done a much better job over the years than I ever could have. Something about email, and especially the communication and collaboration patterns that it facilitates, really fascinated me. I know, I know, but we all have our lapses of sanity. Mine has lasted almost 20 years, a bit more than "momentary" perhaps. I've rarely gotten paid to work on Mailman, but it did provide me some great opportunities. Most notably it led to my 10 year stint at Canonical. I was originally hired on there to integrate mailing lists with Launchpad, and Mailman was the obvious choice. I learned a ton doing that project, and working within the constraints of integrating the two Python-based systems, especially since Launchpad was originally not free software and Mailman was GPL'd. Later, the Zope-based Launchpad source code was released under the AGPL, making much of the monkeypatching unnecessary, but by then the system was solid and reliable, and you don't fix what's not broken. Except, I guess I did. I took a lot of the lessons from that work, along with a good hard look at all the problems with Mailman 2, and began to break another cardinal rule of software development: second system syndrome. The result is Mailman 3. It took forever, and we're still not at complete feature parity with Mailman 2, but at least it's Real Enough to be used at many Real Sites, including python.org and lists.fedoraprojects.org. It would be ridiculous for me to take significant credit for this. I have to acknowledge the amazing user community -- you! -- for all the support, patches, suggestions, feedback, patience, criticism, donations, and contributions that you've given to the project, and to me personally over the years. And my deepest gratitude goes to all the core developers that have stayed or come and gone, but most especially the current Cabal: Abhilash Raj, Aurelien Bompard, Florian Fuchs, Mark Sapiro, Stephen J. Turnbull, Terri Oda. You should know that each and every one of them is truly awesome, both in what they contribute technically, and in their amazing friendships. Mailman is infinitely better because of their involvement, and I've loved spending time with them over the years at the Pycon sprints, making releases and sharing teas and meals. My blog is called We Fear Change, and that's humorously taken from a 90's bit in Mike Myer's excellent Wayne's World movie (a phrase actually uttered by the brilliant Dana Carvey as Garth). The irony of course is that while we all may fear change, it's the one constant thing we can count on. And in fact, we *require* change to thrive, because if you aren't changing, you aren't alive. Time, and being engaged with life's vagaries, means there's no alternative to change; it must be embraced. And so, with a vague reference to the many (good!) changes in my personal and professional life, I'm announcing that I'm stepping down from the project leadership role of GNU Mailman, effective... nowish! And it's with unanimous agreement among the GNU Mailman Steering Committee (a.k.a. the Mailman Cabal), that we are announcing Abhilash Raj as the new project leader. If you don't recognize Abhilash's name, you probably aren't paying attention, at least to Mailman 3. Abhilash came to us in 2013 as a Google Summer of Code student, and he's become one of the project's most valuable contributors. His list of accomplishments is long, and it includes everything from redesigning the website, to integrating CI with our GitLab build system, porting our code to the SQLAlchemy ORM, adding MySQL support, revving up adoption through his Docker images, along with his great coding work on Core, Postorius, HyperKitty, and mailmanclient. This transition is good for the project too. Email, its defining protocols and standards, and its role in our daily lives, has changed profoundly since the early days of Mailman. A fresh perspective and enthusiasm will help keep Mailman relevant to the changing ways we -- especially the FLOSS and tech communities -- communicate. Please join me in supporting Abhilash in every way possible as he takes over in this new role as project leader. I'll be here when and if needed, even as I create space in my "spare" time for... Something Else. I look forward to the vision that Abhilash will bring to the project, and I know that he will do a great job. To me, Mailman has always been about collaboration, and the best way for it to succeed is for you to continue to contribute your insights, experiences, opinions, and skills with positive intention. -Barry https://www.wefearchange.org/

2 1