- Mailman-users - lists.mailman3.org

Editing the "example.org" site
by Stephen J. Turnbull 03 Jan '24

03 Jan '24

Hi all, I don't know how many people will need this, but I just realized that you can edit Django's SITE 1 and (probably, 100% untested but I'm going on the clock so want to get this done quick :-) use that. When you add your first domain, there's a link in that page (not a button, a link!) to edit the domain list. Then you can click on the link to "example.org" in the list, and edit both display name (which I assumed) and the domain name. Maybe I'm just slow, but I've been adding SITE 2 = "Whatever site <whatever.tld>" the whole time. :-) But then you have to edit the SITE = 1 statement in settings.py (which I often forget and hilarity ensues). Of course adding a web site and editing settings.py (which you have to do anyway for other variables) works too, but this seems cleaner to me. Steve

2 3

Can't edit lists anymore: "Something went wrong HTTP Error 404"
by Nils 30 Dec '23

30 Dec '23

When I try to edit any list at "postorius/lists/LISTNAME.SUBDOMAIN.DOMAIN.TLD/", I get this error. The lists are displayed correctly at "postorius/lists/". Selecting any of those lists leads to that error. First step of creating a new list is possible but I get the same error right after the creation of the new list. These lines in the mailman.log seem suspicious: Dec 29 11:59:30 2023 (6255) 127.0.0.1 - - "GET /3.1/lists/testliste.lists.DOMAIN.TLD/member/USERNAME%40DOMAIN.TLD HTTP/1.1" *404* 26 Dec 29 11:59:30 2023 (6255) 127.0.0.1 - - "GET /3.1/users/fa17aa7aa1e946b6a72706b48ddbc14b/preferred_address HTTP/1.1" *404* 26 Dec 29 11:59:30 2023 (6255) 127.0.0.1 - - "POST /3.1/users/fa17aa7aa1e946b6a72706b48ddbc14b/preferred_address HTTP/1.1" *404* 26 Mailman Core Version GNU Mailman 3.2.2 (La Villa Strangiato) Mailman Core API Version 3.1 Mailman Core Python Version 3.10.12 (main, Nov 20 2023, 15:14:05) [GCC 11.4.0] Postorius Version 1.3.5 Here are the full logs of this event: mailman3/web/mailman-web.log ERROR 2023-12-29 11:59:30,571 2416033 postorius Un-handled exception: HTTP Error 404: {"title": "404 Not Found"} Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 181, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python3/dist-packages/django/views/generic/base.py", line 70, in view return self.dispatch(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/postorius/views/generic.py", line 74, in dispatch return super(MailingListView, self).dispatch(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/django/views/generic/base.py", line 98, in dispatch return handler(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/postorius/views/list.py", line 301, in get primary_email = set_preferred(request.user, mm_user) File "/usr/lib/python3/dist-packages/postorius/utils.py", line 77, in set_preferred mm_user.preferred_address = primary_email.email File "/usr/lib/python3/dist-packages/mailmanclient/restobjects/user.py", line 57, in __setattr__ super(User, self).__setattr__(name, value) File "/usr/lib/python3/dist-packages/mailmanclient/restbase/base.py", line 131, in __setattr__ return super(RESTObject, self).__setattr__(name, value) File "/usr/lib/python3/dist-packages/mailmanclient/restobjects/user.py", line 145, in preferred_address response, content = self._connection.call(url, {'email': email}) File "/usr/lib/python3/dist-packages/mailmanclient/restbase/connection.py", line 160, in call raise HTTPError(params.get('url'), response.status_code, urllib.error.HTTPError: HTTP Error 404: {"title": "404 Not Found"} WARNING 2023-12-29 11:59:30,580 2416033 django.request Not Found: /postorius/lists/testliste.lists.DOMAIN.TLD/ WARNING 2023-12-29 11:59:30,580 2416033 django.request Not Found: /postorius/lists/testliste.lists.DOMAIN.TLD/ [pid: 2416033|app: 0|req: 9/9] 2003:ca:bf1d:b000:efc2:8dfa:6fd:715f () {72 vars in 1618 bytes} [Fri Dec 29 11:59:30 2023] GET /postorius/lists/testliste.lists.DOMAIN.TLD/ => generated 6285 bytes in 466 msecs (HTTP/1.1 404) 7 headers in 227 bytes (1 switches on core 0) mailman3/mailman.log Dec 29 11:59:30 2023 (6255) 127.0.0.1 - - "GET /3.1/lists/testliste.lists.DOMAIN.TLD HTTP/1.1" 200 384 Dec 29 11:59:30 2023 (6255) 127.0.0.1 - - "GET /3.1/lists/testliste.lists.DOMAIN.TLD/roster/owner HTTP/1.1" 200 640 Dec 29 11:59:30 2023 (6255) 127.0.0.1 - - "GET /3.1/lists/testliste.lists.DOMAIN.TLD/roster/moderator HTTP/1.1" 200 90 Dec 29 11:59:30 2023 (6255) 127.0.0.1 - - "GET /3.1/lists/testliste(a)lists.DOMAIN.TLD/config HTTP/1.1" 200 2132 Dec 29 11:59:30 2023 (6255) 127.0.0.1 - - "GET /3.1/lists/testliste.lists.DOMAIN.TLD/archivers HTTP/1.1" 200 61 Dec 29 11:59:30 2023 (6255) 127.0.0.1 - - "GET /3.1/lists/testliste(a)lists.DOMAIN.TLD/requests?request_type=subscription HTTP/1.1" 200 90 Dec 29 11:59:30 2023 (6255) 127.0.0.1 - - "GET /3.1/lists/testliste.lists.DOMAIN.TLD/member/USERNAME%40DOMAIN.TLD HTTP/1.1" 404 26 Dec 29 11:59:30 2023 (6255) 127.0.0.1 - - "GET /3.1/users/fa17aa7aa1e946b6a72706b48ddbc14b HTTP/1.1" 200 286 Dec 29 11:59:30 2023 (6255) 127.0.0.1 - - "GET /3.1/users/fa17aa7aa1e946b6a72706b48ddbc14b/preferred_address HTTP/1.1" 404 26 Dec 29 11:59:30 2023 (6255) 127.0.0.1 - - "GET /3.1/addresses/USERNAME(a)DOMAIN.TLD HTTP/1.1" 200 369 Dec 29 11:59:30 2023 (6255) 127.0.0.1 - - "POST /3.1/users/fa17aa7aa1e946b6a72706b48ddbc14b/preferred_address HTTP/1.1" 404 26 Kind regards

2 3

"From address" for list moderation notification
by ronn.ramirez＠pge.com 30 Dec '23

30 Dec '23

Hi Mailman Group, I noticed that the from address for list moderation notifications are coming from a certain user address. May you please help me figure out where to change this? In this example, I would like to change the From address "listadmin(a)domain.com" ================================================================ -----Original Message----- From: Admin <listadmin(a)domain.com> Sent: Thursday, December 28, 2023 12:00 AM To: dummy-list <dummy-list(a)domainx.com> Subject: The dummy-list(a)domainx.com list has 2 moderation requests waiting. The dummy-list(a)domainx.com list has 2 moderation requests waiting. Held Messages: Sender: user1(a)domain.com Subject: You missed a call | Transcription Available . Reason: The message is not from a list member Sender: user2(a)domain.com Subject: Update/Access Required Notice on Friday, September 29, 2023 Reason: The message is not from a list member Please attend to this at your earliest convenience. =================================================================

2 3

Again, after systemupgrade the log file in /var/log/mailman was owned by list:list instead of mailman:mailman and starting failed for this reason [support request]
by Wikinaut 28 Dec '23

28 Dec '23

I made for a repeated time (after system update and/or system reboot) the experience,that my mailman3 installation fails to start because of permission error to write the log file. For some unknown reason, an empty file /var/og/mailman/mailman.log was apparently owned by list:list. I deleted that file and mailman3 core could now be started. The start problem i solved. I asked myself and you, how can this happen for many times? Has anyone an idea what the reason could be? There is still a user list from a previous mailman3 installation, where I assigned the (former user for mailman2), but I suppose the problem is a different problem than a simple user definition. The other log files are always correctly assigned to mailman:mailman <pre> -rw-rw---- 1 mailman mailman 7487 Dec 22 18:21 bounce.log 0 -rw-rw---- 1 mailman mailman 0 Oct 8 22:46 debug.log 4 -rw-rw---- 1 mailman mailman 1909 Dec 24 09:10 mailman.log 57448 -rw-rw---- 1 mailman mailman 58820418 Dec 24 09:00 mailman.log.1 108 -rw-rw---- 1 mailman mailman 108407 Oct 24 12:18 mailman.log.2.gz 0 -rw-rw---- 1 mailman mailman 0 Oct 8 22:46 plugins.log 232 -rw-rw---- 1 mailman mailman 229585 Dec 24 09:10 smtp.log 4 drwxr-xr-x 2 mailman mailman 4096 Oct 20 00:00 <font color="#729FCF"><b>web</b></font> </pre>

3 10

subscribing to a list from a WordPress site
by Johannes Rohr 25 Dec '23

25 Dec '23

Dear all, is there a wordpress plugin/widget allowing visitors to subscribe to a mailman3 hosted mailing list? Else, what is the most convenient way? Sure, I could just link to the maiman site, but since joining a list is as easy as sending mail to LISTNAME-join, there should be a simple way to impement this. What is the best practice? Cheers, Johannes

2 1

Function "Mass subscription" does not allow any more the format `"Givenname Familyname" <mailaddress>`
by Wikinaut 22 Dec '23

22 Dec '23

Wheras my older lists handled these format apparently correctly, I now cannot add any more "Givenname Familyname" <mailaddress> ; or Givenname Familyname <mailaddress> In any of these cases, only the part <mailaddress> is added. Is this strange behaviour know? What can be done to have the correct function back to working again?

2 1

django-allauth failures, but only for some users (independent of browser?)
by Jered Floyd 22 Dec '23

22 Dec '23

Django-allauth seems to just be a basket of woes, but I figured I'd toss this one out there to see if anyone has seen similar: I have Google and Facebook social logins configured. They work fine for me. They work fine for most people. Huzzah! For some people, even when they use different browsers/OSes/etc, attempting a social login generates an error. On the callback, they get "Server error" "An error occurred while processing your request." These errors are generated to me as the admin, and in the elided environment section SITE_ID is indeed 0, but I'm at a loss to imagine why this happens only sometimes! Any pointers for investigation? --Jered Internal Server Error: /accounts/google/login/callback/ ImproperlyConfigured at /accounts/google/login/callback/ You're using the Django "sites framework" without having set the SITE_ID setting. Create a site in your database and set the SITE_ID setting or pass a request to Site.objects.get_current() to fix this error. [...] Traceback (most recent call last): File "/opt/app-root/src/.local/lib/python3.9/site-packages/django/core/handlers/exception.py", line 56, in inner response = get_response(request) File "/opt/app-root/src/.local/lib/python3.9/site-packages/django/core/handlers/base.py", line 197, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/opt/app-root/src/.local/lib/python3.9/site-packages/allauth/socialaccount/providers/oauth2/views.py", line 84, in view return self.dispatch(request, *args, **kwargs) File "/opt/app-root/src/.local/lib/python3.9/site-packages/allauth/socialaccount/providers/oauth2/views.py", line 162, in dispatch return complete_social_login(request, login) File "/opt/app-root/src/.local/lib/python3.9/site-packages/allauth/socialaccount/helpers.py", line 197, in complete_social_login sociallogin.lookup() File "/opt/app-root/src/.local/lib/python3.9/site-packages/allauth/socialaccount/models.py", line 282, in lookup provider_id = self.account.get_provider().id File "/opt/app-root/src/.local/lib/python3.9/site-packages/allauth/socialaccount/models.py", line 141, in get_provider provider = self._provider = adapter.get_provider( File "/opt/app-root/src/.local/lib/python3.9/site-packages/allauth/socialaccount/adapter.py", line 204, in get_provider app = self.get_app(request, provider=provider) File "/opt/app-root/src/.local/lib/python3.9/site-packages/allauth/socialaccount/adapter.py", line 284, in get_app apps = self.list_apps(request, provider=provider, client_id=client_id) File "/opt/app-root/src/.local/lib/python3.9/site-packages/allauth/socialaccount/adapter.py", line 231, in list_apps db_apps = SocialApp.objects.on_site(request) File "/opt/app-root/src/.local/lib/python3.9/site-packages/allauth/socialaccount/models.py", line 27, in on_site site = get_current_site(request) File "/opt/app-root/src/.local/lib/python3.9/site-packages/django/contrib/sites/shortcuts.py", line 16, in get_current_site return Site.objects.get_current(request) File "/opt/app-root/src/.local/lib/python3.9/site-packages/django/contrib/sites/models.py", line 63, in get_current raise ImproperlyConfigured( Exception Type: ImproperlyConfigured at /accounts/google/login/callback/ Exception Value: You're using the Django "sites framework" without having set the SITE_ID setting. Create a site in your database and set the SITE_ID setting or pass a request to Site.objects.get_current() to fix this error. Raised during: allauth.socialaccount.providers.oauth2.views.view [... internal state elided ...]

2 14

mailman3-web generating huge amount of error logs
by Helio Loureiro 22 Dec '23

22 Dec '23

Hi, Now my finished installation is generating a lot of errors and filling up /var/log/syslog 1GB in a few hours. The errors are like this one: Dec 21 08:42:17 new-server mailman-web[981806]: --- Logging error --- Dec 21 08:42:17 new-server mailman-web[981806]: Traceback (most recent call last): Dec 21 08:42:17 new-server mailman-web[981806]: File "/local/mailman/venv/lib/python3.10/site-packages/django_q/cluster.py", line 356, in pusher Dec 21 08:42:17 new-server mailman-web[981806]: task = SignedPackage.loads(task[1]) Dec 21 08:42:17 new-server mailman-web[981806]: File "/local/mailman/venv/lib/python3.10/site-packages/django_q/signing.py", line 25, in loads Dec 21 08:42:17 new-server mailman-web[981806]: return signing.loads( Dec 21 08:42:17 new-server mailman-web[981806]: File "/local/mailman/venv/lib/python3.10/site-packages/django_q/core_signing.py", line 35, in loads Dec 21 08:42:17 new-server mailman-web[981806]: base64d = force_bytes(TimestampSigner(key, salt=salt).unsign(s, max_age=max_age)) Dec 21 08:42:17 new-server mailman-web[981806]: File "/local/mailman/venv/lib/python3.10/site-packages/django_q/core_signing.py", line 70, in unsign Dec 21 08:42:17 new-server mailman-web[981806]: result = super(TimestampSigner, self).unsign(value) Dec 21 08:42:17 new-server mailman-web[981806]: File "/local/mailman/venv/lib/python3.10/site-packages/django_q/core_signing.py", line 55, in unsign Dec 21 08:42:17 new-server mailman-web[981806]: raise BadSignature('Signature "%s" does not match' % sig) Dec 21 08:42:17 new-server mailman-web[981806]: django.core.signing.BadSignature: Signature "ofwl5GkP2_1nDnfM8-vAjAwl_Ss" does not match Dec 21 08:42:17 new-server mailman-web[981806]: During handling of the above exception, another exception occurred: Dec 21 08:42:17 new-server mailman-web[981806]: Traceback (most recent call last): Dec 21 08:42:17 new-server mailman-web[981806]: File "/usr/lib/python3.10/logging/__init__.py", line 1100, in emit Dec 21 08:42:17 new-server mailman-web[981806]: msg = self.format(record) Dec 21 08:42:17 new-server mailman-web[981806]: File "/usr/lib/python3.10/logging/__init__.py", line 943, in format Dec 21 08:42:17 new-server mailman-web[981806]: return fmt.format(record) Dec 21 08:42:17 new-server mailman-web[981806]: File "/usr/lib/python3.10/logging/__init__.py", line 678, in format Dec 21 08:42:17 new-server mailman-web[981806]: record.message = record.getMessage() Dec 21 08:42:17 new-server mailman-web[981806]: File "/usr/lib/python3.10/logging/__init__.py", line 368, in getMessage Dec 21 08:42:17 new-server mailman-web[981806]: msg = msg % self.args Dec 21 08:42:17 new-server mailman-web[981806]: TypeError: not all arguments converted during string formatting Dec 21 08:42:17 new-server mailman-web[981806]: Call stack: Dec 21 08:42:17 new-server mailman-web[981806]: File "/local/mailman/venv/bin/mailman-web", line 8, in <module> Dec 21 08:42:17 new-server mailman-web[981806]: sys.exit(main()) Dec 21 08:42:17 new-server mailman-web[981806]: File "/local/mailman/venv/lib/python3.10/site-packages/mailman_web/manage.py", line 90, in main Dec 21 08:42:17 new-server mailman-web[981806]: execute_from_command_line(sys.argv) Dec 21 08:42:17 new-server mailman-web[981806]: File "/local/mailman/venv/lib/python3.10/site-packages/django/core/management/__init__.py", line 446, in execute_from_command_line Dec 21 08:42:17 new-server mailman-web[981806]: utility.execute() Dec 21 08:42:17 new-server mailman-web[981806]: File "/local/mailman/venv/lib/python3.10/site-packages/django/core/management/__init__.py", line 440, in execute Dec 21 08:42:17 new-server mailman-web[981806]: self.fetch_command(subcommand).run_from_argv(self.argv) Dec 21 08:42:17 new-server mailman-web[981806]: File "/local/mailman/venv/lib/python3.10/site-packages/django/core/management/base.py", line 407, in run_from_argv Dec 21 08:42:17 new-server mailman-web[981806]: self.execute(*args, **cmd_options) Dec 21 08:42:17 new-server mailman-web[981806]: File "/local/mailman/venv/lib/python3.10/site-packages/django/core/management/base.py", line 453, in execute Dec 21 08:42:17 new-server mailman-web[981806]: output = self.handle(*args, **options) Dec 21 08:42:17 new-server mailman-web[981806]: File "/local/mailman/venv/lib/python3.10/site-packages/django_q/management/commands/qcluster.py", line 22, in handle Dec 21 08:42:17 new-server mailman-web[981806]: q.start() Dec 21 08:42:17 new-server mailman-web[981806]: File "/local/mailman/venv/lib/python3.10/site-packages/django_q/cluster.py", line 78, in start Dec 21 08:42:17 new-server mailman-web[981806]: self.sentinel.start() Dec 21 08:42:17 new-server mailman-web[981806]: File "/usr/lib/python3.10/multiprocessing/process.py", line 121, in start Dec 21 08:42:17 new-server mailman-web[981806]: self._popen = self._Popen(self) Dec 21 08:42:17 new-server mailman-web[981806]: File "/usr/lib/python3.10/multiprocessing/context.py", line 224, in _Popen Dec 21 08:42:17 new-server mailman-web[981806]: return _default_context.get_context().Process._Popen(process_obj) Dec 21 08:42:17 new-server mailman-web[981806]: File "/usr/lib/python3.10/multiprocessing/context.py", line 281, in _Popen Dec 21 08:42:17 new-server mailman-web[981806]: return Popen(process_obj) Dec 21 08:42:17 new-server mailman-web[981806]: File "/usr/lib/python3.10/multiprocessing/popen_fork.py", line 19, in __init__ Dec 21 08:42:17 new-server mailman-web[981806]: self._launch(process_obj) Dec 21 08:42:17 new-server mailman-web[981806]: File "/usr/lib/python3.10/multiprocessing/popen_fork.py", line 71, in _launch Dec 21 08:42:17 new-server mailman-web[981806]: code = process_obj._bootstrap(parent_sentinel=child_r) Dec 21 08:42:17 new-server mailman-web[981806]: File "/usr/lib/python3.10/multiprocessing/process.py", line 314, in _bootstrap Dec 21 08:42:17 new-server mailman-web[981806]: self.run() Dec 21 08:42:17 new-server mailman-web[981806]: File "/usr/lib/python3.10/multiprocessing/process.py", line 108, in run Dec 21 08:42:17 new-server mailman-web[981806]: self._target(*self._args, **self._kwargs) Dec 21 08:42:17 new-server mailman-web[981806]: File "/local/mailman/venv/lib/python3.10/site-packages/django_q/cluster.py", line 168, in __init__ Dec 21 08:42:17 new-server mailman-web[981806]: self.start() Dec 21 08:42:17 new-server mailman-web[981806]: File "/local/mailman/venv/lib/python3.10/site-packages/django_q/cluster.py", line 172, in start Dec 21 08:42:17 new-server mailman-web[981806]: self.spawn_cluster() Dec 21 08:42:17 new-server mailman-web[981806]: File "/local/mailman/venv/lib/python3.10/site-packages/django_q/cluster.py", line 248, in spawn_cluster Dec 21 08:42:17 new-server mailman-web[981806]: self.pusher = self.spawn_pusher() Dec 21 08:42:17 new-server mailman-web[981806]: File "/local/mailman/venv/lib/python3.10/site-packages/django_q/cluster.py", line 201, in spawn_pusher Dec 21 08:42:17 new-server mailman-web[981806]: return self.spawn_process(pusher, self.task_queue, self.event_out, self.broker) Dec 21 08:42:17 new-server mailman-web[981806]: File "/local/mailman/venv/lib/python3.10/site-packages/django_q/cluster.py", line 197, in spawn_process Dec 21 08:42:17 new-server mailman-web[981806]: p.start() Dec 21 08:42:17 new-server mailman-web[981806]: File "/usr/lib/python3.10/multiprocessing/process.py", line 121, in start Dec 21 08:42:17 new-server mailman-web[981806]: self._popen = self._Popen(self) Dec 21 08:42:17 new-server mailman-web[981806]: File "/usr/lib/python3.10/multiprocessing/context.py", line 224, in _Popen Dec 21 08:42:17 new-server mailman-web[981806]: return _default_context.get_context().Process._Popen(process_obj) Dec 21 08:42:17 new-server mailman-web[981806]: File "/usr/lib/python3.10/multiprocessing/context.py", line 281, in _Popen Dec 21 08:42:17 new-server mailman-web[981806]: return Popen(process_obj) Dec 21 08:42:17 new-server mailman-web[981806]: File "/usr/lib/python3.10/multiprocessing/popen_fork.py", line 19, in __init__ Dec 21 08:42:17 new-server mailman-web[981806]: self._launch(process_obj) Dec 21 08:42:17 new-server mailman-web[981806]: File "/usr/lib/python3.10/multiprocessing/popen_fork.py", line 71, in _launch Dec 21 08:42:17 new-server mailman-web[981806]: code = process_obj._bootstrap(parent_sentinel=child_r) Dec 21 08:42:17 new-server mailman-web[981806]: File "/usr/lib/python3.10/multiprocessing/process.py", line 314, in _bootstrap Dec 21 08:42:17 new-server mailman-web[981806]: self.run() Dec 21 08:42:17 new-server mailman-web[981806]: File "/usr/lib/python3.10/multiprocessing/process.py", line 108, in run Dec 21 08:42:17 new-server mailman-web[981806]: self._target(*self._args, **self._kwargs) Dec 21 08:42:17 new-server mailman-web[981806]: File "/local/mailman/venv/lib/python3.10/site-packages/django_q/cluster.py", line 358, in pusher Dec 21 08:42:17 new-server mailman-web[981806]: logger.error(e, traceback.format_exc()) Dec 21 08:42:17 new-server mailman-web[981806]: Message: BadSignature('Signature "ofwl5GkP2_1nDnfM8-vAjAwl_Ss" does not match') Dec 21 08:42:17 new-server mailman-web[981806]: Arguments: ('Traceback (most recent call last):\n File "/local/mailman/venv/lib/python3.10/site-packages/django_q/cluster.py", line 356, in pusher\n task = SignedPackage.loads(task[1])\n File "/local/mailman/venv/lib/python3.10/site-packages/django_q/signing.py", line 25, in loads\n return signing.loads(\n File "/local/mailman/venv/lib/python3.10/site-packages/django_q/core_signing.py", line 35, in loads\n base64d = force_bytes(TimestampSigner(key, salt=salt).unsign(s, max_age=max_age))\n File "/local/mailman/venv/lib/python3.10/site-packages/django_q/core_signing.py", line 70, in unsign\n result = super(TimestampSigner, self).unsign(value)\n File "/local/mailman/venv/lib/python3.10/site-packages/django_q/core_signing.py", line 55, in unsign\n raise BadSignature(\'Signature "%s" does not match\' % sig)\ndjango.core.signing.BadSignature: Signature "ofwl5GkP2_1nDnfM8-vAjAwl_Ss" does not match\n',) So any clue how to fix this? Best Regards, Helio Loureiro https://helio.loureiro.eng.br https://github.com/helioloureiro https://mastodon.social/@helioloureiro

3 4

delete unverified accounts
by noemi 21 Dec '23

21 Dec '23

Hi, I'm noticing that a lot of 'spammers' are registering themself via postorius. They do not send emails, neither they are in any list, so they are not technically spammers, but they are a lot [maybe around 500 subscribed in the last month]. While waiting for a captcha system[0] for the main distribution, I'm looking for a rapid/easy way to delete this accounts; since they are not 'verified', I was wondering if I can locate this information in the mailman3 database or if there is some easier way to delete all unverified accounts. Do some of you any help or indications? I'm using GNU Mailman 3.3.9 (Tom Sawyer). Thanks, noemi for pangea.org [ https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… ]

2 1

Is it possible to upgrade from Debian 11 to Debian 12 with Mailman3?
by Pierre Malard 20 Dec '23

20 Dec '23

Hi, Is it possible to upgrade from Debian 11 to Debian 12 with Mailman3 installed on Debian 11? I specify that I want to stay in the Debian repositories, not a "hand" installation of MM3. I tested on a specific server. It was long and tedious but it seemed to me that it was working. In fact everything seems to work except the archive management :-( Here is the procedure followed: Stopping MM services Backup of the database (PostgreSQL) and the base MM directory Switch server from Debian 11 to Debian 12 and restart migrate the database from PG 113 to PG 15 (pg_upgradecluster 13 does this very well) Modify the file /etc/mailman3/mailman.cfg with a URL reference "postgresql://" instead of "postgres://" (see https://lists.mailman3.org/archives/list/ mailman-users(a)mailman3.org/thread/CU6YU44V4WLRJI3WJH2VBWO2HCUF4YEA/) update MM3 databases with "mailman-web migrate" restart MM3 and MM3-web With that MM3 works but not the archiving management! Note that there are no real error messages in the logs… In fact when we go to a list archive, we have pretty waiting wheels... infinite :-( The only reference in mailman3-web.log: [pid: 1429|app: 0|req: 12/12] NNN.NNN.NNN.NNN () {68 vars in 1445 bytes} [Mon Dec 18 16:35:56 2023] GET /hyperkitty/list/admin@ teledetection.fr/ => generated 37443 bytes in 37 msecs (HTTP/1.1 200) 7 headers in 221 bytes (1 switches on core 1) If you have any solution... Thank you in advance, have a good day and happy Christmas -- Pierre Malard Responsable architectures système CDS DINAMIS/THEIA Montpellier IRD - UMR Espace-Dev - UAR CPST - IR Data-Terra Maison de la Télédétection 500 rue Jean-François Breton 34093 Montpellier Cx 5 France « Il n'y a pas de Paradis, mais il faut tâcher de mériter qu'il y en ait un ! » Jules Renard (1864-1910) - Journal, 10 septembre 1903 |\ _,,,---,,_ /,`.-'`' -. ;-;;,_ |,4- ) )-,_. ,\ ( `'-' '---''(_/--' `-'\_) πr perl -e '$_=q#: 3|\ 5_,3-3,2_: 3/,`.'"'"'`'"'"' 5-. ;-;;,_: |,A- ) )-,_. ,\ ( `'"'"'-'"'"': '"'"'-3'"'"'2(_/--'"'"' `-'"'"'\_): 24πr::#;y#:#\n#;s#(\D)(\d+)#$1x$2#ge;print' - --> Ce message n’engage que son auteur <-- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Replaced multipart/alternative part with first alternative.

5 9