- Mailman-users - lists.mailman3.org

Docker Core Configuration "MUST" Documentation
by James Bowery Dec. 23, 2020

Dec. 23, 2020

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 Dec. 22, 2020

Dec. 22, 2020

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 Dec. 17, 2020

Dec. 17, 2020

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 Dec. 17, 2020

Dec. 17, 2020

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 Dec. 16, 2020

Dec. 16, 2020

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 Dec. 15, 2020

Dec. 15, 2020

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 Dec. 15, 2020

Dec. 15, 2020

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

Data too long for column 'data' in workflowstate
by Morris Jones Dec. 14, 2020

Dec. 14, 2020

I ran into this error attempting to add a user to a mailing list: (pymysql.err.DataError) (1406, "Data too long for column 'data' at row 1") [SQL: INSERT INTO workflowstate (token, step, data) VALUES (%(token)s, %(step)s, %(data)s)] [parameters: {'token': '7394fbf654b3faffc6a65eb95e0616eea6651b9e', 'step': 'do_confirm_verify', 'data': '{"pre_approved": false, "pre_confirmed": false, "pre_verified": false, "invitation": false, "address_key": "dorothyxxxxxxxx(a)gmail.com", "subscriber_key": 1, "user_key": "00201c01dcc443c3a0d8f6d1ea42e230", "token_owner_key": 1, "send_welcome_message": null}'}] In MySQL I see that column 'data' in workflowstate is VARCHAR(255), and the data in the query is 259 characters. If I have a moment I'll write a bug or patch ... but I'm not really current on schema migrations. Mojo -- Morris Jones, Monrovia, CA BridgeMojo <http://bridgemojo.com> Old Town Sidewalk Astronomers <http://otastro.org> Mojo's Blog <http://mojo.whiteoaks.com>

2 2

Permission denied for /list:member:digest:header.txt
by Eric Broens Dec. 14, 2020

Dec. 14, 2020

Hi, despite mailman is running as mailman user and the required periodic jobs have all been created in crontab for the mailman user, a permission denied exception for the digest file has been logged in mailman.log: Dec 14 11:31:42 2020 (399913) Uncaught runner exception: [Errno 13] Permission denied: '/var/lib/mailman3/templates/lists/...//list:member:digest:header.txt' The subdirectories and files of the templates subdirectory got the root owner and group: drwxr-xr-x. 3 mailman mailman 4096 Dec 12 17:58 templates drwxr-xr-x. 11 root root 4096 Dec 12 19:20 lists -rw-rw----. 1 root root 16 Dec 12 19:19 list:member:digest:header.txt How can this be avoided? Best Regards,Eric

3 8

Importing config and archives only partially succeeded?
by Eric Broens Dec. 13, 2020

Dec. 13, 2020

Today I have migrated about 30 mailinglists from mailman 2.1 to mailman 3.3.2 & Hyperkitty 1.3.3. Although no error responses were given when importing the 2.1 pck files, and neither for importing the archives, for about half of the mailinglists the hyperkitty webpage doesn't show any subscribers, nor archived emails. The imported members and other settings are correctly shown in the postorius page. Is there anything that I can verify why the archive is not shown on the hyperkitty page?The hyperkitty_email database table does contain the emails. Thanks in advance,Eric

2 11