- Mailman-users - lists.mailman3.org

Rebuilding a list index fails
by Mark Dadgar Feb. 18, 2021

Feb. 18, 2021

Now that I’ve got my instance back up and running on the latest released code, I am trying to rebuild a list index. I am using Xapian via haystack, which worked beautifully before my recent list meltdown. Error messages below. rebuild_index fails with the same error. This is with django version 3.0.12. I am sure I missed reinstalling something or there’s a version mismatch. Thoughts? - Mark ----- mark(a)pdc-racing.net | 408-348-2878 —— (venv) mailman@mail:/opt/mailman/mm/bin$ ./django-admin update_index_one_list xxxxxxs(a)pdc-racing.net Traceback (most recent call last): File "/opt/mailman/mm/venv/bin/django-admin", line 8, in <module> sys.exit(execute_from_command_line()) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/core/management/__init__.py", line 401, in execute_from_command_line utility.execute() File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/core/management/__init__.py", line 395, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/core/management/base.py", line 328, in run_from_argv self.execute(*args, **cmd_options) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/core/management/base.py", line 369, in execute output = self.handle(*args, **options) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/hyperkitty/management/commands/update_index_one_list.py", line 41, in handle update_index(listname=options.get("listname")[0], File "/opt/mailman/mm/venv/lib/python3.8/site-packages/hyperkitty/search_indexes.py", line 117, in update_index update_cmd.update_backend("hyperkitty", "default") File "/opt/mailman/mm/venv/lib/python3.8/site-packages/haystack/management/commands/update_index.py", line 280, in update_backend backend = haystack_connections[using].get_backend() File "/opt/mailman/mm/venv/lib/python3.8/site-packages/haystack/utils/loading.py", line 115, in __getitem__ self.thread_local.connections[key] = load_backend( File "/opt/mailman/mm/venv/lib/python3.8/site-packages/haystack/utils/loading.py", line 61, in load_backend return import_class(full_backend_path) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/haystack/utils/loading.py", line 23, in import_class module_itself = importlib.import_module(module_path) File "/usr/lib/python3.8/importlib/__init__.py", line 127, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "<frozen importlib._bootstrap>", line 1014, in _gcd_import File "<frozen importlib._bootstrap>", line 991, in _find_and_load File "<frozen importlib._bootstrap>", line 975, in _find_and_load_unlocked File "<frozen importlib._bootstrap>", line 671, in _load_unlocked File "<frozen importlib._bootstrap_external>", line 783, in exec_module File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed File "/opt/mailman/mm/venv/lib/python3.8/site-packages/xapian_backend.py", line 10, in <module> from django.utils import six ImportError: cannot import name 'six' from 'django.utils' (/opt/mailman/mm/venv/lib/python3.8/site-packages/django/utils/__init__.py)

3 5

3rd Party Account is not working
by kwp.klein＠gmail.com Feb. 17, 2021

Feb. 17, 2021

I installed Mailman 3 with Postfix. I try to login with the 3rd Party Account. It is not possible, because I get this error message: Server error An error occurred while processing your request.

7 13

ham-confirm+3ee85b006eeb5897ca6f53b093cb063672f6a784@example.com
by Jörg Klein Feb. 17, 2021

Feb. 17, 2021

I want add some subscribers. When the I get this error message: I have no address ham-request(a)example.com. Do I need for every mailing list more as the mailing list email address? Final-Recipient: rfc822; ham-request(a)example.com Action: failed Status: 5.0.0 Remote-MTA: dns; mx0.example.com. (80.237.138.5, the server for the domain example.com.) Diagnostic-Code: smtp; 550 Address invalid (ID:550:1:1 (mi015.mc1.hosteurope.de)) Last-Attempt-Date: Wed, 17 Feb 2021 01:13:18 -0800 (PST)

2 3

List is down - RemovedInDjango30Warning
by Mark Dadgar Feb. 17, 2021

Feb. 17, 2021

So I did the latest mailman upgrades within my venv (per the instructions got from Brian Carpenter when he installed it for me) to the latest version. I had a strange CPU pegging issue that turned out to be mailman struggling with a malformed message but in the process of debugging that I downgraded to the previous mailman release. The resulted in a broken web interface. Today, while debugging, I did a pip install --upgrade of all the components as listed in a previous thread. Now none of the mailman3 processes will start. Doing a bin/mailman-post-update results in the error message below, which are consistent with the issues I saw earlier when trying to access the web interface. Anyone got a solution to this? I suspect it’s something simple, but django is just not my area of expertise. Thanks! - Mark ----- mark(a)pdc-racing.net | 408-348-2878 ——— (venv) mailman@mail:/opt/mailman/mm/bin$ ./mailman-post-update + '[' False == False ']' + mkdir -p /opt/mailman/mm/static + /opt/mailman/mm/bin/django-admin collectstatic --clear --noinput --verbosity 0 + /opt/mailman/mm/bin/django-admin compress Traceback (most recent call last): File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/template/utils.py", line 66, in __getitem__ return self._engines[alias] KeyError: 'django' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/template/backends/django.py", line 121, in get_package_libraries module = import_module(entry[1]) File "/usr/lib/python3.8/importlib/__init__.py", line 127, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "<frozen importlib._bootstrap>", line 1014, in _gcd_import File "<frozen importlib._bootstrap>", line 991, in _find_and_load File "<frozen importlib._bootstrap>", line 975, in _find_and_load_unlocked File "<frozen importlib._bootstrap>", line 671, in _load_unlocked File "<frozen importlib._bootstrap_external>", line 783, in exec_module File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/contrib/admin/templatetags/admin_static.py", line 5, in <module> from django.utils.deprecation import RemovedInDjango30Warning ImportError: cannot import name 'RemovedInDjango30Warning' from 'django.utils.deprecation' (/opt/mailman/mm/venv/lib/python3.8/site-packages/django/utils/deprecation.py) During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/opt/mailman/mm/venv/bin/django-admin", line 8, in <module> sys.exit(execute_from_command_line()) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/core/management/__init__.py", line 401, in execute_from_command_line utility.execute() File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/core/management/__init__.py", line 395, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/core/management/base.py", line 328, in run_from_argv self.execute(*args, **cmd_options) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/core/management/base.py", line 369, in execute output = self.handle(*args, **options) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/compressor/management/commands/compress.py", line 277, in handle self.handle_inner(**options) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/compressor/management/commands/compress.py", line 300, in handle_inner offline_manifest, block_count, results = self.compress(engine, extensions, verbosity, follow_links, log) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/compressor/management/commands/compress.py", line 100, in compress if not self.get_loaders(): File "/opt/mailman/mm/venv/lib/python3.8/site-packages/compressor/management/commands/compress.py", line 50, in get_loaders for e in engines.all(): File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/template/utils.py", line 90, in all return [self[alias] for alias in self] File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/template/utils.py", line 90, in <listcomp> return [self[alias] for alias in self] File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/template/utils.py", line 81, in __getitem__ engine = engine_cls(params) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/template/backends/django.py", line 25, in __init__ options['libraries'] = self.get_templatetag_libraries(libraries) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/template/backends/django.py", line 43, in get_templatetag_libraries libraries = get_installed_libraries() File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/template/backends/django.py", line 108, in get_installed_libraries for name in get_package_libraries(pkg): File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/template/backends/django.py", line 123, in get_package_libraries raise InvalidTemplateLibrary( django.template.library.InvalidTemplateLibrary: Invalid template library specified. ImportError raised when trying to load 'django.contrib.admin.templatetags.admin_static': cannot import name 'RemovedInDjango30Warning' from 'django.utils.deprecation' (/opt/mailman/mm/venv/lib/python3.8/site-packages/django/utils/deprecation.py)

2 2

Imported Digest Settings
by Brian Carpenter Feb. 17, 2021

Feb. 17, 2021

I am still seeing digest formatting issues with the import of Mailman 2 lists into Mailman 3. I am running the latest stable version of Mailman 3 core which is 3.3.3. This is what my client reported: > For the last three REDACTED digests I have been getting unusual and > unreadable characters? See example below. > >> Begin forwarded message: >> >> *From: *REDACTED >> *Subject: *REDACTED*Digest, Vol 2453, Issue 2* >> *Date: *February 13, 2021 at 12:30:24 AM PST >> *To: *REDACTED@REDACTED >> *Reply-To: *REDACTED@REDACTED >> >> �P*+]4�LaG@��[� S� XZ[ [�� \� �X�Z\��[ۜ� ‚] [� [�ܙ‚� � �X��ܚX�H ܈ >> [��X��ܚX�H �XH [XZ[ �[� H Y\��Y�H �] �X�X� ܂�� H� [ � ‚] [�\�\]Y\� >> [�ܙ‚�[�H �[� �XX� H \��ۈ X[�Y�[�� H \� ] �] [�[#<^_NSEDR_^#<ۙ\� >> [�ܙ‚�� [� �\ Z[�� X\�H Y ] [�\� �X�X� [�H �� ] \� [ܙH � X�Y�X [� �N� >> �۝ [� � و S� Y�\� �� ^I�� X�΂� K� �N� [� \� � [\ � >> �� ] >> \�B�KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKB�Y\��Y�N�B� >> ] N� �K L� �X��HL ��N�� L ��N� �� ] \� �� ] >> \�]\�X˘��O��X�X� � � S�H �N� [� \� � [\ • Έ �� [�Y[ �� [�Y[ >> ]ܙ[��K�Y O��Έ � S� H �[\ ] ^Y\�� [� \�] [ۘ[ �] �ܚˈ� [� >> [�ܙς�Y\��Y�KRQ � Q� >> � >> KM�� M� N Q �P��PL �P �] \�]\�X˘��O��۝ [� U \ N� ][ \ \� �[ \�] >> ]�N‚X��[� \�OP\ KSXZ[ M ь P�KL�L�KM ��KP�KM��̌#<^_NSEDR_^#<͌ >> L �Y\� H [�� YX�� H \� Y �[[^H [� � X� \� [�� Y] [�� Y�ܙH H Y� >> \� [� ] �Y[\� �\� Y [� �� \�H ��\ ] H ] [ � H �\� ۙH و \� � Y [� ˈ [ >> [�� ]�\�] [�� H �]�H YK �\� [� ]�Y X[ \ \�� [� �\�[ [�� X� [ۜˈ H >> �\�[ [�� X� [ۋ �H �\� �\� H [�� [\ ܝ [� [� �[ XX� H \� � H ۸�&] [�� >> H �]�H [ و \� � Y [� � H �[YH X] \�X[ ˈ ] �\� H ]X� [ܙH >> \�#<^_NSEDR_^#<ۘ[ ^�Y \ ��X� �܈ XX� � Y [� � H ��Y� \� �� ] H [� >> ܚ] [� � Y� H �]�H YH H \�� Y [� ]�[� ] � �� Y\� >> [�H ]�H � �H � � ۛ�� Y� ] \�JK ��\� �܈ �^[ۙ ] � [�� ] \��[� >> ��H ^H T ۙB� ۈ �X�L So the questions I have are: 1. Why does the formatting of digests change for some members when coming from MM2 to MM3? 2. What proble does the above example reveal? 3. What is the best approach to mitigate these issues? What I did: I had the client change the list member's digest setting from plain-text to mime. Was that the right instruction to do? -- Brian Carpenter Harmonylists.com Emwd.com

2 6

Bottom line of message footer
by Tom Stoddard Feb. 15, 2021

Feb. 15, 2021

Here's another question that I have. A regular message just came into my email from one of the lists I'm a member of and it had a 3 line footer. The first two lines are fine, they just include the list's email address and an address to send unsubscribe requests to. The third line is this: %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s It looks to me like it should be a link to the group's list info page. Is this a bug or is there something I can do to fix it? It looks like it might be missing a forward slash after the first "s".

3 2

Unknown templates being used
by Tom Stoddard Feb. 15, 2021

Feb. 15, 2021

I'm a list owner who has recently (within the last week) had my lists migrated from mailman 2 to mailman 3. The UI that we are using is Affinity. I've reviewed all of the list templates and begun to customize some of them. My issue is that I'm receiving messages that don't match any of the templates. Here is an example of one that I just received this morning. (The x's are inserted by me. The actual message provided valid addresses.) The xxxxxxxxxx(a)xxxxxxxxxx.org list has 1 moderation requests waiting. Held Subscriptions: User:xxxxxxxxxx@gmail.com Please attend to this at your earliest convenience. When I log in to review the request it appears to be a subscription request awaiting approval. I had previously modified the "Moderator Approval Subscription" template, which is what I would expect to have received in this circumstance. I administer several lists and have received some messages that do use the newly modified template so I assume I did it correctly. Any idea where the template for this message came from? Thanks!

3 5

Dealing with recipients' servers spam filtering
by Gilles Filippini Feb. 13, 2021

Feb. 13, 2021

Hi, I run a mailman3 instance with mainly private lists for which I know and trust every single member. Some of them have Hotmail email addresses, and the messages they send though our lists are rejected as being spam by most of the recipients' mail servers, while these are legitimate emails. I'd welcome any pointer to best practices / howtos regarding mailman3 / exim4 configuration to mitigate this problem. Many thanks in advance, _g.

3 5

Mailman 3 installation from latest Debian packages
by Matthew Blissett Feb. 12, 2021

Feb. 12, 2021

Hi, I've installed mailman3-full 3.3.3-1 from Debian bullseye (Debian testing). The dropdown controls on the UI for Postorius (e.g. "Subscription requests", "Mass operations" and the username button to log out) and the similar controls on Hyperkitty (e.g. "Threads by month") do not work. You can see the latter at http://newlistszm.gbif.org/mailman3/hyperkitty/list/test@newlistszm.gbif.or… I found https://lists.gem5.org/archives/list/gem5-announce@gem5.org/ which is running the same version, but presumably not using these Debian packages as the Javascript is slightly different. Could this be a problem with the Debian packaging, or perhaps my configuration -- which is very close to the defaults (i.e. Mailman and Apache configuration generated by dpkg). Has anyone set up a working installation using these packages? Thanks, Matt Blissett PS, I wrote a similar message earlier in the week to a Debian list: https://alioth-lists.debian.net/pipermail/pkg-mailman-hackers/2021-February…

4 3

Innstall and run Mailman 3 with Postfix in a Docker enviroment
by kwp.klein＠gmail.com Feb. 11, 2021

Feb. 11, 2021

## Install Mailman 3 The idea is to install Mailman 3 in ad docker container. Also I want to install Postfix in a container. All the mail which will send and receive should handled in a docker container. The reason is, that on the server only applications in a docker environment working. There is no MTA installed. On the server are Discourse as forum, wikijs, portainer, watchtower, homepage, and the NGINX Proxy Manager installed. At next I need Mailman 3. I don't know how to install and run Postfix for Mailman in a docker environment. Here is my first try. I can visit the site lists.example.com, but I can not set the Admin password. I think the reason is, that the MTA not working. I have a gitlab repo. If you like please look here: https://gitlab.com/joklein/mailman ### Configure the docker-compose.yml file ```yml version: '2' services: postfix: image: mailu/postfix restart: unless-stopped container_name: postfix volumes: - /opt/mailman/postfix:/etc/postfix/main.cf.d - /opt/mailman/core:/opt/mailman ports: - "25:25" networks: mailman: ipv4_address: 172.19.199.6 services: mailman-core: image: maxking/mailman-core:0.3 restart: unless-stopped stop_grace_period: 30s container_name: mailman-core hostname: mailman-core volumes: - /opt/mailman/core:/opt/mailman links: - database:database depends_on: - database environment: - DATABASE_URL=postgres://mailman:mailmanpass@database/mailmandb - DATABASE_TYPE=postgres - DATABASE_CLASS=mailman.database.postgresql.PostgreSQLDatabase - SMTP_HOST=172.19.199.1 - HYPERKITTY_API_KEY=ZawB3NGBUgbmQcMGhZ0kYIW0WRNw8P9osEudsGiFZWv networks: mailman: ipv4_address: 172.19.199.2 mailman-web: image: maxking/mailman-web:0.3 container_name: mailman-web restart: unless-stopped hostname: mailman-web ports: - "8000:8000" depends_on: - database links: - mailman-core:mailman-core - database:database volumes: - /opt/mailman/web:/opt/mailman-web-data environment: - DATABASE_TYPE=postgres - DATABASE_URL=postgres://mailman:mailmanpass@database/mailmandb - HYPERKITTY_API_KEY=ZawB3NGBUgbmQcMGhZ0kYIW0WRNw8P9osEudsGiFZWv - UWSGI_STATIC_MAP=/static=/opt/mailman-web-data/static - SERVE_FROM_DOMAIN=lists.example.com - MAILMAN_ADMIN_USER=admin - MAILMAN_ADMIN_EMAIL=lists(a)example.com - SECRET_KEY=mailmangeheim networks: mailman: ipv4_address: 172.19.199.3 database: image: postgres:9.6-alpine restart: unless-stopped environment: POSTGRES_DB: mailmandb POSTGRES_USER: mailman POSTGRES_PASSWORD: mailmanpass volumes: - /opt/mailman/database:/var/lib/postgresql/data networks: mailman: ipv4_address: 172.19.199.4 networks: mailman: driver: bridge ipam: driver: default config: - subnet: 172.19.199.0/24 ``` #### Build the API Key für Hyperkitty and SECRET_KEY You can build a key with `pwgen -s 128` #### Make some directorys ```sh mkdir -p /opt/mailman/core mkdir -p /opt/mailman/web mkdir -p /opt/mailman/mailman-web-data/static ``` #### Make a file in /opt/mailman/web/settings_local.py ```sh EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' EMAIL_HOST = '172.19.199.1' EMAIL_PORT = 25 USE_SSL = False DEFAULT_FROM_EMAIL = "<E-MAIL>" SERVER_EMAIL = "<E-MAIL>" ``` Change the `<E-MAIL>` with your server address. For example `mailman(a)lists.example.com` So that Postfix also sends your e-mails, you create the file `/opt/mailman/core/mailman-extra.cfg` with the following content: ```sh [mta] incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: 172.19.199.2 lmtp_port: 8024 smtp_host: 172.19.199.1 smtp_port: 25 configuration: /etc/postfix-mailman.cfg ``` Now you are ready to start your container: ```sh sudo su - cd /root/mailman-docker docker-compose up -d ``` #### Check the mailman images ```sh docker ps -a CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES f6990a2f808f maxking/mailman-web:0.3 "docker-entrypoint.s…" 55 seconds ago Up 52 seconds 8000/tcp, 8080/tcp mailman-web a7fa6334b2b8 maxking/mailman-core:0.3 "docker-entrypoint.s…" 58 seconds ago Up 54 seconds 8001/tcp, 8024/tcp mailman-core e8812dc42663 postgres:9.6-alpine "docker-entrypoint.s…" About a minute ago Up 57 seconds 5432/tcp docker-mailman_database_1 ``` #### Check the conection ```sh curl http://172.19.199.3:8000/postorius/lists/ ```

2 2