Mailman-users

Download

mailman-users@mailman3.org

May 2023

39 participants
72 discussions

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