- Mailman-users - lists.mailman3.org

Internal Server Error: /mailman/accounts/fedora/login/
by Kilian Kilger Oct. 24, 2023

Oct. 24, 2023

Hi mailing list, I own a mailman box. I regularily (many times a day) get mail with an internal server error. I am using Debian and the included mailman3-full package. I guess someone tries to hack my instance. But I don't understand why this leads to the internal server error. I am also wondering why the request URL is /mailman/accounts/fedora/login, as I am using Debian (understandable if the request happens via an outside trigger). I have no clue about the internal workings of mailman though. I use Debian 11 bullseye and thus version 3.3.3. I can trigger the internal server error by myself by visiting the request URL. Despite these emails the instance seems to work fine. Best regards, Kilian. Internal Server Error: /mailman/accounts/fedora/login/ TypeError at /accounts/fedora/login/ _openid_consumer() missing 2 required positional arguments: 'provider' and 'endpoint' Request Method: GET Request URL: <URL>/mailman/accounts/fedora/login/?process=login&next=/mailman/accounts/password/reset/ Django Version: 2.2.24 Python Executable: /usr/bin/uwsgi-core Python Version: 3.9.2 Python Path: ['.', '', '/usr/lib/python39.zip', '/usr/lib/python3.9', '/usr/lib/python3.9/lib-dynload', '/usr/local/lib/python3.9/dist-packages', '/usr/lib/python3/dist-packages', '/usr/lib/python3.9/dist-packages'] Server time: Fr, 17 Sep 2021 06:12:57 +0000 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') Traceback: 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/lib/python3/dist-packages/django/views/generic/base.py" in view 71. return self.dispatch(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/django/views/generic/base.py" in dispatch 97. return handler(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/django_mailman3/lib/auth/fedora/views.py" in get 56. return self.post(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/django_mailman3/lib/auth/fedora/views.py" in post 67. client = _openid_consumer(request) Exception Type: TypeError at /accounts/fedora/login/ Exception Value: _openid_consumer() missing 2 required positional arguments: 'provider' and 'endpoint' Request information: USER: AnonymousUser

3 2

General question mailman3: message sender acceptance "always"
by Wikinaut Oct. 23, 2023

Oct. 23, 2023

I received one mail from a sender who's not a member for moderation (=ok). Mailman2 had the moderation option "allow this sender to sender further mails" (I call this: to add this sender to the additional "white list" of white-listed addresses.) I could not find such an option (in the moderation dialog) in Mailman3 (only "accept" or "reject" and "discard", but "accept and add to white-list = accept always"). Is it a bug or feature?

2 4

pip install -U mysqlclient
by Odhiambo Washington Oct. 23, 2023

Oct. 23, 2023

Hello everyone, After successfully updating my MM3 venv install, I thought I could also keep everything else up to date. One app refuses - mysqlclient. All the rest did update. PS: I have a full backup of the venv so no worries there :) <CUT> (venv) [mailman@gw /opt/mailman/mm]$ pip install -U mysqlclient Requirement already satisfied: mysqlclient in ./venv/lib/python3.11/site-packages (2.1.1) Collecting mysqlclient Using cached mysqlclient-2.2.0.tar.gz (89 kB) Installing build dependencies ... done Getting requirements to build wheel ... error error: subprocess-exited-with-error × Getting requirements to build wheel did not run successfully. │ exit code: 1 ╰─> [25 lines of output] Trying pkg-config --exists mysqlclient Command 'pkg-config --exists mysqlclient' returned non-zero exit status 1. Trying pkg-config --exists mariadb Command 'pkg-config --exists mariadb' returned non-zero exit status 1. Traceback (most recent call last): File "/opt/mailman/mm/venv/lib/python3.11/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 353, in <module> main() File "/opt/mailman/mm/venv/lib/python3.11/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 335, in main json_out['return_val'] = hook(**hook_input['kwargs']) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/mm/venv/lib/python3.11/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 118, in get_requires_for_build_wheel return hook(config_settings) ^^^^^^^^^^^^^^^^^^^^^ File "/tmp/pip-build-env-usp5tphe/overlay/lib/python3.11/site-packages/setuptools/build_meta.py", line 355, in get_requires_for_build_wheel return self._get_build_requires(config_settings, requirements=['wheel']) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/tmp/pip-build-env-usp5tphe/overlay/lib/python3.11/site-packages/setuptools/build_meta.py", line 325, in _get_build_requires self.run_setup() File "/tmp/pip-build-env-usp5tphe/overlay/lib/python3.11/site-packages/setuptools/build_meta.py", line 341, in run_setup exec(code, locals()) File "<string>", line 154, in <module> File "<string>", line 48, in get_config_posix File "<string>", line 27, in find_package_name Exception: Can not find valid pkg-config name. Specify MYSQLCLIENT_CFLAGS and MYSQLCLIENT_LDFLAGS env vars manually [end of output] note: This error originates from a subprocess, and is likely not a problem with pip. error: subprocess-exited-with-error × Getting requirements to build wheel did not run successfully. │ exit code: 1 ╰─> See above for output. note: This error originates from a subprocess, and is likely not a problem with pip. </CUT> -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

3 4

no access to Postorius web pages after upgrade
by David Newman Oct. 22, 2023

Oct. 22, 2023

Upgrading to MM3 3.39, Postorius 1.3.10, Hyperkitty, 1.3.8, Django-mailman3 1.3.11, and Mailman-web 0.0.8 in a venv all seemed to go OK. Mailman3 lists work as expected, and admins can log in via Django. However, any attempt to reach lists, domains, users, etc. now returns a 404 Not Found error. All the Postorius stuff worked as expected before the upgrade. In the nginx server logs, any Hyperkitty and Postorius URLs are now appended to /opt/www/roundcubemail, which is this web server's root directory but not the root for Mailman3 (I run Roundcubemail and MM3 on the same server; don't judge me :-). Here is the nginx error, with obfuscation of client and server info: 2023/10/22 10:43:24 [error] 2264140#2264140: *135 "/opt/www/roundcubemail/postorius/domains/index.php" is not found (2: No such file or directory), client: 1.2.3.4, server: lists.example.com, request: "GET /postorius/domains/ HTTP/2.0", host: "lists.example.com", referrer: "https://lists.example.com/mailman3/listinfo" And here are the relevant bits of the Nginx config. Again, this worked before the upgrade. server { listen 443 ssl http2; server_name lists.example.com; root /opt/www/roundcubemail; # begin mailman3 stuff location /static/ { alias /opt/mailman/web/static/; } location /mailman3/ { proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } location /archives/ { proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } location /accounts/ { proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } location /admin/ { proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } location /mailman/ { proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } location /user-profile/ { proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } # end mailman3 stuff } Also, I'm not sure if it's relevant but after upgrading, the migrate command throws a warning like this: (venv) mailman@mail10:~$ mailman-web migrate System check identified some issues: WARNINGS: account.EmailAddress: (models.W036) MariaDB does not support unique constraints with conditions. HINT: A constraint won't be created. Silence this warning if you don't care about it. account.EmailAddress: (models.W043) MariaDB does not support indexes on expressions. HINT: An index won't be created. Silence this warning if you don't care about it. Operations to perform: Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, postorius, sessions, sites, socialaccount Running migrations: No migrations to apply. Thanks in advance for clues on getting all Postorius/Django links working again. dn

2 3

[migration] to a another server - one year database apparently lacks fields for newer mailman3/django suite
by Wikinaut Oct. 22, 2023

Oct. 22, 2023

As suggested by @Mark last week, I exported my databases mailman3, mailman2web of what was mailman 3.3.0 (or so) and imported these on my new working system. Apparently, a database migration step is needed to run the new mailman3 with some older databases: because when I want to login to view my mailing lists, I got "An error occurred while processing your request." in the web. Log files and error mail messages say inter alia: Internal Server Error: /accounts/login/ OperationalError at /accounts/login/ (1054, "Unknown column 'socialaccount_socialapp.provider_id' in 'field list'" and Internal Server Error: /archives/ OperationalError at /archives/ (1054, "Unknown column 'hyperkitty_mailinglist.archive_rendering_mode' in 'field list'") Please can you assist: How can I add the missing tables, is there an update script (running "python migrate.py" was not fixing this).

2 2

New messages are not archived - may be a path issue
by Wikinaut Oct. 21, 2023

Oct. 21, 2023

(I read thoroughly https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… "New messages not being archived", but could not find what's wrong on my machine.) This is what I found in /var/log/mailman3/mailman.log : HyperKitty failure on https://mail.opteryx.org/mailman3/archives/api/mailman/archive: This page either doesn't exist, or it moved somewhere else. I have double checked all settings in the /etc/mailman3/ configuration files and are not able to get message archived. There is not REST error message any more, but perhaps a problem with the paths. I have no idea any more where to fix this.

3 3

(venv) mailman-web migrate (as explained) fails with "django.core.exceptions.ImproperlyConfigured: allauth.account.middleware.AccountMiddleware must be added to settings.MIDDLEWARE"
by Wikinaut Oct. 21, 2023

Oct. 21, 2023

I followed all single steps until this: https://docs.list.org/en/latest/install/virtualenv.html#run-database-migrat… (I will improve the documentation with the missing parts later today), Now I got this and got stucked and need your help: django.core.exceptions.ImproperlyConfigured: allauth.account.middleware.AccountMiddleware must be added to settings.MIDDLEWARE full stack: (venv) mailman@mail:/run$ mailman-web migrate Traceback (most recent call last): File "/opt/mailman/venv/bin/mailman-web", line 8, in <module> sys.exit(main()) ^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/mailman_web/manage.py", line 37, in main execute_from_command_line(sys.argv) File "/opt/mailman/venv/lib/python3.11/site-packages/django/core/management/__init__.py", line 446, in execute_from_command_line utility.execute() File "/opt/mailman/venv/lib/python3.11/site-packages/django/core/management/__init__.py", line 420, in execute django.setup() File "/opt/mailman/venv/lib/python3.11/site-packages/django/__init__.py", line 24, in setup apps.populate(settings.INSTALLED_APPS) File "/opt/mailman/venv/lib/python3.11/site-packages/django/apps/registry.py", line 124, in populate app_config.ready() File "/opt/mailman/venv/lib/python3.11/site-packages/allauth/account/apps.py", line 15, in ready raise ImproperlyConfigured( django.core.exceptions.ImproperlyConfigured: allauth.account.middleware.AccountMiddleware must be added to settings.MIDDLEWARE

6 28

[Bug] Archiver: when deleting an archive, the control flow is lost (return-to should go to https://example.com/archives/ but does not)
by Wikinaut Oct. 21, 2023

Oct. 21, 2023

How to reproduce: When deleting an archive, the confirmation page for the requested delete action is (correct) https://example.com/archives/list/test@example.com/delete/ When you now click the button DELETE, then the web control flow ist lost. BUG Instead of https://example.com/archives/ the https://example.com is shown, which appears to be a bug. REMARK: The archive-to-be-deleted was indeed deleted. This behaviour was observed with both installations on a fresh server: - debian12 install (package mailman3-full) ; and - venv install (recommended on your page)

2 1

Message of migrated list showing "unsubscribe@%(host_name)s" in footer
by alex＠presland.net Oct. 21, 2023

Oct. 21, 2023

Apologies if I've not found a previous post for this; I did look before starting a new thread. We migrated a number of mailman lists last weekend and I spotted this evening that an email from the list contained a footer along the lines of the following (all bits in CAPITALS were successfully representing the list. ===== LISTNAME mailing-list -- LISTNAME@DOMAIN To unsubscribe, email LISTNAME-unsubscribe@%(host_name)s ===== 1) I don't know why %(host_name)s hasn't been automagically substituted 2) I can't find anywhere to change this footer in the Mailman3 Postorius interface

2 3

After importing my old databases, the mail local_recipient map is suddenly not working any more
by Wikinaut Oct. 20, 2023

Oct. 20, 2023

After importing old databases everythimng looks fine now. But the mail local_recipient maps are not working (/etc/postfix/main.cf looks fine, as before, and postfix was restarted). Mails to test(a)example.org rejected with Error 550 Recipient address rejected: User unknown in local recipient table /* as in your installation guide */ transport_maps = hash:/var/lib/mailman3/data/postfix_lmtp local_recipient_maps = $alias_maps hash:/var/lib/mailman3/data/postfix_lmtp relay_domains = hash:/var/lib/mailman3/data/postfix_domains The files appears to be present: /var/lib/mailman3/data# dir 4 -rw-rw---- 1 mailman mailman 339 Oct 20 21:13 postfix_domains 8 -rw-r----- 1 mailman mailman 12288 Oct 20 21:13 postfix_domains.db 4 -rw-rw---- 1 mailman mailman 2714 Oct 20 21:13 postfix_lmtp 12 -rw-r----- 1 mailman mailman 12288 Oct 20 21:13 postfix_lmtp.db What else is needed to get the list-addresses working and not rejected? It worked before the import.

1 3