Mailman 3 November 2016 - Mailman-Developers

before next release: disable backscatter in default installation
by Jo Rhett 07 Nov '22

07 Nov '22

Hi. There's a fairly simple problem here that needs to be addressed. And it's mostly a documentation/install problem. I'm hoping we can get this resolved before the next release. PROBLEM: Mailman comes out of the box ready to backscatter spam people. Yes, it's easy enough to fix. But because it comes stock this way, and is documented to install this way, most people install it to do this. Those of us who work in abuse departments are tired of hearing "well that's how Mailman works". We also object to having to teach people how to fix their mailman installations because it's not documented in the current manual. This is *exactly* like Sendmail 14 years ago. We didn't accept it then, and Sendmail fixed the problem. RESOLUTION: Mailman default installation should not backscatter in a default configuration. 1. Don't create backscatter aliases for subscribe/unsubscribe/etc by default. Nearly everyone uses web based signup. 2. Discard or hold messages from non-subscribers by default. I would think that it would be perfectly reasonable to have documentation on how to enable the 1980s-style -request / -subscribe etc aliases. However this documentation should have a note that this is against the AUP of nearly every network provider, and enabling it will likely cause them to get listed in various blacklists as a backscatter source. FYI: I know that this goes against the instincts of many old-time mailing list advocates here. But after dealing with a 10k/hour backscatter DoS my tolerance for this problem is understandably limited. Yes, it was a sweet day back in the 1980s. I was running a mailing list server and several UUCP gateways at the time, so I remember them well. But those days are past, and we need to deal with the reality of today. -- Jo Rhett Net Consonance : consonant endings by net philanthropy, open source and other randomness

21 168

Translation
by Simon Hanna 11 Jan '17

11 Jan '17

Hi, I just completed setting up the Mailman 3 projects on zanata.org They can be found here: https://translate.zanata.org/project/view/mailman https://translate.zanata.org/project/view/postorius https://translate.zanata.org/project/view/hyperkitty I'm hesitating to ask people to translate because zanata is really slow and I'm afraid of scaring people away from translating mailman in the future :D Anyhow, I'm writing to ask for your opinions. What do you think about zanata? Maybe you can try translating a couple of things and report how you feel about it. I stumbled across a few other open source solutions: https://translatewiki.net http://pootle.locamotion.org/ https://demo.weblate.org/ This mediagoblin issue discussed some alternatives when they switched away from transifex. https://issues.mediagoblin.org/ticket/913 There seems to be a pootle server run by gnu itself. https://chapters.gnu.org/pootle/ What do you think? Simon

4 9

Re: [Mailman-Developers] [django_mailman3-1.0.2] No Facebook app configured: please add a SocialApp using the Django admin
by Simon Hanna 28 Nov '16

28 Nov '16

On 28 November 2016 05:33:55 GMT+01:00, Leon <best.sum(a)gmail.com> wrote: >Hi developers. I copied production.py from ( >https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=At…), >so 'allauth.socialaccount.providers.facebook' is in INSTALLED_APPS. >Also, I >added another site and set SITE_ID = 2( >http://stackoverflow.com/questions/14019017/django-allauth-no-facebook-app-…). >However, the exception is not fixed. > > >Error log: >ImproperlyConfigured at /accounts/login/ > >No Facebook app configured: please add a SocialApp using the Django >admin > The error says it all... You need to login to the django admin and add the configuration for Facebook before you can start using it. This is needed because some auth providers require api tokens. Also are you sure you want site_id set to 2? You will have to configure a site in the admin as well. AFAIK with site_id set to 1 you get a automatically configured example.com site. -- Sent from my Android device with K-9 Mail. Please excuse my brevity.

1 0

[django_mailman3-1.0.2] No Facebook app configured: please add a SocialApp using the Django admin
by Leon 28 Nov '16

28 Nov '16

Hi developers. I copied production.py from ( https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=At…), so 'allauth.socialaccount.providers.facebook' is in INSTALLED_APPS. Also, I added another site and set SITE_ID = 2( http://stackoverflow.com/questions/14019017/django-allauth-no-facebook-app-…). However, the exception is not fixed. Error log: ImproperlyConfigured at /accounts/login/ No Facebook app configured: please add a SocialApp using the Django admin Request Method: GET Request URL: http://list.conferency.com/accounts/login/?next=/archives/ Django Version: 1.10.3 Exception Type: ImproperlyConfigured Exception Value: No Facebook app configured: please add a SocialApp using the Django admin Exception Location: /opt/mailman/venv/lib/python2.7/site-packages/django_allauth-0.29.0-py2.7.egg/allauth/socialaccount/providers/facebook/provider.py in media_js, line 131 Python Executable: /opt/mailman/venv/bin/python2 Python Version: 2.7.12 Python Path: ['/opt/mailman/mailman-bundler', '/opt/mailman/mailman-bundler/eggs/gunicorn-19.6.0-py2.7.egg', '/opt/mailman/mailman-bundler/eggs/Whoosh-2.7.4-py2.7.egg', '/opt/mailman/mailman-bundler/eggs/mock-2.0.0-py2.7.egg', '/opt/mailman/mailman-bundler/eggs/beautifulsoup4-4.5.1-py2.7.egg', '/opt/mailman/mailman-bundler/eggs/six-1.10.0-py2.7.egg', '/opt/mailman/mailman-bundler/eggs/pbr-1.10.0-py2.7.egg', '/opt/mailman/mailman-bundler/eggs/funcsigs-1.0.2-py2.7.egg', '/opt/mailman/mailman-bundler/eggs/lockfile-0.12.2-py2.7.egg', '/opt/mailman/mailman-bundler/eggs/django_extensions-1.7.5-py2.7.egg', '/opt/mailman/mailman-bundler/eggs/django_haystack-2.5.1-py2.7.egg', '/opt/mailman/mailman-bundler/eggs/enum34-1.1.6-py2.7.egg', '/opt/mailman/mailman-bundler/eggs/networkx-1.11-py2.7.egg', '/opt/mailman/mailman-bundler/eggs/python_dateutil-1.5-py2.7.egg', '/opt/mailman/mailman-bundler/eggs/django_browserid-2.0.2-py2.7.egg', '/opt/mailman/venv/lib/python2.7/site-packages/HyperKitty-1.0.4-py2.7.egg', '/opt/mailman/venv/lib/python2.7/site-packages/mailmanclient-1.0.1-py2.7.egg', '/opt/mailman/venv/lib/python2.7/site-packages/django_allauth-0.29.0-py2.7.egg', '/opt/mailman/venv/lib/python2.7/site-packages/postorius-1.0.4-py2.7.egg', '/opt/mailman/venv/lib/python2.7/site-packages/django_mailman3-1.0.2-py2.7.egg', '/opt/mailman/venv/lib/python2.7/site-packages/Django-1.10.3-py2.7.egg', '/opt/mailman/venv/lib/python2.7/site-packages', '/opt/mailman/mailman-bundler/eggs/django_compressor-2.1-py2.7.egg', '/opt/mailman/mailman-bundler/eggs/django_paintstore-0.2-py2.7.egg', '/opt/mailman/mailman-bundler/eggs/pytz-2016.7-py2.7.egg', '/opt/mailman/mailman-bundler/eggs/robot_detection-0.4-py2.7.egg', '/opt/mailman/mailman-bundler/eggs/cssmin-0.2.0-py2.7.egg', '/opt/mailman/mailman-bundler/eggs/rjsmin-1.0.12-py2.7-linux-x86_64.egg', '/opt/mailman/mailman-bundler/eggs/django_crispy_forms-1.6.1-py2.7.egg', '/opt/mailman/mailman-bundler/eggs/djangorestframework-3.5.3-py2.7.egg', '/opt/mailman/mailman-bundler/eggs/python_social_auth-0.2.21-py2.7.egg', '/opt/mailman/mailman-bundler/eggs/django_gravatar2-1.4.0-py2.7.egg', '/opt/mailman/mailman-bundler/eggs/decorator-4.0.10-py2.7.egg', '/opt/mailman/mailman-bundler/eggs/httplib2-0.9.2-py2.7.egg', '/opt/mailman/mailman-bundler/eggs/requests-2.12.1-py2.7.egg', '/opt/mailman/mailman-bundler/eggs/rcssmin-1.0.6-py2.7-linux-x86_64.egg', '/opt/mailman/mailman-bundler/eggs/django_appconf-1.0.2-py2.7.egg', '/opt/mailman/mailman-bundler/eggs/PyJWT-1.4.2-py2.7.egg', '/opt/mailman/mailman-bundler/eggs/requests_oauthlib-0.7.0-py2.7.egg', '/opt/mailman/mailman-bundler/eggs/oauthlib-2.0.1-py2.7.egg', '/opt/mailman/mailman-bundler/eggs/python_openid-2.2.5-py2.7.egg', '/opt/mailman/mailman-bundler/bin', '/opt/mailman/venv/lib/python2.7', '/opt/mailman/venv/lib/python2.7/plat-x86_64-linux-gnu', '/opt/mailman/venv/lib/python2.7/lib-tk', '/opt/mailman/venv/lib/python2.7/lib-old', '/opt/mailman/venv/lib/python2.7/lib-dynload', '/usr/lib/python2.7', '/usr/lib/python2.7/plat-x86_64-linux-gnu', '/usr/lib/python2.7/lib-tk', '/opt/mailman/venv/local/lib/python2.7/site-packages/six-1.10.0-py2.7.egg', '/opt/mailman/venv/local/lib/python2.7/site-packages/lockfile-0.12.2-py2.7.egg', '/opt/mailman/venv/local/lib/python2.7/site-packages/django_extensions-1.7.5-py2.7.egg', '/opt/mailman/venv/local/lib/python2.7/site-packages/django_haystack-2.5.1-py2.7.egg', '/opt/mailman/venv/local/lib/python2.7/site-packages/enum34-1.1.6-py2.7.egg', '/opt/mailman/venv/local/lib/python2.7/site-packages/networkx-1.11-py2.7.egg', '/opt/mailman/venv/local/lib/python2.7/site-packages/python_dateutil-1.5-py2.7.egg', '/opt/mailman/venv/local/lib/python2.7/site-packages/django_compressor-2.1-py2.7.egg', '/opt/mailman/venv/local/lib/python2.7/site-packages/django_paintstore-0.2-py2.7.egg', '/opt/mailman/venv/local/lib/python2.7/site-packages/pytz-2016.7-py2.7.egg', '/opt/mailman/venv/local/lib/python2.7/site-packages/robot_detection-0.4-py2.7.egg', '/opt/mailman/venv/local/lib/python2.7/site-packages/cssmin-0.2.0-py2.7.egg', '/opt/mailman/venv/local/lib/python2.7/site-packages/rjsmin-1.0.12-py2.7-linux-x86_64.egg', '/opt/mailman/venv/local/lib/python2.7/site-packages/djangorestframework-3.5.3-py2.7.egg', '/opt/mailman/venv/local/lib/python2.7/site-packages/django_gravatar2-1.4.0-py2.7.egg', '/opt/mailman/venv/local/lib/python2.7/site-packages/decorator-4.0.10-py2.7.egg', '/opt/mailman/venv/local/lib/python2.7/site-packages/httplib2-0.9.2-py2.7.egg', '/opt/mailman/venv/local/lib/python2.7/site-packages/rcssmin-1.0.6-py2.7-linux-x86_64.egg', '/opt/mailman/venv/local/lib/python2.7/site-packages/django_appconf-1.0.2-py2.7.egg', '/opt/mailman/venv/local/lib/python2.7/site-packages/requests-2.12.1-py2.7.egg', '/opt/mailman/venv/local/lib/python2.7/site-packages/requests_oauthlib-0.7.0-py2.7.egg', '/opt/mailman/venv/local/lib/python2.7/site-packages/python_openid-2.2.5-py2.7.egg', '/opt/mailman/venv/local/lib/python2.7/site-packages/oauthlib-2.0.1-py2.7.egg', '/opt/mailman/venv/lib/python2.7/site-packages/six-1.10.0-py2.7.egg', '/opt/mailman/venv/lib/python2.7/site-packages/lockfile-0.12.2-py2.7.egg', '/opt/mailman/venv/lib/python2.7/site-packages/django_extensions-1.7.5-py2.7.egg', '/opt/mailman/venv/lib/python2.7/site-packages/django_haystack-2.5.1-py2.7.egg', '/opt/mailman/venv/lib/python2.7/site-packages/enum34-1.1.6-py2.7.egg', '/opt/mailman/venv/lib/python2.7/site-packages/networkx-1.11-py2.7.egg', '/opt/mailman/venv/lib/python2.7/site-packages/python_dateutil-1.5-py2.7.egg', '/opt/mailman/venv/lib/python2.7/site-packages/django_compressor-2.1-py2.7.egg', '/opt/mailman/venv/lib/python2.7/site-packages/django_paintstore-0.2-py2.7.egg', '/opt/mailman/venv/lib/python2.7/site-packages/pytz-2016.7-py2.7.egg', '/opt/mailman/venv/lib/python2.7/site-packages/robot_detection-0.4-py2.7.egg', '/opt/mailman/venv/lib/python2.7/site-packages/cssmin-0.2.0-py2.7.egg', '/opt/mailman/venv/lib/python2.7/site-packages/rjsmin-1.0.12-py2.7-linux-x86_64.egg', '/opt/mailman/venv/lib/python2.7/site-packages/djangorestframework-3.5.3-py2.7.egg', '/opt/mailman/venv/lib/python2.7/site-packages/django_gravatar2-1.4.0-py2.7.egg', '/opt/mailman/venv/lib/python2.7/site-packages/decorator-4.0.10-py2.7.egg', '/opt/mailman/venv/lib/python2.7/site-packages/httplib2-0.9.2-py2.7.egg', '/opt/mailman/venv/lib/python2.7/site-packages/rcssmin-1.0.6-py2.7-linux-x86_64.egg', '/opt/mailman/venv/lib/python2.7/site-packages/django_appconf-1.0.2-py2.7.egg', '/opt/mailman/venv/lib/python2.7/site-packages/requests-2.12.1-py2.7.egg', '/opt/mailman/venv/lib/python2.7/site-packages/requests_oauthlib-0.7.0-py2.7.egg', '/opt/mailman/venv/lib/python2.7/site-packages/python_openid-2.2.5-py2.7.egg', '/opt/mailman/venv/lib/python2.7/site-packages/oauthlib-2.0.1-py2.7.egg'] Error during template rendering In template /opt/mailman/venv/lib/python2.7/site-packages/django_mailman3-1.0.2-py2.7.egg/django_mailman3/templates/account/login.html, error at line *0* No Facebook app configured: please add a SocialApp using the Django admin 1 {% extends "account/base.html" %} 2 3 {% load i18n %} 4 {% load account socialaccount %} 5 {% load bootstrap_tags %} 6 7 {% block head_title %}{% trans "Sign In" %}{% endblock %} 8 9 {% block content %} -- Best wishes, Leon

1 0

Re: [Mailman-Developers] Error occurs when subscribers send emails to list_name-leave
by Mark Sapiro 22 Nov '16

22 Nov '16

On 11/21/2016 07:23 PM, Leon wrote: > Hi developers. > > Subscribers who sent emails to list-leave@XXX got unsubscribe confirmation > email, but they are still in the member list. This is a known issue. See <https://gitlab.com/mailman/mailman/issues/294>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 0

Error occurs when subscribers send emails to list_name-leave
by Leon 22 Nov '16

22 Nov '16

Hi developers. Subscribers who sent emails to list-leave@XXX got unsubscribe confirmation email, but they are still in the member list. Error log of mailman: Nov 22 02:28:50 2016 (12315) deque: do_confirm_verify Traceback (most recent call last): File "/opt/mailman/git/mailman/src/mailman/app/workflow.py", line 69, in __next__ return step() File "/opt/mailman/git/mailman/src/mailman/app/subscriptions.py", line 402, in _step_send_confirmation raise StopIteration StopIteration Nov 22 02:30:03 2016 (12315) Uncaught runner exception: None Nov 22 02:30:03 2016 (12315) Traceback (most recent call last): File "/opt/mailman/git/mailman/src/mailman/core/runner.py", line 159, in _one_iteration self._process_one_file(msg, msgdata) File "/opt/mailman/git/mailman/src/mailman/core/runner.py", line 252, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/opt/mailman/git/mailman/src/mailman/runners/command.py", line 196, in _dispose mlist, msg, msgdata, parts, results) File "/opt/mailman/git/mailman/src/mailman/commands/eml_confirm.py", line 56, in process assert member is not None, member AssertionError: None -- Best wishes, Leon

1 0

PGP support for MM3
by Dominik 19 Nov '16

19 Nov '16

Hello everybody, I'd like to see PGP support for MM3 but I thought it might be a little to early to file an issue. My original motivation was a setup of a full encrypted mailing list. I'm well aware of the fact that it provides not the security a full end-to-end encrypted communication provides, but for some people (including me) it is an acceptable compromise. Encrypted mailing for groups of people is still a mess in 2016: * Either the group is relatively static or you never encrypt the mail for all people. * All members need to know each other. And you need the keys of all the other members. So far for the motivation. Below there are some initial thoughts: **Treat mail differently based on their signing status:** 1. Whether it has a signature or not. 2. Whether the signature is valid or not. 3. Whether the signing key matches the key of the list member. **Treat mail differently based on their encryption status** Whether it is encrypted or not. **Other opportunities** 1. A public key per list. 2. Signing of outgoing mails with that list key. 3. Encryption of outgoing mails with that list key. 4. Send a mail with the lists public key on request. Which one of these points a worth an implementation? Regards Dominik

4 3

Re: [Mailman-Developers] Docker files for mailman
by Stephen J. Turnbull 19 Nov '16

19 Nov '16

Danil Smirnov writes: > Okay I've found that image can be built if you base on Ubuntu Trusty distro > (line 6 of the Dockerfile: "FROM ubuntu:trusty") and add ruby-sass to the > set of packages to install (line 13: "apt-get install -y git python3-dev > python3-pip python-dev python-pip python-virtualenv ruby-sass"). The absence of sass is a known problem with Debian-derived systems. > I'm not sure whether I need to change it in the Wiki... Please do, but do mention that currently it seems to a problem only for the Debian family of distributions. Steve

1 0

Re: [Mailman-Developers] Docker files for mailman
by Danil Smirnov 18 Nov '16

18 Nov '16

Okay I've found that image can be built if you base on Ubuntu Trusty distro (line 6 of the Dockerfile: "FROM ubuntu:trusty") and add ruby-sass to the set of packages to install (line 13: "apt-get install -y git python3-dev python3-pip python-dev python-pip python-virtualenv ruby-sass"). I'm not sure whether I need to change it in the Wiki... On 18 November 2016 at 16:08, Danil Smirnov <danil(a)smirnov.la> wrote: > Hi Simon! > > I've just tried to build docker image from the Dockerfile mentioned on page > https://wiki.list.org/DEV/Mailman%203.0/Mailman%203.0%20Suite%20Dockerfile > > The building has stopped with the following error > > Installing mailman. >> The executable python3.4 (from --python=python3.4) does not exist >> /tmp/tmpez1ftK/run: 2: /tmp/tmpez1ftK/run: /mailman3/mailman-bundler/venv-3.4/bin/pip: >> not found >> While: >> Installing mailman. >> >> An internal error occurred due to a bug in either zc.buildout or in a >> recipe being used: >> Traceback (most recent call last): >> File "/usr/local/lib/python2.7/dist-packages/zc/buildout/buildout.py", >> line 1995, in main >> getattr(buildout, command)(args) >> File "/usr/local/lib/python2.7/dist-packages/zc/buildout/buildout.py", >> line 666, in install >> installed_files = self[part]._call(recipe.install) >> File "/usr/local/lib/python2.7/dist-packages/zc/buildout/buildout.py", >> line 1410, in _call >> return f() >> File "/mailman3/mailman-bundler/eggs/collective.recipe.cmd-0. >> 11-py2.7.egg/collective/recipe/cmd/__init__.py", line 56, in install >> self.execute() >> File "/mailman3/mailman-bundler/eggs/collective.recipe.cmd-0. >> 11-py2.7.egg/collective/recipe/cmd/__init__.py", line 69, in execute >> run_commands(cmds, self.shell) >> File "/mailman3/mailman-bundler/eggs/collective.recipe.cmd-0. >> 11-py2.7.egg/collective/recipe/cmd/__init__.py", line 39, in run_commands >> check_call('%s %s' % (shell, tmpfile), shell=True) >> File "/usr/lib/python2.7/subprocess.py", line 541, in check_call >> raise CalledProcessError(retcode, cmd) >> CalledProcessError: Command 'sh /tmp/tmpez1ftK/run' returned non-zero >> exit status 127 >> The command '/bin/sh -c buildout' returned a non-zero code: 1 >> > > Do you have any clue what happens? > > Danil > > > On 17 July 2016 at 20:06, Simon Hanna <simon.hanna(a)serve-me.info> wrote: > >> 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 >> _______________________________________________ >> 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/ma >> ilman-developers%40python.org/ >> Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/ >> danil%40smirnov.la >> >> Security Policy: http://wiki.list.org/x/QIA9 >> > >

1 0

Docker files for mailman
by Simon Hanna 18 Nov '16

18 Nov '16

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

2 1