- Mailman-users - lists.mailman3.org

MTA setup
by Arte Chambers 23 Dec '24

23 Dec '24

I've got a new installation of Mailman 3 setup, however I am having some issues I'm not sure how to troubleshoot. Mailman is successfully sending invite emails however user messages sent to the list are not being sent to subscribers. Also in Hyperkitty none of my test messages to the list are showing up in the archive. I am using Postfix with an SMTP relay hosted at Brevo.com (formally sendinblue). Brevo's logs show the message getting rejected Log from brevo.com (SMPT Relay) Sent on 17-11-2024 21:49:16 From listmember(a)gmail.com To listmember(a)gmail.com Message ID<CAPesOD1y0fEaG=GFodz=Lgs1m_hqRErPnQcpXCNtKsBbJ= BJ7Q(a)mail.gmail.com> 17-11-2024 21:49:16 Sending has been rejected because the sender you used listmember(a)gmail.com is not valid. Validate your sender or authenticate your domain >>>Postfix main.cf # See /usr/share/postfix/main.cf.dist for a commented, more complete version # Debian specific: Specifying a file name will cause the first # line of that file to be used as the name. The Debian default # is /etc/mailname. #myorigin = /etc/mailname smtpd_banner = $myhostname ESMTP $mail_name (Ubuntu) biff = no # appending .domain is the MUA's job. append_dot_mydomain = no # Uncomment the next line to generate "delayed mail" warnings #delay_warning_time = 4h readme_directory = no # See http://www.postfix.org/COMPATIBILITY_README.html -- default to 3.6 on # fresh installs. compatibility_level = 3.6 # TLS parameters smtpd_tls_cert_file=/etc/ssl/certs/ssl-cert-snakeoil.pem smtpd_tls_key_file=/etc/ssl/private/ssl-cert-snakeoil.key smtpd_tls_security_level=may smtp_tls_CApath=/etc/ssl/certs smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache smtpd_relay_restrictions = permit_mynetworks permit_sasl_authenticated defer_unauth_destination myhostname = list.louisvillecommunitygrocery.com alias_maps = hash:/etc/aliases alias_database = hash:/etc/aliases myorigin = $myhostname mydestination = $myhostname, list.louisvillecommunitygrocery.com, localhost.louisvillecommunitygrocery.com, , localhost mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128 mailbox_size_limit = 0 recipient_delimiter = + inet_interfaces = all inet_protocols = all # Mailman3 configs # Support the default VERP delimiter. recipient_delimiter = + unknown_local_recipient_reject_code = 550 owner_request_special = no transport_maps = hash:/opt/mailman/mm/var/data/postfix_lmtp local_recipient_maps = hash:/opt/mailman/mm/var/data/postfix_lmtp relay_domains = hash:/opt/mailman/mm/var/data/postfix_domains #SMPT Relay Brevo relayhost = [smtp-relay.sendinblue.com]:587 smtp_sasl_auth_enable = yes smtp_sasl_security_options = noanonymous smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd smtp_tls_security_level = encrypt smtp_tls_CAfile = /etc/ssl/certs/ca-certificates.crt *In closing*, can anyone point me in the right direction for further troubleshooting on this issue? Thank you, Paul 'Arte Chambers' Robey

2 8

Clean-up of non-members
by Torge Riedel 23 Dec '24

23 Dec '24

Dears, I am currently cleaning up a huge list of non-members. In contrast to the members list where I can select multiple entries and delete them at once, this is not possible in the list of non-members? Can this be enabled in a future release? Thank you and kind regards Torge

3 4

MM2 to MM3 Archives Loading
by Joshua Bushe 22 Dec '24

22 Dec '24

Hi everyone, I’ve successfully converted a list from Mailman 2 to Mailman 3, and most things are working smoothly. However, I’m encountering an issue with the archives in the GUI: Problem: The archives don’t load on the overview page. Odd Behavior: If I use the search function, the archives appear as expected, but they remain invisible on the main overview. Has anyone encountered this issue or have suggestions for troubleshooting? Thanks in advance for your help!

5 15

Flooded non-members with "prvs=<number>=<mail>"
by Torge Riedel 22 Dec '24

22 Dec '24

Dears, I checked the non-members list of all my mailman3 lists and found a lot entries like "prvs=<number>=<mail>", the <mail> is always an address from @freenet.de A quick research mentions something related to bouncing and that such mails should be blocked/filtered. But no further details. Can you give a hint where I need to change what to block such mails and avoid that such entries floods the non-members list? Thank you and kind regards Torge

2 1

Poor rendering of disabled registration page
by Torge Riedel 22 Dec '24

22 Dec '24

Dears, I have set ACCOUNT_ADAPTER = 'django_mailman3.views.user_adapter.DisableSignupAdapter' in my settings.py, so clicking on the "Registration+" button shows a page that registration is disabled: 1. The page has a poor rendering, as far as I can see not css is referenced 2. A would prefer that I am able to hide the registration button Is either of this possible to be fixed in the future? Thank you and kind regards Torge

2 1

Cache mailman3
by pau.baiges＠csuc.cat 22 Dec '24

22 Dec '24

Is there a way to delete the mailman3 cache? It's because it gives us this error and we think it's because of the cache. Internal Server Error: /mailman3/accounts/login/ TemplateDoesNotExist at /accounts/login/ django_saml2_auth/error.html Request Method: GET Request URL: http://llistes.csuc.cat/mailman3/accounts/login/?next=/mailman3/postorius/l… Django Version: 2.2.12 Python Executable: /usr/bin/uwsgi-core Python Version: 3.8.10 Python Path: ['.', '', '/usr/lib/python38.zip', '/usr/lib/python3.8', '/usr/lib/python3.8/lib-dynload', '/usr/local/lib/python3.8/dist-packages', '/usr/lib/python3/dist-packages'] Server time: dv., 15 Març 2024 10:33:00 +0100 Installed Applications: ('hyperkitty', 'postorius', 'django_mailman3', 'django.contrib.admin', 'django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.sites', 'django.contrib.messages', 'django.contrib.staticfiles', 'rest_framework', 'django_gravatar', 'compressor', 'haystack', 'django_extensions', 'django_q', 'allauth', 'allauth.account', 'allauth.socialaccount', 'django_mailman3.lib.auth.fedora') Installed Middleware: ('django.contrib.sessions.middleware.SessionMiddleware', 'django.middleware.common.CommonMiddleware', 'django.middleware.csrf.CsrfViewMiddleware', 'django.middleware.locale.LocaleMiddleware', 'django.contrib.auth.middleware.AuthenticationMiddleware', 'django.contrib.messages.middleware.MessageMiddleware', 'django.middleware.clickjacking.XFrameOptionsMiddleware', 'django.middleware.security.SecurityMiddleware', 'django_mailman3.middleware.TimezoneMiddleware', 'postorius.middleware.PostoriusMiddleware') Template loader postmortem Django tried loading these templates, in this order: Using engine django: This engine did not provide a list of tried templates. Traceback: File "/usr/local/lib/python3.8/dist-packages/django_saml2_auth/utils.py" in wrapper 179. result = function(request) File "/usr/local/lib/python3.8/dist-packages/django_saml2_auth/views.py" in signin 271. saml_client = get_saml_client(get_assertion_url(request), acs) File "/usr/local/lib/python3.8/dist-packages/django_saml2_auth/saml.py" in get_saml_client 169. metadata = get_metadata(user_id) File "/usr/local/lib/python3.8/dist-packages/django_saml2_auth/saml.py" in get_metadata 131. raise SAMLAuthError("Invalid metadata URL.", extra={ During handling of the above exception (Invalid metadata URL.), another exception occurred: File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py" in inner 34. response = get_response(request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py" in _get_response 115. response = self.process_exception_by_middleware(e, request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py" in _get_response 113. response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/local/lib/python3.8/dist-packages/django_saml2_auth/utils.py" in wrapper 181. result = handle_exception(exc, request) File "/usr/local/lib/python3.8/dist-packages/django_saml2_auth/utils.py" in handle_exception 162. return render(request, File "/usr/lib/python3/dist-packages/django/shortcuts.py" in render 36. content = loader.render_to_string(template_name, context, request, using=using) File "/usr/lib/python3/dist-packages/django/template/loader.py" in render_to_string 61. template = get_template(template_name, using=using) File "/usr/lib/python3/dist-packages/django/template/loader.py" in get_template 19. raise TemplateDoesNotExist(template_name, chain=chain) Exception Type: TemplateDoesNotExist at /accounts/login/ Exception Value: django_saml2_auth/error.html Request information: USER: AnonymousUser

3 2

Error: Module "django.contrib.sessions.serializers" does not define a "PickleSerializer" attribute/class
by Torge Riedel 22 Dec '24

22 Dec '24

Dears, I just upgraded my Server from Ubuntu 22.04 to 24.04 and I get the following error when accessing the web page. Django is 5.0.10 Postorius is 1.3.13 Any help is welcome. Thank you and kind regards Torge Internal Server Error:/mailman3/lists/ ImportError at/mailman3/lists/ Module "django.contrib.sessions.serializers" does not define a "PickleSerializer" attribute/class Request Method: GET Request URL:https://lists.lsv-pinneberg.de/mailman3/lists/ Django Version: 5.0.10 Python Executable: /usr/bin/uwsgi-core Python Version: 3.12.3 Python Path: ['.', '', '/usr/lib/python312.zip', '/usr/lib/python3.12', '/usr/lib/python3.12/lib-dynload', '/opt/mailman/web/venv/lib/python3.12/site-packages'] Server time: Sun, 22 Dec 2024 11:05:00 +0100 Installed Applications: ('hyperkitty', 'postorius', 'django_mailman3', 'django.contrib.admin', 'django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.sites', 'django.contrib.messages', 'django.contrib.staticfiles', 'rest_framework', 'django_gravatar', 'compressor', 'haystack', 'django_extensions', 'django_q', 'allauth', 'allauth.account', 'allauth.socialaccount') Installed Middleware: ('django.contrib.sessions.middleware.SessionMiddleware', 'django.middleware.common.CommonMiddleware', 'django.middleware.csrf.CsrfViewMiddleware', 'django.middleware.locale.LocaleMiddleware', 'django.contrib.auth.middleware.AuthenticationMiddleware', 'django.contrib.messages.middleware.MessageMiddleware', 'django.middleware.clickjacking.XFrameOptionsMiddleware', 'django.middleware.security.SecurityMiddleware', 'django_mailman3.middleware.TimezoneMiddleware', 'postorius.middleware.PostoriusMiddleware', 'allauth.account.middleware.AccountMiddleware') Traceback (most recent call last): File "/opt/mailman/web/venv/lib/python3.12/site-packages/django/utils/module_loading.py", line 30, in import_string return cached_import(module_path, class_name) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/web/venv/lib/python3.12/site-packages/django/utils/module_loading.py", line 16, in cached_import return getattr(module, class_name) ^^^^^^^^^^^^^^^^^^^^^^^^^^^ The above exception (module 'django.contrib.sessions.serializers' has no attribute 'PickleSerializer') was the direct cause of the following exception: File "/opt/mailman/web/venv/lib/python3.12/site-packages/django/core/handlers/exception.py", line 55, in inner response = get_response(request) ^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/web/venv/lib/python3.12/site-packages/django/utils/deprecation.py", line 133, in __call__ response = self.process_request(request) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/web/venv/lib/python3.12/site-packages/django/contrib/sessions/middleware.py", line 20, in process_request request.session = self.SessionStore(session_key) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/web/venv/lib/python3.12/site-packages/django/contrib/sessions/backends/db.py", line 16, in __init__ super().__init__(session_key) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/web/venv/lib/python3.12/site-packages/django/contrib/sessions/backends/base.py", line 47, in __init__ self.serializer = import_string(settings.SESSION_SERIALIZER) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/web/venv/lib/python3.12/site-packages/django/utils/module_loading.py", line 32, in import_string raise ImportError( ^^^^^^^^^^ Exception Type: ImportError at/mailman3/lists/ Exception Value: Module "django.contrib.sessions.serializers" does not define a "PickleSerializer" attribute/class Raised during: postorius.views.list.list_index

1 1

Subscription requires confirmation when list is set as Open
by Mark 21 Dec '24

21 Dec '24

Hi All, I have a list set with the following ... List Settings > Member Policy # Subscription Policy = "Open" When I subscribe with an email address that has been used (subscribed/unsubscribed) on any other list (on that server), the address is subscribed automatically. However, if I subscribe with an address that has never been used before, I receive an email that requires me to confirm the subscription. The subscription is also held in the administrator's "Subscription requests: Pending confirmation". This happens when subscribing by both email and the web UI. Ideally, as the Policy is set as "Open", the subscription of any new email address should be added automatically. Have I missed a configuration setting somewhere? Any advice really appreciated. Regards, Mark $ mailman info GNU Mailman 3.3.9 (Tom Sawyer) Python 3.11.2 (main, Mar 13 2023, 12:18:29) [GCC 12.2.0] Venv installation on Debian

3 7

Re: mail stuck in "out" queue
by Dmitry Makovey 18 Dec '24

18 Dec '24

So our mailman got stuck again, but I did follow your advise. Here's what I've found: On 3/29/19 2:58 PM, Mark Sapiro wrote: > On 3/29/19 2:28 PM, Dmitry Makovey wrote: >> I've had encountered this situation now twice: mail is being stuck in >> "out" queue and nothing in the logs indicates the issue. Is there a way >> to ask mailman-core politely to attempt delivery (perhaps with increased >> debugging in the logs) *without* restarting the core (which does solve >> *this* problem but creates other problems, like availability of the >> mailman as a whole) > > > Is the "out" runner running? yes: # docker top mailman-core | grep -F out: 100 21681 13215 0 Mar28 ? 01:14:16 /usr/local/bin/python /usr/local/bin/runner --runner=out:0:1 -C /etc/mailman.cfg > ps -fwwA |grep runner=out > > If not, you should be able to start it as the Mailman user with a > command like > > /path/to/python3 /path/to/mailman/bin/runner -C /path/to/mailman.cfg > --runner=out:0:1 > > See 'ps -fwwA|grep runner' for examples > > If the out runner is running, is there a file named *.bak along with all > the *.pck files in queue/out/ there is one, yes: # ls -l /srv/mail/mailman/core/var/queue/out/*.bak -rw-rw---- 1 100 65533 21512 Apr 14 19:45 /srv/mail/mailman/core/var/queue/out/1555296331.8386078+2c905825b82708e5a682b872b0aff320c9dd0b2e.bak what does it indicate and what should my steps be to resolve this (other than restarting queues)? > And if it's not, is there anything in Mailman's logs to indicate why it > died? > > Also, 'mailman restart' should only take a matter of seconds, but if the > out runner is running but not processing its queue, I think sending it a > SIGINT should restart it. SIGINT killed the process allright, but it didn't auto-respawn. I ended up spawning it with: /usr/local/bin/python /usr/local/bin/runner --runner=out:0:1 -C /etc/mailman.cfg but soon realized it doesn't go to background nicely so I've nohup'ed it in the end. but it did solve my problem. -- Sr System and DevOps Engineer SoM IRT

6 17

Upgrading other python packages than the mailman ones in a venv results in dependency conflicts
by Ulf R. 17 Dec '24

17 Dec '24

Hello, I know this should be the way to upgrade: https://docs.mailman3.org/en/latest/upgrade-guide.html I have 3.3.10 installed. I saw that some python packages are outdated an tried this which install all outdated packages in a row: pip list --outdated --format=json | jq '.[].name' | xargs -n1 pip install -U One outdated package was django and this part happened: ------------------------------- vDownloading Django-5.1.4-py3-none-any.whl (8.3 MB) Installing collected packages: Django Attempting uninstall: Django Found existing installation: Django 4.2.16 Uninstalling Django-4.2.16: Successfully uninstalled Django-4.2.16 ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts. hyperkitty 1.3.12 requires django<5.1,>=4.2, but you have django 5.1.4 which is incompatible. mailman-web 0.0.9 requires django<4.3,>=4.0, but you have django 5.1.4 which is incompatible. postorius 1.3.13 requires django<5.1,>=4.2, but you have django 5.1.4 which is incompatible. django-mailman3 1.3.15 requires django<5.1,>=4.2, but you have django 5.1.4 which is incompatible. Successfully installed Django-5.1.4 ------------------------------- So I made a roll back. Is this really the only secure way to update the venv?: pip install -U mailman postorius django-mailman3 hyperkitty mailman-web May be yes and I have to ignore the rest? ;-) Thank you und regards

4 3