- Mailman-users - lists.mailman3.org

mailing list aliases
by Dmitry Makovey Jan. 20, 2018

Jan. 20, 2018

I'm running mailman 3.3.0 and seeing odd behavior for "Settings/Message Acceptance/Acceptable aliases". Two things strike me as odd: 1. whenever I change content of that field interface keeps on wrapping it in more and more square brackets: [u'[u\'[u"[u\\\'foo(a)my.com\\\']"]\']'] whereas I've started with simple foo(a)my.com. I've checked with mailmanclient library and it seems like this is happening at the core level not just an interface: ml.settings['acceptable_aliases']=['foo(a)my.com'] ml.save() print ml.settings['acceptable_aliases'] am I using it wrong or is there a bug? 2. Related to #1 - we've migrated our mailing lists from foo(a)my.com to foo(a)lists.my.com however we've preserved old addresses. But in new setup mail sent in gets stopped for moderation with: "X-Mailman-Rule-Hits: implicit-dest" . What's the best course of action here to get mailing list respond to multiple email addresses? -- Sr System and DevOps Engineer SoM IRT

3 3

why am I seeing "Access to the archiving API endpoint was forbidden"
by Dmitry Makovey Jan. 19, 2018

Jan. 19, 2018

Running docker-based MM3 I get quite a few messages in mailmanweb.log: ERROR 2018-01-19 19:09:07,467 401 hyperkitty.views.mailman Access to the archiving API endpoint was forbidden from IP 172.19.199.1, your MAILMAN_ARCHIVER_FROM setting may be misconfigured which points to the docker host making those requests. But I have no scripts/code dunning on host to do that. I've posted to this list earlier (see "mailman-web: ResponseNotReady" and "Getting connection refused on postfix trying to connect to mailman-core:lmtp") my woes with public vs private IPs in my setup and my "hack" was to set up docker-compose with explicit domainname and hostname: mailman-core: domainname: my.com hostname: mailman ... networks: mailman: aliases: - mailman.my.com where mailman.my.com is the public IP of the service. so I think I'm in the weird state where mailman-core container starts off communication on a private docker IP and finishes it off on what it thinks is public someplace... not sure where is that coming from. I ran a cross-ping for all containers to confirm they all see only private IPs and they do: core, web & nginx cross-pinging each-other and mailman.my.com all show private docker IPs so why would any packet be routed from external? can I allow more than a single IP for MAILMAN_ARCHIVER_FROM ? ITMT I've moved MAILMAN_ARCHIVER_FROM to settings_local.py and hardwired it to be 172.199.19.1 and I believe there are no errors in log files... but again - that's a lot of tiptoeing and tapdancing around the IP assignment in docker so I'm looking for input to simplify the setup. -- Sr System and DevOps Engineer SoM IRT

1 0

MM3 & postfix ... (mail loops back to myself)
by Dmitry Makovey Jan. 18, 2018

Jan. 18, 2018

Hi, I've been running Postfix+MM3 setup for a while now. However it turns out one portion of functionality has been broken all this time: member subscription via "confirmation". Quick notes on setup: I've got 2 VMs: smtp.my.com mailman.my.com I'm running mailing lists under: lists.my.com DNS for lists.my.com A: - same as mailman.my.com MX: - smtp.my.com So when somebody sends a message to foo(a)lists.my.com they receive confirmation email (which is fine and normal). That mail suggests user needs to reply to foo-confirm+randomstuff(a)lists.my.com. Whenever user does that - postfix refuses to deliver *that* mail with reason: Action: failed Status: 5.4.6 Diagnostic-Code: X-Postfix; mail for lists.my.com loops back to myself I've got transport_maps = regexp:/opt/mailman/core/var/data/postfix_lmtp local_recipient_maps = regexp:/opt/mailman/core/var/data/postfix_lmtp relay_domains = regexp:/opt/mailman/core/var/data/postfix_domains and postfix_domains contains: /^lists\.my\.com$/ lists.my.com and postfix_lmtp contains: foo(a)lists\.my\.com$/ lmtp:[mailman.my.com]:8024 ... what am I missing? -- Sr System and DevOps Engineer SoM IRT

3 2

Hyperkitty: AttributeError: 'NoneType' object has no attribute 'subject'
by Alex McLean Jan. 14, 2018

Jan. 14, 2018

I'm getting a 500 server error with some threads in hyperkitty, e.g. this one: https://we.lurk.org/hyperkitty/list/tidal@we.lurk.org/thread/3IN5NFFFPVAQSR… The following appears in the log, any pointers much appreciated! ERROR 2018-01-13 12:29:53,855 6056 django.request Internal Server Error: /hyperkitty/list/tidal(a)we.lurk.org/thread/4ECEUJRXMJ2U7EPKRMU6V6A3FVL523BC/ Traceback (most recent call last): File "/usr/local/lib/python2.7/dist-packages/django/core/handlers/exception.py", line 41, in inner response = get_response(request) File "/usr/local/lib/python2.7/dist-packages/django/core/handlers/base.py", line 249, in _legacy_get_response response = self._get_response(request) File "/usr/local/lib/python2.7/dist-packages/django/core/handlers/base.py", line 187, in _get_response response = self.process_exception_by_middleware(e, request) File "/usr/local/lib/python2.7/dist-packages/django/core/handlers/base.py", line 185, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/local/lib/python2.7/dist-packages/hyperkitty/lib/view_helpers.py", line 136, in inner return func(request, *args, **kwargs) File "/usr/local/lib/python2.7/dist-packages/hyperkitty/views/thread.py", line 193, in thread_index return render(request, "hyperkitty/thread.html", context) File "/usr/local/lib/python2.7/dist-packages/django/shortcuts.py", line 30, in render content = loader.render_to_string(template_name, context, request, using=using) File "/usr/local/lib/python2.7/dist-packages/django/template/loader.py", line 68, in render_to_string return template.render(context, request) File "/usr/local/lib/python2.7/dist-packages/django/template/backends/django.py", line 66, in render return self.template.render(context) File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 207, in render return self._render(context) File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 199, in _render return self.nodelist.render(context) File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 990, in render bit = node.render_annotated(context) File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 957, in render_annotated return self.render(context) File "/usr/local/lib/python2.7/dist-packages/django/template/loader_tags.py", line 177, in render return compiled_parent._render(context) File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 199, in _render return self.nodelist.render(context) File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 990, in render bit = node.render_annotated(context) File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 957, in render_annotated return self.render(context) File "/usr/local/lib/python2.7/dist-packages/django/template/loader_tags.py", line 72, in render result = block.nodelist.render(context) File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 990, in render bit = node.render_annotated(context) File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 957, in render_annotated return self.render(context) File "/usr/local/lib/python2.7/dist-packages/django/template/defaulttags.py", line 529, in render return self.nodelist.render(context) File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 990, in render bit = node.render_annotated(context) File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 957, in render_annotated return self.render(context) File "/usr/local/lib/python2.7/dist-packages/django/template/defaulttags.py", line 322, in render return nodelist.render(context) File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 990, in render bit = node.render_annotated(context) File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 957, in render_annotated return self.render(context) File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 1040, in render output = self.filter_expression.resolve(context) File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 708, in resolve obj = self.var.resolve(context) File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 849, in resolve value = self._resolve_lookup(context) File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 890, in _resolve_lookup current = getattr(current, bit) File "/usr/local/lib/python2.7/dist-packages/hyperkitty/models/thread.py", line 108, in subject return self.cached_values["subject"]() File "/usr/local/lib/python2.7/dist-packages/hyperkitty/models/common.py", line 61, in __call__ return self.get_or_set(*args, **kwargs) File "/usr/local/lib/python2.7/dist-packages/hyperkitty/models/common.py", line 57, in get_or_set value = self.rebuild(*args, **kwargs) File "/usr/local/lib/python2.7/dist-packages/hyperkitty/models/common.py", line 49, in rebuild value = self.get_value(*args, **kwargs) File "/usr/local/lib/python2.7/dist-packages/hyperkitty/models/thread.py", line 223, in get_value return self.instance.starting_email.subject AttributeError: 'NoneType' object has no attribute 'subject' ERROR 2018-01-13 12:29:53,855 6056 django.request Internal Server Error: /hyperkitty/list/tidal(a)we.lurk.org/thread/4ECEUJRXMJ2U7EPKRMU6V6A3FVL523BC/ Traceback (most recent call last): File "/usr/local/lib/python2.7/dist-packages/django/core/handlers/exception.py", line 41, in inner response = get_response(request) File "/usr/local/lib/python2.7/dist-packages/django/core/handlers/base.py", line 249, in _legacy_get_response response = self._get_response(request) File "/usr/local/lib/python2.7/dist-packages/django/core/handlers/base.py", line 187, in _get_response response = self.process_exception_by_middleware(e, request) File "/usr/local/lib/python2.7/dist-packages/django/core/handlers/base.py", line 185, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/local/lib/python2.7/dist-packages/hyperkitty/lib/view_helpers.py", line 136, in inner return func(request, *args, **kwargs) File "/usr/local/lib/python2.7/dist-packages/hyperkitty/views/thread.py", line 193, in thread_index return render(request, "hyperkitty/thread.html", context) File "/usr/local/lib/python2.7/dist-packages/django/shortcuts.py", line 30, in render content = loader.render_to_string(template_name, context, request, using=using) File "/usr/local/lib/python2.7/dist-packages/django/template/loader.py", line 68, in render_to_string return template.render(context, request) File "/usr/local/lib/python2.7/dist-packages/django/template/backends/django.py", line 66, in render return self.template.render(context) File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 207, in render return self._render(context) File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 199, in _render return self.nodelist.render(context) File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 990, in render bit = node.render_annotated(context) File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 957, in render_annotated return self.render(context) File "/usr/local/lib/python2.7/dist-packages/django/template/loader_tags.py", line 177, in render return compiled_parent._render(context) File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 199, in _render return self.nodelist.render(context) File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 990, in render bit = node.render_annotated(context) File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 957, in render_annotated return self.render(context) File "/usr/local/lib/python2.7/dist-packages/django/template/loader_tags.py", line 72, in render result = block.nodelist.render(context) File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 990, in render bit = node.render_annotated(context) File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 957, in render_annotated return self.render(context) File "/usr/local/lib/python2.7/dist-packages/django/template/defaulttags.py", line 529, in render return self.nodelist.render(context) File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 990, in render bit = node.render_annotated(context) File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 957, in render_annotated return self.render(context) File "/usr/local/lib/python2.7/dist-packages/django/template/defaulttags.py", line 322, in render return nodelist.render(context) File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 990, in render bit = node.render_annotated(context) File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 957, in render_annotated return self.render(context) File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 1040, in render output = self.filter_expression.resolve(context) File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 708, in resolve obj = self.var.resolve(context) File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 849, in resolve value = self._resolve_lookup(context) File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 890, in _resolve_lookup current = getattr(current, bit) File "/usr/local/lib/python2.7/dist-packages/hyperkitty/models/thread.py", line 108, in subject return self.cached_values["subject"]() File "/usr/local/lib/python2.7/dist-packages/hyperkitty/models/common.py", line 61, in __call__ return self.get_or_set(*args, **kwargs) File "/usr/local/lib/python2.7/dist-packages/hyperkitty/models/common.py", line 57, in get_or_set value = self.rebuild(*args, **kwargs) File "/usr/local/lib/python2.7/dist-packages/hyperkitty/models/common.py", line 49, in rebuild value = self.get_value(*args, **kwargs) File "/usr/local/lib/python2.7/dist-packages/hyperkitty/models/thread.py", line 223, in get_value return self.instance.starting_email.subject AttributeError: 'NoneType' object has no attribute 'subject'

2 3

Django logins for new subscribers
by Alex McLean Jan. 13, 2018

Jan. 13, 2018

Hi all, I'm moving our groups to mailman3 (http://we.lurk.org) Enjoying it so far! I've mass-subscribed people via postorius. However the subscribers don't have django (postorius/hyperkitty) logins. It seems they only exist on the mailman side, not the django side. If they go through the process of creating an account in postorius, they can configure their mailing list subscriptions, but this is a bit fiddly. Is this expected behaviour? It would be great if they could be sent a temporary link to set a password and go. Best wishes, alex

3 4

hyperkitty connection issues
by Dmitry Makovey Jan. 11, 2018

Jan. 11, 2018

I'm using docker-based deployment of mailman. things appear to be functioning for the most part, but recently I've started getting reports from users stating that mail from *some* subscribers to the list gets queued for moderation with reason "n/a". Not sure if that's related, but I've also noticed that my logs are filling up with Connection to HyperKitty failed: ("Connection broken: ConnectionResetError(104, 'Connection reset by peer')", ConnectionResetError(104, 'Connection reset by peer')) (full dump: https://gist.github.com/droopy4096/1538d34ed7b6709252e8c3e82aaca69d ) what's the best angle to troubleshoot this situation? Note: I have restarted containers within the last 24 hours and still am observing above behavior (both mail issues and connection issues in logs) -- Sr System and DevOps Engineer SoM IRT

2 1

Hyperkitty import from mailman2
by Sten Aus Jan. 3, 2018

Jan. 3, 2018

Hi I have installed mailman3 - it looks very great! Now I wanted to try import from mailman2 mbox, so i did: python2 manage.py hyperkitty_import --settings settings --ignore-mtime -v 3 --since 2010-01-01 -l test(a)list.domain.com /tmp/test.mbox It shows that it have sucessfully imported all emails and I can see them from database (sqlite3), but I cannot see them from GUI (hyperkitty). Only thing I can see is this inactive "test" list. I have tried that I create list before importing, still same result. All new emails are archiving to another lists (which are not imported, but new installations). Any help is appreciated! All the best Sten

4 8

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