- 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

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

Starting new thread in Postorius -> disappears
by Thor Atle Rustad Nov. 22, 2017

Nov. 22, 2017

I have had this working before, so I guess it's a simple setup error. 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. I have installed maxking's docker-mailman and copied my old setup with basic stuff like passwords and such. The only new thing is that I'm now running in userspace by putting in /etc/subuid and subguid: mailman:10000:65536 and in /etc/docker/daemon.json: { "userns-remap": "mailman" } So I get the following ownership in /opt/mailman: drwxrwsr-x 3 10100 10000 4096 nov. 21 09:00 core drwx------ 19 10070 10000 4096 nov. 21 09:27 database drwxr-sr-x 5 10100 10101 4096 nov. 21 09:24 web (I have created a user named mailman with uid 10100 so, in reality, it says "mailman" there instead of 10100 but I guess that is irrelevant here)

3 4

Mailman Core 3.1.1 and Postorius 1.1.1 released
by Abhilash Raj Nov. 19, 2017

Nov. 19, 2017

Hello Everyone, I am pleased to announce the release of Mailman Core 3.1.1 and Postorius 1.1.1. Python 2.7 is the only supported version for Postorius 1.1.1 and Python 3.5-3.6 are supported for Mailman Core 3.1.1. Both of these are bugfix releases and include some improvements. For a full list of changes, please see [1] for Core and [2] for Postorius. [1]: http://mailman.rtfd.io/en/release-3.1/src/mailman/docs/NEWS.html [2]: http://docs.mailman3.org/projects/postorius/en/latest/news.html For more information about GNU Mailman, please see our wesbite at one of the following: http://www.list.org https://www.gnu.org/software/mailman http://mailman.sourceforge.net/ https://mirror.list.org/ Documentation for Mailman 3 is available at: http://docs.mailman3.org/en/latest/ Both of these can be downloaded from PyPI. https://pypi.org/project/mailman/ https://pypi.org/project/postorius/ thanks, Abhilash Raj

1 0

Which crontab?
by Pierre Abbat Nov. 15, 2017

Nov. 15, 2017

According to http://docs.mailman3.org/en/latest/config-core.html, I have to add "@daily mailman digests --send" to the crontab. Which crontab does it go in? In the system crontab, the thing after the time is the username, and there's no user named "mailman" in /etc/passwd. Or should I put a script in / etc/cron.daily/? Pierre -- loi mintu se ckaji danlu cu jmaji

2 10

Rolling releases for Container Images and Funding Campaign for Mailman
by Abhilash Raj Nov. 14, 2017

Nov. 14, 2017

Hi Everyone, As you all know I have been working on container images for Mailman 3. We now have a new "rolling" tag for both mailman-core and mailman-web images. These images have latest source installed for every Mailman component. You can find more information about them on the website [3]. New images are available on quay.io and, moving forward, the rest of the image builds will also be moved to Quay[4][5]. These images are built using git-heads *only* if they are passing our test suite and are re-generated weekly. You should be aware that while all these components are tested with their individual test suites, their combination might sometimes not be stable. This will get you updates/bug-fixes much faster :) As most of you already know, Mailman 3 is the new and improved version with extra features, better security and much better architecture. We released Mailman Suite 3.0 in April 2015 and have come a long ways since then. Mailman Suite 3.1, release May 2016, was aimed to provide feature-parity with Mailman 2.x series and we think we _almost_ hit that goal. Apart from no monthly password reminders, Mailman 3 has a much better Administrator/User interface, REST API for scripting, a really awesome archiver, support for multiple domains, support for external plugins, support for SSO/social login and so much more! I love working on Mailman and would enjoy being able to do so full time for next 6-8 weeks. Mailman 3 is not very far from becoming the default version everyone would use, but it still needs some work to get there. I need help from you, the users of Mailman, to get us there. If you or your organization would like to move to (or, already moved to) Mailman 3, I urge you to donate[1] to us. There are options to donate using Credit Card, Paypal, Bitcoin, Wire Transfer (of any currency), Check and money order. If this campaign succeeds, here is a road map of what I intend to get done: - Move Django apps(UI/Archiver) to Python 3 (or bilingual) - Fork `mailman import` command to provide an upgrade path to Mailman 3.x from Mailman 2.x - Fix MySQL compatibility in Core - Changes in Postorius: - Add support for missing options that are already exposed in Core’s API - e.g. Support for setting templates - Find the commonly used options that are not exposed in Core, add them to Core's API and add to Postorius - Add Admin Dashboard project from GSoC 2014 (maybe?) - Add better testing of container images and provide deployment instructions for Kubernetes & Docker Swarm - Improve the container images to work with new micro-services architecture, to achieve scaling and redundancy in services. - Administrator/User documentation for Postorius & Mailman - (optional) Fork [mmcli](https://github.com/rajeevs1992/mailmancli) project from Rajeev, fix if there is anything missing and add it as an additional command line tool to work with Mailman Core. Maybe pull it under Mailman umbrella. Except for these, if there is something more important that is preventing the adoption of Mailman 3 from your end, we can discuss them. I'd like to mention that I have been working on Mailman 3 for quite some time now and I intend to implement every single item on the list. You donations would help it get done much sooner, hopefully in time for 3.2 release schedule (at PyCon US 2018). You can follow the progress of this campaign here[2]. [1]: https://my.fsf.org/civicrm/contribute/transact?reset=1&id=22 [2]: https://wiki.list.org/x/17892025 [3]: https://asynchronous.in/docker-mailman/#rolling-releases [4]: https://quay.io/repository/maxking/mailman-web [5]: https://quay.io/repository/maxking/mailman-core -- Abhilash Raj maxking(a)asynchronous.in

3 6

Django 2.0 (and newer) requires Python 3; how about archiver and list handler Django apps?
by ddw David Wilson Nov. 13, 2017

Nov. 13, 2017

Hi all; LTS Django version 1.11, the last supporting Python 2.7, was released earlier this year. I noticed that in December 2017, Django version 2.0 will be released, which apparently will require Python 3.X Taken from the Django web site, 'We recommend using the latest version of Python 3. The last version to support Python 2.7 is Django 1.11 LTS.' Given that the utilities to archive and also handle email lists are both Django applications, which apparently have *not* yet been updated to Python 3, if I understand correctly? *This leads me to wonder if this presents a problem moving forward and staying compatible with the current versions of Django (in addition to Mailman 3.0)?* Many thanks in advance for any light you can shed in this area. Best regards. Dave Wilson

2 1

Re: integrating mm3 with postfix / lmtp
by Mark Sapiro Nov. 13, 2017

Nov. 13, 2017

On 10/25/2017 05:41 PM, Fabian A. Santiago wrote: > > No to the domains part and I think virtual alias maps is needed: > > mail postfix/trivial-rewrite[19445]: warning: do not list domain xxx in BOTH virtual_mailbox_domains and relay_domains > Oct 25 20:39:19 mail postfix/trivial-rewrite[19445]: warning: do not list domain xxx in BOTH virtual_mailbox_domains and relay_domains > Oct 25 20:39:19 mail postfix/submission/smtpd[19441]: NOQUEUE: reject: RCPT from pool-108-53-239-102.nwrknj.fios.verizon.net[108.53.239.102]: 550 5.1.1 <test123@xxx>: Recipient address rejected: User unknown in virtual mailbox table; from=<fsantiago@xxx> to=<test123@xxx> proto=ESMTP helo=<[10.0.0.29]> (above slightly sanitized for return to the list) The issue here is your list domain cannot be a virtual_mailbox_domain or a virtual_alias_domain. I have the same issue on mail.python.org where we have both Mailman 2 and Mailman 3 lists @python.org. and python.org is a virtual_alias_domain. I have a group of MRs for a branch that implements "alias_domains" to deal with this. Basically it works by creating another (virtual_alias_maps) postfix_vmap mapping to map list addresses @python.org to addresses @x.python.org. Then the postfix_domains and postfix_lmtp maps have the x.python.org domain and there is a patch to mailman/runners/lmtp.py to map the x.python.org domain back to python.org. The various MRs are <https://gitlab.com/mailman/mailman/merge_requests/202> for the core, <https://gitlab.com/mailman/mailmanclient/merge_requests/18> for the REST bindings used by Postorius and <https://gitlab.com/mailman/postorius/merge_requests/186> to be able to set an alias_domain via Postorius. That's not all implemented at mail.python.org. What's there is the basic Postfix config, a bash script the generate the new mappings from the old and a simple patch to mailman/runners/lmtp.py. So, the bottom line is it can be done and it's in process, but it won't really be supported until Mailman 3.2. In the mean time, you just need to have a separate domain for your lists that isn't a virtual_*_domain. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 15

HyperKitty: discussions not updating, misreporting stats
by Cameron Smith Nov. 13, 2017

Nov. 13, 2017

These are a couple of HyperKitty issues that I have talked about in August [1]. I’ve been doing a bit more experimentation in the last few days and am reporting my findings. The two issues are: — Missing messages: HyperKitty doesn’t show all of the messages in a discussion - Misreporting of discussion statistics: HyperKitty doesn’t update the number of participants and comments in a discussion I’m using the latest Docker setup. Neither of these issues are solved by updating or rebuilding indexes: sudo docker exec mailman-web ./manage.py update_index sudo docker exec mailman-web ./manage.py rebuild_index However, if I stop and then restart the containers (sudo docker-compose down; sudo docker-compose up -d), the discussion statistics are updated and properly display the number of participants and comments in all discussions. This does not, however, solve the problem of missing messages. I have discovered two methods of displaying the missing discussion messages: add a new message to the thread in HyperKitty; I’m not convinced that this works *every* time, but it at least works *most* times run the yearly cron job; this seems to work *every* time: sudo docker exec mailman-web ./manage.py runjobs yearly [1]: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… Cameron Smith

2 1

Bounces
by David Krantz Nov. 7, 2017

Nov. 7, 2017

Hi. How do I config mailman 3.1x to send any unrecognized bounces to e.g. the list owner? Now they just end up in the bounces table but I would like to see the entire message in this case. Cheers // David

2 3

LDAP/Krb5/SAML auth for Mailman
by Dmitry Makovey Nov. 7, 2017

Nov. 7, 2017

Can anyone share some information on LDAP/Krb5 or better yet SAML auth implementation for Mailman. Is it just adding appropriate auth module to DJango project or is there more involved things? -- Sr System and DevOps Engineer SoM IRT

2 1

configuring moderators per list
by Dmitry Makovey Nov. 7, 2017

Nov. 7, 2017

We're trying to configure moderator per list and so far we were only able to add "superuser" accounts that can handle "Held messages", "Members", "Banned addresses" etc. Is there a way to create special account per-list to manage some of the aspects of particular ML without giving them all the permissions that Superuser comes along with? In MM2 there was a ML password that moderator/list admin would use to login to perform operations. Current setup allows list admins to add/delete existing lists which is not desired. -- Sr System and DevOps Engineer SoM IRT

3 3

disabling social login
by Dmitry Makovey Nov. 6, 2017

Nov. 6, 2017

Hi, I'm trying to disable social login and running into troubles stepping on it's remnants all over the place. What's the proper sequence for disabling social login in MM3 install? -- Sr System and DevOps Engineer SoM IRT

3 4

Message shows up individually but not in the thread
by Marvin Gülker Nov. 4, 2017

Nov. 4, 2017

Hi, I've just observed something weird. While some users were testing the new mailman setup, the reply did not make it into the corresponding thread, but is still associated with it. That is, the message does not show up in the thread page at[1]. However, the reply is visible if requested individually[2]. Now what's weird is that in [2] there's a link at the top that says "< thread" that takes one to [1], so there is some kind of association appearently made but only in one direction (the reverse one). mailman.log has this to say: Nov 03 17:22:31 2017 (498) ACCEPT: <1fa6f9e1-254c-e999-42d0-9a6cc263020d(a)openmailbox.org> Nov 03 17:22:32 2017 (507) 127.0.0.1 - - "GET /3.0/users/sydneyjd(a)openmailbox.org HTTP/1.1" 200 305 Nov 03 17:22:32 2017 (495) HyperKitty archived message <1fa6f9e1-254c-e999-42d0-9a6cc263020d(a)openmailbox.org> to https://lists.secretchronicles.org/hyperkitty/list/tsc-users@lists.secretch… The mailman-suite log contains: INFO 2017-11-03 17:22:32,910 14330 hyperkitty.views.mailman Archived message <1fa6f9e1-254c-e999-42d0-9a6cc263020d(a)openmailbox.org> to https://lists.secretchronicles.org/hyperkitty/list/tsc-users@lists.secretch… This looks to me like a bug. The OP of that thread sent the same message to our other mailinglist[3] (where he did not get a reply), so Mailman may has been confused by that. Marvin [1]: https://lists.secretchronicles.org/hyperkitty/list/tsc-users@lists.secretch… [2]: https://lists.secretchronicles.org/hyperkitty/list/tsc-users@lists.secretch… [3]: https://lists.secretchronicles.org/hyperkitty/list/tsc-devel@lists.secretch… -- Blog: https://www.guelkerdev.de PGP/GPG ID: F1D8799FBCC8BC4F

2 8

Hyperkitty Missing Theme/Style Sheets?
by Andrew Hodder Nov. 1, 2017

Nov. 1, 2017

I have an odd one, my Hyperkitty is functionally working fine (archived several lists without issue, can login/out), however I must have done something wrong during it's setup as it's layout is completely broken (and it keeps throwing Example.com up in the top-left corner). See attached. I'd run into a similar issue with Postorious when I first set it up, but I can't recall what fixed it. Any ideas to what needs correcting? Thanks. Sincerely, Andrew Hodder Systems Administrator Support Operations, Afilias E-mail: drew(a)afilias.info Phone: +1 416.673.4164 Fax: +1 416.646.1541

3 9

localhost[::1] said: 550 Requested action not, taken: mailbox unavailable
by Bjoern Franke Oct. 29, 2017

Oct. 29, 2017

Hi, I created & imported a bunch of 2.1 lists and for one of the lists mm3 replies mailbox unavailable to postfix. I have no clue why this happens because the other lists work. Kind regards Bjoern

2 5

No path configuration found: paths.master
by Pierre Abbat Oct. 27, 2017

Oct. 27, 2017

I installed postorius and hyperkitty with pip and ran into another problem. I ran "mailman info" and got "No path configuration found: paths.master". I have three files named mailman.cfg: /etc/mailman.cfg /usr/local/lib/python3.5/dist-packages/mailman/config/mailman.cfg /var/etc/mailman.cfg The one in /etc contains the following: [mailman] layout: master The one in /var/etc is completely commented out. If I move the one in /etc/ out of the way and run "mailman info" again, I get this: GNU Mailman 3.1.0 (Between The Wheels) Python 3.5.2 (default, Sep 14 2017, 22:51:06) [GCC 5.4.0 20160609] config file: None db url: sqlite:////etc/var/data/mailman.db devmode: DISABLED REST root url: http://localhost:8001/3.1/ REST credentials: restadmin:restpass It said "config file: /var/etc/mailman.cfg" before. What changed? Pierre -- La sal en el mar es más que en la sangre. Le sel dans la mer est plus que dans le sang.

4 6

Moderating posts via email
by Dmitry Makovey Oct. 26, 2017

Oct. 26, 2017

Hi, we are trying to figure out what is that we're doing wrong as we can't use instructions that mailman sends with information on held messages as referenced in: https://gitlab.com/mailman/mailman/blob/master/src/mailman/chains/hold.py#L… In particular - replying to the message with "Approved: listpassword" we were not able to approve any message. Since there's no place we could find in interface to change ML password I did it through the mailmanclient: ml=client.get_list('mylists(a)lists.some.com') ml.settings['moderator_password']='password123' ml.settings.save() after which we've used above password trying to approve messages following the steps outlined above. What are we doing wrong, or where to look for further information? -- Sr System and DevOps Engineer SoM IRT

4 8

scheduled tasks in docker-based deployments
by Dmitry Makovey Oct. 26, 2017

Oct. 26, 2017

I came across the section http://docs.mailman3.org/en/latest/config-web.html#scheduled-tasks-required that claims that crontab entries are *required* for normal MM3 operations, but I do not see anything like that in docker-based implementation. Should I add similar cron jobs manually to the host box? -- Sr System and DevOps Engineer SoM IRT

2 2

Setting configuration variables on all lists from command line
by Peter Mueller Oct. 26, 2017

Oct. 26, 2017

Hello, could you provide an example how I can set various configuration variables using "mailman withlist" or "mailman "shell" on _all_ lists? E.g. I want to set on all lists: m.send_welcome_message = 0 m.send_goodbye_message = 0 Thank you! P.M.

2 2

changing mail footer
by Dmitry Makovey Oct. 26, 2017

Oct. 26, 2017

Where and how can I set a footer of the message to include link to mailing list subsciptio/admin pages to simulate MM2 behavior? -- Sr System and DevOps Engineer SoM IRT

2 1

changing secrets on a prod instance
by Dmitry Makovey Oct. 26, 2017

Oct. 26, 2017

I'm trying to sort how to properly change secrets of an already running setup. In particular I want to be able to change: REST API user/password Hyperkitty API key Secret key So far, after attempting to change REST API credentials I've got my setup failing on me. Setup details: MM3 set up from maxking's docker images. -- Sr System and DevOps Engineer SoM IRT

4 4

mailman info traceback (Ubuntu Xenial)
by Pierre Abbat Oct. 26, 2017

Oct. 26, 2017

I'm trying to set up a mailing list server using Mailman. I created a server running Ubuntu Xenial and installed, then removed, the Mailman in the repo, which is 1:2.1.20-1ubuntu0.1. Then I installed pip and ran "pip3 install mailman" and "mailman info" and got an error with traceback. I then tried installing sass and Django following the instructions (I have no idea about sass and Django), then uninstalled and reinstalled Mailman, and tried "mailman info" again. Here is the result: root@lists:/# mailman info Traceback (most recent call last): File "/usr/local/bin/mailman", line 11, in <module> sys.exit(main()) File "/usr/local/lib/python3.5/dist-packages/mailman/bin/mailman.py", line 97, in main initialize(config_path) File "/usr/local/lib/python3.5/dist-packages/mailman/core/initialize.py", line 185, in initialize initialize_2(propagate_logs=propagate_logs) File "/usr/local/lib/python3.5/dist-packages/mailman/core/initialize.py", line 156, in initialize_2 config.db = getUtility(IDatabaseFactory, utility_name).create() File "/usr/local/lib/python3.5/dist-packages/mailman/database/factory.py", line 55, in create SchemaManager(database).setup_database() File "/usr/local/lib/python3.5/dist-packages/mailman/database/factory.py", line 96, in setup_database alembic.command.stamp(alembic_cfg, 'head') File "/usr/local/lib/python3.5/dist-packages/alembic/command.py", line 504, in stamp script.run_env() File "/usr/local/lib/python3.5/dist-packages/alembic/script/base.py", line 425, in run_env util.load_python_file(self.dir, 'env.py') File "/usr/local/lib/python3.5/dist-packages/alembic/util/pyfiles.py", line 81, in load_python_file module = load_module_py(module_id, path) File "/usr/local/lib/python3.5/dist-packages/alembic/util/compat.py", line 83, in load_module_py spec.loader.exec_module(module) File "<frozen importlib._bootstrap_external>", line 665, in exec_module File "<frozen importlib._bootstrap>", line 222, in _call_with_frames_removed File "/usr/local/lib/python3.5/dist-packages/mailman/database/alembic/ env.py", line 38, in <module> @public File "/usr/local/lib/python3.5/dist-packages/public/public.py", line 15, in public else sys.modules[thing.__module__].__dict__) KeyError: 'env_py' What am I doing wrong, and how do I fix it? Pierre -- .i toljundi do .ibabo mi'afra tu'a do .ibabo damba do .ibabo do jinga .icu'u la ma'atman.

2 2

how do I bulk-remove users from ML in MM3?
by Dmitry Makovey Oct. 26, 2017

Oct. 26, 2017

I just realized that "mailman members" only offers to "add members" via "-a filename" but I see no remove option. -- Sr System and DevOps Engineer SoM IRT

5 6

integrating mm3 with postfix / lmtp
by Fabian A. Santiago Oct. 25, 2017

Oct. 25, 2017

Hello, I have mm3 up and running via docker (courtesy of maxking/docker-mailman) but when i send an email to my test list, it bounces back claiming user unknown. it states: <"lmtp:[172.19.199.2]:8024"@>: unknown user: "lmtp:[172.19.199.2]:8024" looking at the email source, it seems as though the message is trying to be delivered to: Final-Recipient: rfc822; "lmtp:[172.19.199.2]:8024"@<my email server's FQDN> Original-Recipient: rfc822;test123@<my list's email domain> all of various alias transport maps are defined in postfix's main.cf. not sure where to go from here. does anyone have any clues? -- Thanks, Fabian S. OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC

2 2

mail host choices when creating a new list
by Andrew Hodder Oct. 24, 2017

Oct. 24, 2017

Hi! So, I'm trying to create a new list and pick one of the other mail domains we have configured (from the django admin panel), yet in the "Create New List" page in postorius, I see only a single option (the first domain we'd added/set as the default) in the drop-down under "Mail Host". Am I missing somewhere else I need to add alternative mail domains to? Thanks in advance! Sincerely, Andrew Hodder Systems Administrator Support Operations, Afilias E-mail: drew(a)afilias.info Phone: +1 416.673.4164 Fax: +1 416.646.1541

2 4

Mailman installation results in KeyError: 'env_py'
by Marvin Gülker Oct. 24, 2017

Oct. 24, 2017

Hi, I'm trying to install Mailman 3 on Debian 9. However, it doesn't let me do. ~~~~~~~~~~~~~ $ virtualenv -p python3 env [...] $ . ./env/bin/activate $ pip install mailman [...] Successfully installed [...]mailman-3.1.0[...] $ mailman info Traceback (most recent call last): File "/home/mailman/mailman-test/env/bin/mailman", line 11, in <module> sys.exit(main()) File "/home/mailman/mailman-test/env/lib/python3.5/site-packages/mailman/bin/mailman.py", line 97, in main initialize(config_path) File "/home/mailman/mailman-test/env/lib/python3.5/site-packages/mailman/core/initialize.py", line 185, in initialize initialize_2(propagate_logs=propagate_logs) File "/home/mailman/mailman-test/env/lib/python3.5/site-packages/mailman/core/initialize.py", line 156, in initialize_2 config.db = getUtility(IDatabaseFactory, utility_name).create() File "/home/mailman/mailman-test/env/lib/python3.5/site-packages/mailman/database/factory.py", line 55, in create SchemaManager(database).setup_database() File "/home/mailman/mailman-test/env/lib/python3.5/site-packages/mailman/database/factory.py", line 96, in setup_database alembic.command.stamp(alembic_cfg, 'head') File "/home/mailman/mailman-test/env/lib/python3.5/site-packages/alembic/command.py", line 504, in stamp script.run_env() File "/home/mailman/mailman-test/env/lib/python3.5/site-packages/alembic/script/base.py", line 425, in run_env util.load_python_file(self.dir, 'env.py') File "/home/mailman/mailman-test/env/lib/python3.5/site-packages/alembic/util/pyfiles.py", line 81, in load_python_file module = load_module_py(module_id, path) File "/home/mailman/mailman-test/env/lib/python3.5/site-packages/alembic/util/compat.py", line 83, in load_module_py spec.loader.exec_module(module) File "<frozen importlib._bootstrap_external>", line 673, in exec_module File "<frozen importlib._bootstrap>", line 222, in _call_with_frames_removed File "/home/mailman/mailman-test/env/lib/python3.5/site-packages/mailman/database/alembic/env.py", line 38, in <module> @public File "/home/mailman/mailman-test/env/lib/python3.5/site-packages/public/public.py", line 15, in public else sys.modules[thing.__module__].__dict__) KeyError: 'env_py' ~~~~~~~~~~~~~ I'm not a Python developer, I usually use Ruby for anything web-related, thus I can't make anything of this. Since the error message conveys exactly no information that I could use to find the problem and Google provides no mailman-specific information on it, I don't know what to do now. Any hint is appreciated. Python version, if of any use: $ python --version Python 3.5.3 Greetings Marvin -- Blog: https://www.guelkerdev.de PGP/GPG ID: F1D8799FBCC8BC4F

4 8

mailman-web: ResponseNotReady
by Dmitry Makovey Oct. 22, 2017

Oct. 22, 2017

We've had an odd experience with mailman3 containers: ERROR 2017-10-18 15:47:09,448 60 django.request Internal Server Error: /postorius/lists/ 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) File "/usr/local/lib/python2.7/site-packages/django/core/handlers/base.py", line 249, in _legacy_get_response response = self._get_response(request) File "/usr/local/lib/python2.7/site-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/site-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/site-packages/postorius/views/list.py", line 590, in list_index choosable_domains = _get_choosable_domains(request) File "/usr/local/lib/python2.7/site-packages/postorius/views/list.py", line 524, in _get_choosable_domains return [(d.mail_host, d.mail_host) for d in domains] File "/usr/local/lib/python2.7/site-packages/mailmanclient/_client.py", line 217, in __getattr__ return self._get(name) File "/usr/local/lib/python2.7/site-packages/mailmanclient/_client.py", line 183, in _get return self.rest_data.get(key) File "/usr/local/lib/python2.7/site-packages/mailmanclient/_client.py", line 172, in rest_data response, content = self._connection.call(self._url) File "/usr/local/lib/python2.7/site-packages/mailmanclient/_client.py", line 109, in call response, content = Http().request(url, method, data_str, headers) File "/usr/local/lib/python2.7/site-packages/httplib2/__init__.py", line 1659, in request (response, content) = self._request(conn, authority, uri, request_uri, method, body, headers, redirections, cachekey) File "/usr/local/lib/python2.7/site-packages/httplib2/__init__.py", line 1399, in _request (response, content) = self._conn_request(conn, request_uri, method, body, headers) File "/usr/local/lib/python2.7/site-packages/httplib2/__init__.py", line 1355, in _conn_request response = conn.getresponse() File "/usr/local/lib/python2.7/httplib.py", line 1108, in getresponse raise ResponseNotReady() ResponseNotReady It seems like mailman-core is still operating properly, but for some reason mailman-web is not. Can I reset mailman-web somehow to re-initiate? -- Sr System and DevOps Engineer SoM IRT

4 9

Removing the footer from mails
by Peter Mueller Oct. 21, 2017

Oct. 21, 2017

Hi, mailman2 had the configuration variable "msg_footer" to edit/remove the footer. How can I get rid of the footer in mailman3? Example: "_______________________________________________ Example mailing list -- mailinglist(a)example.com To unsubscribe send an email to mailinglist(a)example.com" Thank you! P.M.

2 1

Moving/cloning mailman3
by Dmitry Makovey Oct. 18, 2017

Oct. 18, 2017

Hi, I am drawing a blank looking for documentation for mailman3 migrations. How can one dump existing settings for mailman and import it into another instance? -- Sr System and DevOps Engineer SoM IRT

3 5

Mails from Django are not sent
by Bjoern Franke Oct. 17, 2017

Oct. 17, 2017

Hi, I'm using the "mailman-suite" setup for Postorious and Hyperkitty. I've set EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' EMAIL_HOST = 'localhost' in settings.py, but no mails are sent. Files with the e-mails are in the emails folder, but nothing happens, also no errors regarding emails are logged. Postfix as MTA can be connected via localhost:25 and e.g. mailman-core can use it fine. What can I do for further debugging? Kind regards Bjoern Franke

3 3

Installing mailman using pip
by Loring Oct. 16, 2017

Oct. 16, 2017

I have install mailman-core using pip when I call up "mailman info" I get the following error can anyone point me to what is wrong. Traceback (most recent call last): File "/usr/local/bin/mailman", line 11, in <module> sys.exit(main()) File "/usr/local/lib/python3.5/dist-packages/mailman/bin/mailman.py", line 97, in main initialize(config_path) File "/usr/local/lib/python3.5/dist-packages/mailman/core/initialize.py", line 185, in initialize initialize_2(propagate_logs=propagate_logs) File "/usr/local/lib/python3.5/dist-packages/mailman/core/initialize.py", line 156, in initialize_2 config.db = getUtility(IDatabaseFactory, utility_name).create() File "/usr/local/lib/python3.5/dist-packages/mailman/database/factory.py", line 55, in create SchemaManager(database).setup_database() File "/usr/local/lib/python3.5/dist-packages/mailman/database/factory.py", line 96, in setup_database alembic.command.stamp(alembic_cfg, 'head') File "/usr/local/lib/python3.5/dist-packages/alembic/command.py", line 504, in stamp script.run_env() File "/usr/local/lib/python3.5/dist-packages/alembic/script/base.py", line 425, in run_env util.load_python_file(self.dir, 'env.py') File "/usr/local/lib/python3.5/dist-packages/alembic/util/pyfiles.py", line 81, in load_python_file module = load_module_py(module_id, path) File "/usr/local/lib/python3.5/dist-packages/alembic/util/compat.py", line 83, in load_module_py spec.loader.exec_module(module) File "<frozen importlib._bootstrap_external>", line 665, in exec_module File "<frozen importlib._bootstrap>", line 222, in _call_with_frames_removed File "/usr/local/lib/python3.5/dist-packages/mailman/database/alembic/env.py", line 38, in <module> @public File "/usr/local/lib/python3.5/dist-packages/public/public.py", line 15, in public else sys.modules[thing.__module__].__dict__) KeyError: 'env_py' -- Richmond Loring rloring(a)bnl.gov Advanced Systems Engineer

2 1

Disabling max_message_size and send_welcome/goodbye_msg globally or by API
by Peter Mueller Oct. 11, 2017

Oct. 11, 2017

Hello, is it possible to turn off max_message_size and send_welcome_msg / send_goodbye_msg globally? If there are no global options, how can I turn off these feature using the REST API? In python you can do it with >>> mlist.max_message_size = 0. If I send a PATCH request to lists/some@list/config with body max_message_size=0, I get "Unknown attribute". Same for send_welcome_msg and send_goodbye_msg. Thank you! P.M.

2 1

The message is larger than the 40 KB maximum size
by Simon Oct. 8, 2017

Oct. 8, 2017

Hello, I understand I cannot increase the message size limit in Postorius (yet). But is there another way to adjust it? Simon

2 2

Re: Mailman core: basic internationalization howto?
by David Krantz Oct. 6, 2017

Oct. 6, 2017

Hi. This is far short of a howto: I have done something similar for one of my lists, although for Swedish. I just added custom templates for all things necessary and set the default language for the list to "sv" for Swedish. It worked without setting the language on the list but then any non-ASCII characters in the template caused mailman to crash and lose the mail without any warning if you send a HTML-formatted message. But it works just fine for pure text messages, I guess as the character set in my test mail was something compatible. I think I filed an error for this. The language for the list can be set via the "mailman withlist" command (or in the database directly, but I have not tried that). I run a relatively new version of mailman, after 3.1. Without Hyperkitty. // David On Wed, Oct 4, 2017 at 10:55 AM, Thor Atle Rustad <thor.rustad(a)gmail.com> wrote: > I would like to use Norwegian in the welcome/subscribe/unsubscribe/confirm > etc messages from mailman3. For my current project I want all future > mailing lists to have Norwegian as default. I find some sporadic info on > the subject, but it's fair to say that I would like some simple > instructions (e.g. what to copy from where to where, and which configs to > change). > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

5 5