- Mailman-users - lists.mailman3.org

Problem creating list members using REST API
by Stephen Daniel 19 Jan '22

19 Jan '22

Mailman3 experts -- I am trying to subscribe a user to a mailing list via the REST API. This works: Posting to url http://localhost:8001/3.1/members POST payload: { "list_id": "<LISTID>", "subscriber": "d13b0bbb29844eb9af4b38dad7bb3707", } RESULT post of "http://localhost:8001/3.1/members" succeeds with code 202 This works does *not *work Posting to url http://localhost:8001/3.1/members POST payload: { "list_id": "<LISTID>", "subscriber": "d13b0bbb29844eb9af4b38dad7bb3707", "pre_approved": true } RESULT post of "http://localhost:8001/3.1/members" fails with code 500 Any suggestions? As best I can tell, inclusion of *any* boolean types in my JSON causes the error code 500. FWIW I am generating the JSON using go language's JSON package. I noticed in the API doc that the boolean values are represented as 'True' rather than 'true'. So I tried converting all instances of 'true' to 'True' in my encoded json. That produced an http 400 error, as it probably should. Thanks! -- Stephen

3 8

clone a list?
by Dave McGuire 18 Jan '22

18 Jan '22

Hi folks. Is there a way to clone or duplicate a list in MM3, i.e. create a list with a different name but other settings etc being identical? Thanks, -Dave -- Dave McGuire, AK4HZ New Kensington, PA

2 2

Mirroring a mailman3 server
by Axel Rau 17 Jan '22

17 Jan '22

Hi all, I have 2 list servers (lists4 and lists5) in an HA configuration. Both share a CNAME (lists.framail.de) in DNS. In case of failover, the postgresql server on the peer becomes master and the CNAME is updated to point at the peer. Both database servers are kept à jour by replication. What else must be synced (by rsync)? Currently (the CNAME points at mailman 2.1 server at the peer. While creating a domain, what should I enter into the fields? Mail Host lists.framail.de (currently lists5.lrau.net) Alias Domain listsl.framail.de Web Host lists.framail.de (currently lists5.lrau.net) Any help appreciated, Axel --- PGP-Key: CDE74120 ☀ computing @ chaos claudius

2 3

REST API for "members" collection?
by Stephen Daniel 17 Jan '22

17 Jan '22

Mailman3 People -- I am trying to manage subscriptions via the REST API. Most of my attempts at using the API work. For example, I can get the list of users: For example: http GET request "http://localhost:8001/3.1/users" returns 200 However, attempting to get the "members" collection fails. http GET request "http://localhost:8001/3.1/members" returns 400 The documentation here <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…> suggests this should work. Any thoughts? Am I using the wrong URL to get the "members" collection? I also tried using the domain URL/members, but that returned a 404 error code. I've also tried posting a structure like this: { "list_id": "LISTNAME", "subscriber": "swd(a)pobox.com", "pre_verified": true, "pre_confirmed": true, "pre_Approved": true, "send_welcome_message": false, "delivery_mode": "regular", "delivery_status": "by_user" } to the members collection, in an attempt to create a subscription. That got an error code 500 Thanks! -- Stephen

1 1

EMWD Mailing Lists Down
by Sherry Xie 16 Jan '22

16 Jan '22

Hi all, I am an EMWD Mailman 3 customer, and I recently realized my mailing lists are no longer working (the last email that went through was sent on December 25, 2021). Emails I send to the lists do not show up in archives or reach subscribers. It seems like others have had this issue before since ownership of the company was transferred following Brian Carpenter's passing – has anyone been able to get in touch with support or get their issues resolved? I've submitted a support ticket but have no idea if this is being monitored. I also have no way to contact the current management team, as only their names were announced in the November 5, 2021 email from Barbara Carpenter. Any help would be greatly appreciated – thanks in advance! Sherry

4 3

Question about adding addresses using the REST API
by Stephen Daniel 16 Jan '22

16 Jan '22

Mailman3 experts -- It is clear from many aspects of the documentation that mailman3 may have addresses in its database that are not connected to any user. I would like to create such addresses using the REST API. The REST API documentation does not suggest this is possible, nor does trying an obvious POST request to the addresses collection work (returns a 405 error). The only way I've found to create addresses with the REST API is to create users. The only way I've found to create a standalone address (not linked to any user) is to create a user with that address, unlink the address, then delete the user. Is there a more straightforward way to just create an address with no user? Thanks! -- Stephen Daniel

3 5

nginx configuration on a multitasking server
by David Newman 16 Jan '22

16 Jan '22

Couple of questions about the sample nginx configuration given in the venv doc and the Mailman Mailman Suite Documentation v. 3.3 PDF: server { listen 443 ssl default_server; listen [::]:443 ssl default_server; server_name MY_SERVER_NAME; location /static/ { alias /opt/mailman/web/static/; } location / { proxy_pass 127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } ssl_certificate /path-to-ssl-certs/cert.pem; ssl_certificate_key /path-to-ssl-certs/privkey.pem; } 1. At least on my system, the proxy_pass statement will only run without errors if I change this to a fully formed URL, e.g., 'proxy_pass http://127.0.0.1:8000'. Is this a typo in the docs? 2. What document root(s) and alias(es) to use for Postorius and Hyperkitty and the Django admin on a server that also runs other services (e.g., Postfix for non-list mail and Roundcubemail)? With MM2, I use location statements with their own root and aliases: location /mailman { root /usr/lib/cgi-bin; fastcgi_split_path_info (^/mailman/[^/]+)(/.*)$; fastcgi_pass unix:///var/run/fcgiwrap.socket; include /etc/nginx/fastcgi_params; fastcgi_param SCRIPT_FILENAME \ $document_root$fastcgi_script_name; fastcgi_param PATH_INFO $fastcgi_path_info; } location /images/mailman { alias /var/lib/mailman/icons; } location /icons { alias /var/lib/mailman/icons; } location /pipermail { alias /var/lib/mailman/archives/public; autoindex on; } What is the MM3 equivalent way to do this? I think root would be somewhere under /opt/mailman but don't know exactly where, or which locations to point to. Many thanks! dn

2 23

under which uid should uwsgi/manage.py run?
by Axel Rau 14 Jan '22

14 Jan '22

My current setup has uid = www gid = www in uwsgi.ini For DB access, I’m using client certs, where the key is only readable for owner, so I have 2 cert locations. One is configured in settings per OPTIONS in DATABASES The other uses the default location .postgresql und the mailman home. Looking at var, I see: (mailman_33) [root@lists5 /usr/local/mailman3/var]# ls -l total 46 drwxr-xr-x 2 mailman www 2 13 Jan. 17:32 archives drwxr-xr-x 2 mailman www 2 13 Jan. 17:32 cache drwxr-xr-x 2 mailman www 2 13 Jan. 17:32 data drwxr-xr-x 2 root www 4 13 Jan. 17:32 etc drwxr-xr-x 3 mailman www 3 13 Jan. 22:22 lists drwxr-xr-x 2 mailman www 4 14 Jan. 10:02 locks drwxr-xr-x 2 mailman www 7 13 Jan. 17:32 logs -rw-rw---- 1 mailman www 6 13 Jan. 17:32 master.pid drwxr-xr-x 2 mailman www 2 13 Jan. 17:32 messages drwxr-xr-x 14 mailman www 14 13 Jan. 17:32 queue drwxr-xr-x 2 mailman www 2 13 Jan. 17:32 templates I could allow write access for group www, but I suspect other problems. What is the recommended setting? Axel --- PGP-Key: CDE74120 ☀ computing @ chaos claudius

4 6

Issues with importing archives from a particular list
by Prasanth Nair 14 Jan '22

14 Jan '22

Hello, We are trying to import archives from Mailman2 to Mailman3. For a particular list, it is not importing all of the messages. We can see that Mailman2 has archives from 2015 to 2022. But, it only imports messages from 2018 to 2022 to the Mailman3 server. It was not giving any errors while importing. All other lists are imported successfully. Any idea what was causing the problem? Kind regards, Prasanth

3 2

REST API authorization failed
by Axel Rau 13 Jan '22

13 Jan '22

Hi all, I’m going to do a mailman2->3 migration in a FreeBSD jail. I installed mailman3 in an venv from pypi, along with nginx, uwsgi and exim. The above error happens when I try to open the base url of my server with a browser (is redirected to postorius/lists/) (no errors on admin/ and hyperkitty urls) Same passwords and users in mailman.cfg: [webservice] hostname: localhost port: 8001 use_https: no admin_user: restadmin admin_pass: ??? and in settings.py: MAILMAN_REST_API_URL = 'http://localhost:8001' MAILMAN_REST_API_USER = 'restadmin' MAILMAN_REST_API_PASS = ??? Its a long password, created as secret key by manage.py Axel --- PGP-Key: CDE74120 ☀ computing @ chaos claudius

4 8