May 2023 - Mailman-users - lists.mailman3.org

Amazon SES, Message-ID, and mailman
by Sam Darwin May 5, 2023

May 5, 2023

Hi, We are running a mailman 2 mailing list, soon to upgrade to mailman 3. We recently switch the mail gateway from mailgun to Amazon SES. There's a new problem that the mailman 2 archives are not able to group threads together the way they were before. Moreover, end users have their own mail clients that display the list messages, and they are complaining about issues in their local mail clients. It seems to be related to the mail header fields Message-ID: , References: , and In-Reply-To: . Amazon SES rewrites the Message-ID. Therefore, it won't match the original Message-ID, and so the second reply email won't matched with the first email in a web archive display. Additionally, email replies are often sent both to the list and to individual participants, and so it's important that both of these copies have the identical message id. Has anyone else used Amazon SES as a mail gateway, and did you have success with it? Does this interpretation of the problem seem reasonable? Would it make sense to briefly discuss "Amazon SES" in an FAQ section of the mailman documentation? Thanks, Sam

2 2

Change delivery_status of a member by using the rest api
by Michael Schaarschmidt May 4, 2023

May 4, 2023

Hello, I would like to set or change the delivery_status of a list member by using the rest api. The curl request looks like curl \ -X PATCH \ -H "Content-Type: application/json“ \ -H "Accept: application/json“ \ -u restadmin:secret_password \ -d "@./foo_patch.json“ \ "http://127.0.0.1:8001/3.1/members/ebcdd09bb8d84758a135c3449023701e“ With the json-file: { „delivery_status“: „by_user“ } I get an error message: {"title": "400 Bad Request", "description": "Unexpected parameters: delivery_status“} Is there a way to change the attribute `delivery_status` of an existing member by using the rest api? Cheers, Michael Schaarschmidt ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Replaced multipart/alternative part with first alternative.

2 1

Postorius install - missing python modules
by Marco F May 3, 2023

May 3, 2023

Hello, On AlmaLinux 8.7, after Configuring Mailman and Setting up my database (postgres), and hooking up my mailserver (Exim), the instructions proceed to Set up Postorius: https://docs.mailman3.org/projects/postorius/en/latest/setup.html I've tried `pip install postorius`, as well as the latest version, cloning and `pip install -e .`. I've tried with multiple python versions, all with the results: ModuleNotFoundError. Here's highlights of one example: ``` dnf update -y dnf upgrade -y dnf install -y python39 alternatives --config python3 » python3 -V Python 3.9.13 pip3 install postorius git clone https://gitlab.com/mailman/postorius.git cd postorius pip3 install -e . cd example_project ~/postorius/example_project (master)» » python3 manage.py migrate ... ModuleNotFoundError: No module named 'debug_toolbar' » pip3 install debug_toolbar ERROR: Could not find a version that satisfies the requirement debug_toolbar (from versions: none) ERROR: No matching distribution found for debug_toolbar » pip3 install django-debug-toolbar ... » python3 manage.py migrate ... ModuleNotFoundError: No module named 'requests_panel' » pip3 install requests_panel ... » python3 manage.py migrate ... ModuleNotFoundError: No module named 'requests_panel' » pip3 install django-requests-panel ... » python3 manage.py migrate ... ModuleNotFoundError: No module named 'requests_panel.panel' # I tried a bunch of different modules, none resolved the error, finally tried this & it did: » cd $( dirname $( locate requests_panel/panels.py ) ) && cp -pv panels.py panel.py » python3 manage.py migrate ... ModuleNotFoundError: No module named 'requests_wrapper' » pip3 install requests_wrapper ... » python3 manage.py migrate ... ImportError: cannot import name '_total_seconds' from 'requests_wrapper' (/usr/local/lib/python3.9/site-packages/requests_wrapper/__init__.py) ```

2 1

looking for more detailed traceback for shunted message
by bob B May 3, 2023

May 3, 2023

Had a message get shunted in /opt/mailman/core/var/queue/shunt/. *** but that is the location in the docker environment, which we are running. The mailman log shows: Apr 26 13:09:56 2023 (31) ACCEPT: 2e0e82a5-0924-1777-bed8-34862417fe7e@[Redacted] Apr 26 13:09:56 2023 (35) Uncaught runner exception: 'ascii' codec can't encode characters in position 1198-1200: ordinal not in range(128) Apr 26 13:09:56 2023 (35) Traceback (most recent call last): Apr 26 13:09:56 2023 (35) SHUNTING: 1682514596.7976818+6067e5ddeb70e4aad97977071b5ed00c41999057 Apr 26 13:10:14 2023 (31) ACCEPT: 367fa8b7-97ac-58b3-fb99-458dbb951f5d@[Redacted] Apr 26 13:10:14 2023 (31) ACCEPT: 367fa8b7-97ac-58b3-fb99-458dbb951f5d@[Redacted] Apr 26 13:10:16 2023 (35) Uncaught runner exception: 'ascii' codec can't encode characters in position 1198-1200: ordinal not in range(128) Apr 26 13:10:16 2023 (35) Traceback (most recent call last): Apr 26 13:10:16 2023 (35) SHUNTING: 1682514616.5346222+7292ba8b651bc1bd76a9098733a39090e092add2 Is there anyway to get more info, Is there a more detailed traceback somewhere?

5 10