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

rDNS issue? Helo name contains an IP address (HELO was [127.0.0.1]) and not is valid
by Kyriakos Terzopoulos Oct. 25, 2023

Oct. 25, 2023

Hi all, I'm on the latest mailman installation in a HestiaCP server. The past few days I have been investigating some spam issues and by using dkimvalidator.com I found the following: 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature -1.0 MAILING_LIST_MULTI Multiple indicators imply a widely-seen list manager* 3.2 HELO_DYNAMIC_IPADDR Relay HELO'd using suspicious hostname (IP addr 1)* Note the last line on the above debug information which raises the spam score of the email. Some research showed me that I needed a rDNS entry in my server. I'm on a Hetzner cloud VM so I used the Hetzner console to change the rDNS entry from: static.XXX.XXX.XXX.XXX.clients.your-server.de to my initial server hostname for example: *hestia.myserver.com <http://hestia.myserver.com>* However, after some propagation, I found today that even though I can send email to any normal address created in the server's control panel, mailing list emails do not get sent. I see the following in the logs: Mailman SMTP log: Oct 24 14:17:47 2023 (3759611) <169814622178.3759638.4589434779084932533@localhost> *response exception: (550, b'Helo name contains an IP address (HELO was [127.0.0.1]) and not is valid'*, 'testlist-bounces+myusername=myproject.eu(a)myproject.eu') Oct 24 14:17:47 2023 (3759611) <169814622178.3759638.4589434779084932533@localhost> smtp to testlist(a)myproject.eu for 1 recips, completed in 45.07745146751404 seconds Oct 24 14:17:47 2023 (3759611) <169814622178.3759638.4589434779084932533@localhost> post to testlist(a)myproject.eu from testlist-confirm+07d3315fa11a75588857fc93d1832ba74fb09fdd(a)myproject.eu, 1633 bytes, 1 failures Oct 24 14:17:47 2023 (3759611) <169814622178.3759638.4589434779084932533@localhost> delivery to myusername(a)myproject.eu failed with code 550, b*'Helo name contains an IP address (HELO was [127.0.0.1]) and not is valid'* Exim4 log: 2023-10-24 14:17:47 H=([127.0.0.1]) [XXX.XXX.XXX.XXX] rejected MAIL <testlist-bounces+myusername=myproject.eu(a)myproject.eu>: *Helo name contains an IP address (HELO was [127.0.0.1]) and not is valid* The weird thing is that when I do a mailman-web sendtestemail this email is sent successfully. Also please note that before the rDNS change I did not have an issue with mail sending. Last but not least, after some search I set in Exim4 the following: PRIMARY_HOST_NAME = *hestia.myserver.com <http://hestia.myserver.com>* Any help would be greatly appreciated. *Kyriakos Terzopoulos *Web developer / e-learning expert *Tel:*+30 211 213 9858 *Mobile:* +30 694 526 4512 * E-mail: *kyriakos.terzopoulos(a)gmail.com * Skype:* kyriakos.terzopoulos Find me on Facebook <http://www.facebook.com/cirrus3d> Follow me on Twitter <http://twitter.com/#%21/cirrus3d>

2 4

Without being logged in, at least one mailing list - flagged as no-show - is listed in https://mydomain/hyperkitty/
by Wikinaut Oct. 25, 2023

Oct. 25, 2023

The list is not yet used (i.e. "inactive"), but clearly flagged as " Show list on index page = no" I regard this as a bug.

1 1

More Mailman releases!
by Abhilash Raj Oct. 24, 2023

Oct. 24, 2023

Hello Everyone, I am pleased to announce several new releases for GNU Mailman project. Thanks to all the contributors for making these releases possible! 1. Postorius 1.3.10 [1] 2. Hyperkitty 1.3.8 [2] 3. Django-mailman3 1.3.10 [3] 4. Mailman-web 0.0.7 [4] All the releases are published to PyPI and you can find links to all the PyPI projects: https://docs.mailman3.org/en/latest/ A full list of change logs are available below: [1]: https://docs.mailman3.org/projects/postorius/en/latest/news.html#news-1-3-10 [2]: https://docs.mailman3.org/projects/hyperkitty/en/latest/news.html#news-1-3-8 [3]: https://gitlab.com/mailman/django-mailman3/-/blob/master/README.rst [4]: https://gitlab.com/mailman/mailman-web/-/blob/master/README.rst Do note that for Postorius, I released 1.3.9, but I forgot to update dependency metadata to require `django-mailman3>=1.3.10` (which is required for the new bootstrap 5 upgrade across packages) and so I also released Postorius 1.3.10 just after. Installation documentation is available at https://docs.mailman3.org/en/latest/install/install.html and if you are upgrading an existing virtualenv install you can refer https://docs.mailman3.org/en/latest/upgrade-3.2.html If you find any issues, you can report them at the respective bug tracker for the projects. The links to issue trackers are available at https://docs.mailman3.org/en/latest/. Finally, similar to Mailman Core, note that PyPI doesn't accept signatures anymore so each packages' release page now has the tarball uploaded to them along with the signature: Django-mailman3: https://gitlab.com/mailman/django-mailman3/-/releases/v1.3.10 Hyperkitty: https://gitlab.com/mailman/hyperkitty/-/releases/v1.3.8 Postorius: https://gitlab.com/mailman/postorius/-/releases/v1.3.10 Mailman-web: https://gitlab.com/mailman/mailman-web/-/releases/0.0.7 -- thanks, Abhilash Raj (maxking)

9 17

120 gmail users removed from lists !
by elemac＠free.fr Oct. 24, 2023

Oct. 24, 2023

Hello, on 15th October, 120 users with gmail address where suddenly removed from lists in mailman3, something changed in google ?

8 11

Gmail bounces as a result to high send rate
by Mohsen Masoudfar Oct. 24, 2023

Oct. 24, 2023

I managed to receive the bounced emails to my mailbox and I can now see the stated reason for th eissue, the bulk of the emails are marked as "expired" due to the following response: "smtp; Message expired: unable to deliver in 840 minutes.< Our system has detected an unusual rate of unsolicited mail. To protect our users from spam, mail has been temporarily rate limited. Please visit https://support.google.com/mail/?p=UnsolicitedRateLimitError to review our Bulk Email Senders Guidelines." The issue is exclusive to Gmail, no other email provider responded with a comparable message. I followed their recommendation, but I am not sure how to reduce the rate on Postfix side. Can I do it per list? or once per server? Thanks.

2 1

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