- Mailman-users - lists.mailman3.org

Just starting with mailman3
by Loring 01 Feb '18

01 Feb '18

I am just starting with mailman 3 where can I find good documentation on getting started? -- Richmond Loring rloring(a)bnl.gov Advanced Systems Engineer

2 1

confirm-email: error NoReverseMatc
by Peter Münster 31 Jan '18

31 Jan '18

Hi, When confirming the email address after sign-up, I get this error: --8<---------------cut here---------------start------------->8--- ERROR 2018-01-31 09:31:57,143 28537 django.request Internal Server Error: /accounts/confirm-email/Ng:1egno5:_T5eipR8TTan-zWjLK8EhYuetjQ/ Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/django/core/handlers/base.py", line 132, in get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python2.7/site-packages/django/views/generic/base.py", line 71, in view return self.dispatch(request, *args, **kwargs) File "/usr/lib/python2.7/site-packages/django/views/generic/base.py", line 89, in dispatch return handler(request, *args, **kwargs) File "/usr/lib/python2.7/site-packages/django_allauth-0.34.0-py2.7.egg/allauth/account/views.py", line 283, in post resp = self.login_on_confirm(confirmation) File "/usr/lib/python2.7/site-packages/django_allauth-0.34.0-py2.7.egg/allauth/account/views.py", line 332, in login_on_confirm redirect_url=self.get_redirect_url) File "/usr/lib/python2.7/site-packages/django_allauth-0.34.0-py2.7.egg/allauth/account/utils.py", line 157, in perform_login get_login_redirect_url(request, redirect_url)) File "/usr/lib/python2.7/site-packages/django_allauth-0.34.0-py2.7.egg/allauth/account/utils.py", line 50, in get_login_redirect_url url = url() File "/usr/lib/python2.7/site-packages/django_allauth-0.34.0-py2.7.egg/allauth/account/views.py", line 362, in get_redirect_url self.request) File "/usr/lib/python2.7/site-packages/django_allauth-0.34.0-py2.7.egg/allauth/account/adapter.py", line 176, in get_email_confirmation_redirect_url return self.get_login_redirect_url(request) File "/usr/lib/python2.7/site-packages/django_allauth-0.34.0-py2.7.egg/allauth/account/adapter.py", line 156, in get_login_redirect_url return resolve_url(url) File "/usr/lib/python2.7/site-packages/django/shortcuts.py", line 205, in resolve_url return urlresolvers.reverse(to, args=args, kwargs=kwargs) File "/usr/lib/python2.7/site-packages/django/core/urlresolvers.py", line 579, in reverse return force_text(iri_to_uri(resolver._reverse_with_prefix(view, prefix, *args, **kwargs))) File "/usr/lib/python2.7/site-packages/django/core/urlresolvers.py", line 496, in _reverse_with_prefix (lookup_view_s, args, kwargs, len(patterns), patterns)) NoReverseMatch: Reverse for '' with arguments '()' and keyword arguments '{}' not found. 0 pattern(s) tried: [] ERROR 2018-01-31 09:31:57,143 28537 django.request Internal Server Error: /accounts/confirm-email/Ng:1egno5:_T5eipR8TTan-zWjLK8EhYuetjQ/ Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/django/core/handlers/base.py", line 132, in get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python2.7/site-packages/django/views/generic/base.py", line 71, in view return self.dispatch(request, *args, **kwargs) File "/usr/lib/python2.7/site-packages/django/views/generic/base.py", line 89, in dispatch return handler(request, *args, **kwargs) File "/usr/lib/python2.7/site-packages/django_allauth-0.34.0-py2.7.egg/allauth/account/views.py", line 283, in post resp = self.login_on_confirm(confirmation) File "/usr/lib/python2.7/site-packages/django_allauth-0.34.0-py2.7.egg/allauth/account/views.py", line 332, in login_on_confirm redirect_url=self.get_redirect_url) File "/usr/lib/python2.7/site-packages/django_allauth-0.34.0-py2.7.egg/allauth/account/utils.py", line 157, in perform_login get_login_redirect_url(request, redirect_url)) File "/usr/lib/python2.7/site-packages/django_allauth-0.34.0-py2.7.egg/allauth/account/utils.py", line 50, in get_login_redirect_url url = url() File "/usr/lib/python2.7/site-packages/django_allauth-0.34.0-py2.7.egg/allauth/account/views.py", line 362, in get_redirect_url self.request) File "/usr/lib/python2.7/site-packages/django_allauth-0.34.0-py2.7.egg/allauth/account/adapter.py", line 176, in get_email_confirmation_redirect_url return self.get_login_redirect_url(request) File "/usr/lib/python2.7/site-packages/django_allauth-0.34.0-py2.7.egg/allauth/account/adapter.py", line 156, in get_login_redirect_url return resolve_url(url) File "/usr/lib/python2.7/site-packages/django/shortcuts.py", line 205, in resolve_url return urlresolvers.reverse(to, args=args, kwargs=kwargs) File "/usr/lib/python2.7/site-packages/django/core/urlresolvers.py", line 579, in reverse return force_text(iri_to_uri(resolver._reverse_with_prefix(view, prefix, *args, **kwargs))) File "/usr/lib/python2.7/site-packages/django/core/urlresolvers.py", line 496, in _reverse_with_prefix (lookup_view_s, args, kwargs, len(patterns), patterns)) NoReverseMatch: Reverse for '' with arguments '()' and keyword arguments '{}' not found. 0 pattern(s) tried: [] --8<---------------cut here---------------end--------------->8--- What could be the reason, and how could I solve this issue please? Since it's perhaps related, here is my urls.py: --8<---------------cut here---------------start------------->8--- from django.conf.urls import include, url from django.contrib import admin from postorius.views.list import list_index urlpatterns = [ url(r'^postorius/', include('postorius.urls')), url(r'^archives/', include('hyperkitty.urls')), url(r'', include('django_mailman3.urls')), url(r'^accounts/', include('allauth.urls')), url(r'^admin/', include(admin.site.urls)), url(r'^$', list_index, name='list_index'), ] --8<---------------cut here---------------end--------------->8--- TIA for any help, -- Peter

2 4

setup of URLs
by Peter Münster 29 Jan '18

29 Jan '18

Hi, I would like to point "https://my-domain.org/" to the list of mailing-lists of this domain. How should I setup my Apache configuration and/or the urlpatterns please? With my actual configuration, the above URL is always rewritten to https://my-domain.org/postorius/lists/ These are my urlpatterns: urlpatterns = [ url(r'^$', RedirectView.as_view( url=reverse_lazy('list_index'), permanent=True)), url(r'^postorius/', include('postorius.urls')), url(r'^archive/', include('hyperkitty.urls')), url(r'', include('django_mailman3.urls')), url(r'^accounts/', include('allauth.urls')), url(r'^admin/', include(admin.site.urls)), ] TIA for any help, -- Peter

4 4

Where is postorius.wsgi?
by Peter Münster 28 Jan '18

28 Jan '18

Hi, I try to install Postorius, but I don't find the file postorius.wsgi. Where should I get it please? This is, what I've done so far: - git clone https://gitlab.com/mailman/postorius.git - cd postorius - python3 setup.py install - cd example_project - virtualenv venv - . venv/bin/activate - pip3 install -r requirements.txt - in venv/lib/python3.6/site-packages/django_mailman3/lib/mailman.py: replace "urllib2" by "urllib.error" - python3 manage.py migrate - python3 manage.py createsuperuser - python3 manage.py compilemessages - python3 manage.py collectstatic Now I try to follow https://postorius.readthedocs.io/en/latest/deployment.html#apache-with-mod-… but I don't find postorius.wsgi ... TIA for any help. Kind regards, -- Peter

5 10

OperationalError: database is locked
by cyp＠trojina.si 25 Jan '18

25 Jan '18

On our installation, we are often gettting Internal Server Error (500). The logs look like this: ERROR 2018-01-09 13:52:57,640 1604 django.request Internal Server Error: /hyperkitty/list/test(a)seznami.cjvt.si/ Traceback (most recent call last): File "/opt/mailman/venv2/local/lib/python2.7/site-packages/Django-1.10.7-py2.7.egg/django/core/handlers/exception.py", line 42, in inner response = get_response(request) File "/opt/mailman/venv2/local/lib/python2.7/site-packages/Django-1.10.7-py2.7.egg/django/core/handlers/base.py", line 249, in _legacy_get_response response = self._get_response(request) File "/opt/mailman/venv2/local/lib/python2.7/site-packages/Django-1.10.7-py2.7.egg/django/core/handlers/base.py", line 187, in _get_response response = self.process_exception_by_middleware(e, request) File "/opt/mailman/venv2/local/lib/python2.7/site-packages/Django-1.10.7-py2.7.egg/django/core/handlers/base.py", line 185, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/opt/mailman/venv2/local/lib/python2.7/site-packages/HyperKitty-1.1.0-py2.7.egg/hyperkitty/lib/view_helpers.py", line 133, in inner mlist = MailingList.objects.get(name=mlist_fqdn) File "/opt/mailman/venv2/local/lib/python2.7/site-packages/Django-1.10.7-py2.7.egg/django/db/models/manager.py", line 85, in manager_method return getattr(self.get_queryset(), name)(*args, **kwargs) File "/opt/mailman/venv2/local/lib/python2.7/site-packages/Django-1.10.7-py2.7.egg/django/db/models/query.py", line 379, in get num = len(clone) File "/opt/mailman/venv2/local/lib/python2.7/site-packages/Django-1.10.7-py2.7.egg/django/db/models/query.py", line 238, in __len__ self._fetch_all() File "/opt/mailman/venv2/local/lib/python2.7/site-packages/Django-1.10.7-py2.7.egg/django/db/models/query.py", line 1087, in _fetch_all self._result_cache = list(self.iterator()) File "/opt/mailman/venv2/local/lib/python2.7/site-packages/Django-1.10.7-py2.7.egg/django/db/models/query.py", line 54, in __iter__ results = compiler.execute_sql() File "/opt/mailman/venv2/local/lib/python2.7/site-packages/Django-1.10.7-py2.7.egg/django/db/models/sql/compiler.py", line 835, in execute_sql cursor.execute(sql, params) File "/opt/mailman/venv2/local/lib/python2.7/site-packages/Django-1.10.7-py2.7.egg/django/db/backends/utils.py", line 64, in execute return self.cursor.execute(sql, params) File "/opt/mailman/venv2/local/lib/python2.7/site-packages/Django-1.10.7-py2.7.egg/django/db/utils.py", line 94, in __exit__ six.reraise(dj_exc_type, dj_exc_value, traceback) File "/opt/mailman/venv2/local/lib/python2.7/site-packages/Django-1.10.7-py2.7.egg/django/db/backends/utils.py", line 64, in execute return self.cursor.execute(sql, params) File "/opt/mailman/venv2/local/lib/python2.7/site-packages/Django-1.10.7-py2.7.egg/django/db/backends/sqlite3/base.py", line 337, in execute return Database.Cursor.execute(self, query, params) OperationalError: database is locked Does this suggest I should switch from sqlite to postgres (https://stackoverflow.com/a/26864360)? I'm happy to do that, but how do I migrate the data between the databases (after installing postgres and creating the database)? I've found this doc (http://mailman.readthedocs.io/en/latest/src/mailman/docs/database.html#data…), but I don't think I understand this and I haven't used alembic: these instructions are just for when you modify the model within the same database, right? Thanks in advance!

4 9

Solved issues not in Docker-mailman rolling releases
by Henrik Rasmussen 25 Jan '18

25 Jan '18

I am currently using Docker-mailman rolling releases and with great respect to the maintainer's time it was my impression from @maxking that rolling releases was likely to be one week behind the development. In my report of https://gitlab.com/mailman/mailman/issues/444 @msapiro commented that #444 is a duplicate of #406 (closed) which was fixed by !322 (merged), but !322 was merged a month ago. Thinking that I wasn't up to speed, I did a `docker pull quay.io/maxking/mailman-core:rolling` only got 'XXXXXXXXXXXX: Already exists'. Also `docker images` shows 'quay.io/maxking/mailman-core rolling 1654a3226db8 7 weeks ago 179.3 MB'. Not to be umpolite, did I misunderstand the concept?

2 3

Postorius: Show only own lists
by Thor Atle Rustad 23 Jan '18

23 Jan '18

Imagine an installation with 500+ mailing lists and almost as many local admins that are supposed to maintain their own local lists with a few local members. As site admin, I see all 500+ lists, but I was expecting *local* admins to see only the lists they maintain. I have set all lists to "advertised = False", so they are hidden from ordinary view. Is there a way to show only relevant lists to local admins? I am running docker running release. mailman info GNU Mailman 3.2.0a1 (La Villa Strangiato) Thor Atle Rustad

4 6

mailing list aliases
by Dmitry Makovey 20 Jan '18

20 Jan '18

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 19 Jan '18

19 Jan '18

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 18 Jan '18

18 Jan '18

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