- Mailman-users - lists.mailman3.org

Syncing Real Name between user account and membership
by Andreas Barth 31 Dec '20

31 Dec '20

Hi together, a user was mass-subscribed (with a wrong name) and now registered and changed his name via the web interface but the list entry is not changed. On looking further at that, I got to the following json outputs: curl -urest:pass http://localhost:8001/3.0/addresses/user@example.com/user { "created_on": "2020-11-26T15:43:24.928285", "is_server_owner": false, "self_link": "http://localhost:8001/3.0/users/123456", "user_id": 123456 "display_name": "Fixed Name", } curl -urest:pass http://localhost:8001/3.0/addresses/user@example.com { "email": "user(a)example.com", "original_email": "user(a)example.com" "registered_on": "2020-11-26T15:43:24.896405", "self_link": "http://localhost:8001/3.0/addresses/user@example.com", "display_name": "Broken Name", "verified_on": "2020-11-26T15:43:24.965784", "user": "http://localhost:8001/3.0/users/123456" } Should the fix of the name propagate? Or what would be the appropriate action here? Regards, Andi

4 9

Upgrade to 3.3.2 fails
by Joel Lord 28 Dec '20

28 Dec '20

I've just upgraded python to 3.7, so now I can upgrade mailman from 3.3.1 to 3.3.2. Take it down, "pip install --upgrade mailman", and try a "mailman info". It fails hard, and what I think are the important parts of the stack trace are: sqlalchemy.exc.OperationalError: (pymysql.err.OperationalError) (1118, 'Row size too large. The maximum row size for the used table type, not counting BLOBs, is 8126. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs') [SQL: ALTER TABLE mailinglist ADD COLUMN archive_rendering_mode INTEGER] (Background on this error at: http://sqlalche.me/e/13/e3q8) Looks to me like the mailinglist table has been using awfully close to the default mysql max row length, and this added column pushes me over? Is there some other fix other than a terrifyingly gigantic process of dumping all my databases, changing my page size, and restoring them all? This DB server isn't serving just mailman... Thanks -- Joel Lord

3 7

WEB UI fail to reply and create new thread
by Milan P. Stanić 23 Dec '20

23 Dec '20

Hi, Alpine Linux is testing mailman3 as system for project mailing lists. We created docker-compose which can be seen here https://gitlab.alpinelinux.org/alpine/infra/compose/mailman We installed it and run in testing system here https://lists-test.alpinelinux.org/hyperkitty/ Sending mail by mail clients works and mails are sent to subscribers properly. Most other 'things' works but we have problem with reply to posts and creating new threads using web ui. When replying to post with web ui it says that the everything is ok and post is sent but post doesn't arrive to mailing list. Same happens with creating new thread. Our debug says "KeyError: 'display_fixed'" but we are not sure what should be changed/fixed/set for this problem. Attached is excerpt from debug log. TIA, mps

4 5

Docker Core Configuration "MUST" Documentation
by James Bowery 23 Dec '20

23 Dec '20

The docker core configuration README says: "These are the variables that you MUST change before deploying:" Does this mean: "The following variables MUST be set in /opt/mailman/core/mailman-extra.cfg (on the host) to match the values in docker-compose.yaml before deploying:" ?

2 1

Re: Equivalent Apache2 Directives for Those From the Docker Nginx Documentation?
by James Bowery 22 Dec '20

22 Dec '20

Thanks. That configuration worked for me -- at least to the point that I got this in my apache error log, which means the proxy pass was working: [Sun Dec 20 22:45:02.548267 2020] [proxy:error] [pid 18049] (111)Connection refused: AH00957: uwsgi: attempt to connect to 172.19.199.3:8080 (172.19.199.3) failed [Sun Dec 20 22:45:02.548294 2020] [:error] [pid 18049] [client ....:59424] AH10101: failed to make connection to backend: 172.19.199.3:8080 On Mon, Dec 14, 2020 at 10:03 PM <matthew(a)alberti.us> wrote: > James, > This is what I put in my apache2 conf for the mailman virtual host: > > #Mailman3 Web Configuration > Alias /favicon.ico /opt/mailman/web/static/hyperkitty/img/favicon.ico > > Alias /static /opt/mailman/web/static > <Directory /opt/mailman/web/static> > Require all granted > </Directory> > > ProxyPassMatch ^/static ! > ProxyPassMatch ^/favicon.ico ! > ProxyPass / uwsgi://172.19.199.3:8080/ > > I don't believe I did anything to uwsgi's conf. One thing I did > notice is that the '/' on the end of the 'ProxyPass' command (last line) is > relevant. I think it didn't work right without it. > > I am interested to hear from others if that configuration is > complete. It works as far as I know. > > - Matt Alberti > > -----Original Message----- > From: James Bowery <jabowery(a)gmail.com> > Sent: Monday, December 14, 2020 8:27 PM > To: mailman-users(a)mailman3.org > Subject: [MM3-users] Equivalent Apache2 Directives for Those From the > Docker > Nginx Documentation? > > The Docker documentation at: > > https://asynchronous.in/docker-mailman/#dependencies > > I've installed and enabled proxy_uwsgi for Apache and made a rough cut at a > configuration for the lists.* subdomain in question but it's failing. > > What follows are the document's Nginx directives for which I would greatly > appreciate the Apache2 equivalents. I'm attempting to move a mailing list > off of Yahoo groups onto my hosted server using an Apache2's virtual host > on > the 'lists' subdomain: > > Setting up your web server: > > # Nginx configuration. > > location / { > # First attempt to serve request as file, then > > proxy_pass http://172.19.199.3:8000; > include uwsgi_params; > uwsgi_read_timeout 300; > proxy_set_header Host $host; > proxy_set_header X-Forwarded-For $remote_addr; > } > > uwsgi: > > # Nginx configuration. > > location / { > # First attempt to serve request as file, then > > uwsgi_pass 172.19.199.3:8080; > include uwsgi_params; > uwsgi_read_timeout 300; > } > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe > send > an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > >

3 8

Message Sent to A Re-Created List Results In Error
by matthew＠alberti.us 17 Dec '20

17 Dec '20

I created a list in the Postorius interface, used it, and then deleted it. A week or so later, I re-created the list, and things were fine thru the creation and subscription process. But when I sent a message to the list, a "550 user unknown" error was sent back. I tried to determine if this is a known issue by searching the issues in Gitlab; but didn't find anything. But wanted to ask if this was a known issue or not? Thanks. - Matt Alberti

4 5

moderator cannot login to the list
by Gregory Edigarov 17 Dec '20

17 Dec '20

Hello, I am using this mailman: GNU Mailman 3.2.1 (La Villa Strangiato) Python 3.7.3 (default, Jul 25 2020, 13:03:44) I've imported some lists from mailman-2.1 using 'mailman import21' command. the import went fine, I am able to login into postorius as admin, and see all imported mail list data. but login as a moderator member of a list. I tried to reset moderator password via rest api. That doesn't help. how is that supposed to be done? thank you. -- With best regards, Gregory Edigarov

3 2

Mailman automatic accept notification
by tambet.paide＠mkm.ee 16 Dec '20

16 Dec '20

How can I configure mailman so that all the users in mailing list won't get automatic accept notification (uncaught bounce notification)? I'n mailman configure I cant find nothing about disabling bounce message. I'm using Mailman 3 and cat figure it out

4 8

Handling of (un)subscribe mails for already (un)subscribed users
by Andreas Barth 15 Dec '20

15 Dec '20

Hi, I noticed that a mail to -subscribe for an already subscribed user doesn't get any response (about line 225 in mailman/src/mailman/app/subscriptions.py). Same but different for unsubscribe for users not on the list. I'd need these kind of mails however in hope that users complain less. Would that be generally interessting, and if so, any special requirements for submitting patches, or should I just do that locally? Regards, Andi

3 7

Equivalent Apache2 Directives for Those From the Docker Nginx Documentation?
by James Bowery 15 Dec '20

15 Dec '20

The Docker documentation at: https://asynchronous.in/docker-mailman/#dependencies I've installed and enabled proxy_uwsgi for Apache and made a rough cut at a configuration for the lists.* subdomain in question but it's failing. What follows are the document's Nginx directives for which I would greatly appreciate the Apache2 equivalents. I'm attempting to move a mailing list off of Yahoo groups onto my hosted server using an Apache2's virtual host on the 'lists' subdomain: Setting up your web server: # Nginx configuration. location / { # First attempt to serve request as file, then proxy_pass http://172.19.199.3:8000; include uwsgi_params; uwsgi_read_timeout 300; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } uwsgi: # Nginx configuration. location / { # First attempt to serve request as file, then uwsgi_pass 172.19.199.3:8080; include uwsgi_params; uwsgi_read_timeout 300; }

2 1