- Mailman-users - lists.mailman3.org

Only held_messages for 1 (of 3) list has "Mailman REST API not available" message.
by Duane Raymond 10 Jan '22

10 Jan '22

Hi everyone, Today my stable mailman3 server started having web access problems. It specifically applies to only one of three lists on the mailman server (one of the others use the same domain name) and only to the held_messages page as admin. It displays the "Mailman REST API not available..." message despite the other two lists displaying it fine. I've rebooted the server and mailman core, but the problem remains (which is what I've seen suggested on this forum for the same error message so far). I've been running a stable mailman3 server for the last 9 months and only updating the security patches for the the underling OS (Debian 10 with postgresql and nginx), I've encountered a problem that just seemed to appear today (wish no recent changes on the server). Any suggestions or diagnosis to resolve it? Duane

2 4

modify subscription page by mailinglist?
by Lars Schimmer 10 Jan '22

10 Jan '22

Hi Is it (easy) possible to modify the subscription page individual per mailinglist? If so, since which version? And how? Is there a guide? Thank you. MfG, Lars Schimmer -- ------------------------------------------------------------- TU Graz, Institut für ComputerGraphik & WissensVisualisierung Tel: +43 316 873-5405 E-Mail: l.schimmer(a)cgv.tugraz.at Fax: +43 316 873-5402 PGP-Key-ID: 0x4A9B1723

3 4

Still unable to get mailman3 working on Ubuntu 20.04 LTS
by Michael Heseltine 10 Jan '22

10 Jan '22

Hi all, after many more attempts, I've still failed to find any set of instructions that can install mailman3 on an Ubuntu 20.04 LTS server of mine. I've recently switched to a new server without any previous installation (apart from an apache web server) so that I can follow the instructions provided in https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10 to the letter, if possible. But still, I run into an error I do not understand. I have followed the instructions until this point: > # pip install importlib_resources==1.1.0 > Once the above packages are installed run “mailman info” in your virtual environment. That will install Mailman core into your /opt/mailman/mm/var directory. (I had to add "apt install libmemcached-dev" to the instruction for "pip install psycopg2-binary" to succeed.) Then, I run "mailman info", but get an error message: > File "/opt/mailman/mm/venv/lib/python3.8/site-packages/sqlalchemy/engine/default.py", line 508, in connect > return self.dbapi.connect(*cargs, **cparams) > File "/opt/mailman/mm/venv/lib/python3.8/site-packages/psycopg2/__init__.py", line 122, in connect > conn = _connect(dsn, connection_factory=connection_factory, **kwasync) > sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) connection to server at "localhost" (::1), port 5432 failed: FATAL: password authentication failed > for user "mailman" > connection to server at "localhost" (::1), port 5432 failed: FATAL: password authentication failed for user "mailman" This suggests that the connection to postgresql fails, but if I test this using # psql --user mailman and type in the password listed in settings_local.py, I can login fine. I've also changed the port number in that configuration from '' to '2222', but the connection is still made to port 5432, which suggests to me that my call to mailman info uses another set of connection parameters provided elsewhere. Where can this be found? How will I be able to run "mailman info" w/o error and continue the installation as detailed in https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10 ? Any help is appreciated. Happy new year, Michael.

4 25

Bulk changes to delivery mode and moderation action
by David Newman 08 Jan '22

08 Jan '22

I fat-fingered a command in the Postorius UI and accidentally unsubcribed all members of a list. Oops. Have added them back using Mass operations/Mass subscribe but this raised three questions: 1. In Users/Members, moderation action for the newly resubscribed users shows as "None". Is there a method, either in the UI or the command line, to change this to "Default processing" for all users? 2. Although Delivery Mode shows as "Regular" for all users in Users/Members list, clicking on a member's name shows all options such as delivery status, delivery mode, etc., as undefined. Similar question: How to set subscriber options for all members in one go? 3. As a subscriber to this list, I received email notification that I'd been unsubscribed. Where is the control for enabling/disabling subscription notifications? Settings/Member Policy/Un-subscription Policy is set to Confirm, but I don't think that's relevant here since I unsubscribed users as the Django superuser. Thanks. dn, chastened

2 7

unwanted chunked delivery
by mm3-omf＠sh.werbittewas.de 07 Jan '22

07 Jan '22

hello, we've a mailing-list with currently 81 recipients running with debian-dist mailman3 3.3.3-1. every post to this list will be chunked into one delivery with 60 recipients and one delivery with 21 recipients. we've searched a bit and found a config-option "max_recipients" for bulk-transfers, but we haven't set it and (as we understand the explaination for this option) then there should be no limit in one transfer to the MTA. nevertheless, we've tried to set it to a high value, but even this doesn't change anything in behaviour. any search for '60' within mailman3 gives no relevant results. could someone tell us, where the limit of 60 comes from and how we could change it to unlimited? thanks. omf

2 3

[Mailman-Users] Listservers currently hosted with EMWD - urgent request for assistance
by Stephen J. Turnbull 07 Jan '22

07 Jan '22

Note: Reply-To set to mailman-users(a)mailman3.org. Please check that any replies are addressed to that list, and not mailman-users(a)python.org. Jonathan, FWIW, I haven't heard anything. I have 3 students submitting MS/PhD theses in less than (checks watch) 18 hours, but after that I'll see if I can find out anything. I wouldn't bet on it, though, as I don't think anyone here has a connection to the Carpenter family or whoever is left of the EMWD staff. I assume you have checked the emwd.com website? > We have our listservers hosted with EMWD which stopped working on > 23 December. What does "stopped working" mean? I assume that list traffic is no longer being forwarded to subscribers, but perhaps other services are working. It may help if you can answer the following questions. 1. Are you using the GNU Mailman-supplied Postorius/HyperKitty combination for administration and archiving, or EMWD's proprietary "Harmony" (Affinity/Empathy) platform? 2. Can you see archives (if any)? 3. Can you log in to the administrative interface? 4. Is mail to the lists being returned to sender, or just disappearing into the void? 5. You mention an automated response in a later message. Is that to an email you sent, or from a web-based issue-tracking system? What does it say about the current status of EMWD services, if anything? Regards, Steve > We have since found out the devastating news that > Brian Carpenter passed away last year. Brian was really helpful > when we moved our listservers from a legacy system to hosting on > the EMWD platform. My sincere condolences to his family and > friends. > > As we can no longer get a response from EMWD about our listserver issue I was wondering if any one else in this community could help. > > Many thanks. > > Jonathan > > Jonathan Ashby > ICT Strategic Communications Project Manager > Londonwide LMCs and Londonwide Enterprise Ltd > Working days: Tuesday and Wednesday > Direct dial: 020 3818 6228 > Mobile: 07768 109601 > Fax: 020 7383 7442 > Email: jonathan.ashby(a)lmc.org.uk > Web: www.lmc.org.uk > Twitter: @LondonwideLMCs > > > > ---------------------------- > Visit www.lmc.org.uk/coronavirus-covid-19 for the latest official resources and guidance on covid-19. > > Remember that you can use WhatsApp and FaceTime for online consultations as well as the usual online tools. > 🌲 Think of the environment. Do you really need to print this email? > This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please accept our apologies and notify the sender. > > The registered and office address for Londonwide Local Medical Committees Limited is: Tavistock House South, Tavistock Square, London WC1H 9LG. Registered in England No: 6391298. > > Londonwide Enterprise Limited is a wholly owned subsidiary of Londonwide Local Medical Committees Limited. Londonwide Enterprise Limited is registered at: Tavistock House South, Tavistock Square, London WC1H 9LG. Registered in England No. 6990874. Londonwide Enterprise Limited is registered as a Company Limited by Shares. VAT no: 130 1454 66. > > Londonwide Local Medical Committees Limited and Londonwide Enterprise Limited do not provide legal or financial advice and thereby excludes all liability howsoever arising in circumstances where any individual, person or entity has suffered any loss or damage arising from the use of information provided by Londonwide Local Medical Committees Limited and Londonwide Enterprise Limited in circumstances where professional legal or financial advice ought reasonably to have been obtained. > > Londonwide Local Medical Committees Limited and Londonwide Enterprise Limited provide guidance and support to GPs and practice teams in the Londonwide area. Additionally Londonwide Local Medical Committees Limited provides representation to GPs and practice teams in the Londonwide area. Londonwide Local Medical Committees Limited and Londonwide Enterprise Limited strongly advises individuals or practices to obtain independent legal or financial advice. > > ------------------------------------------------------ > Mailman-Users mailing list -- mailman-users(a)python.org > To unsubscribe send an email to mailman-users-leave(a)python.org > https://mail.python.org/mailman3/lists/mailman-users.python.org/ > Mailman FAQ: http://wiki.list.org/x/AgA3 > Security Policy: http://wiki.list.org/x/QIA9 > Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ > https://mail.python.org/archives/list/mailman-users@python.org/

2 2

Request for help with configuring "from" headers in mailman3 list
by Stephen Daniel 06 Jan '22

06 Jan '22

Mailman3 users -- I am in the process of migrating a set of mailing lists from a very old privately operated server running mailman2 to a VM in Google's cloud (GCP) running mailman3. I have mailman3 up and running in GCP. However, VM's in GCP are not permitted to send emails. To work around this I configured postfix relay SMTP traffic through sendgrid.com. I chose Sendgrid because they offer a free service for low volume users. This works well for emails generated by the mailman3 system. However, it does not work for the list traffic itself. Sendgrid requires that the "From:" address on any email reference an authenticated domain. In the old mailman2 implementation, emails sent by mailman are listed as From: <human name via LISTNAME> LISTNAME(a)LISTDOMAIN.org Reply-to: <human name> sender(a)senderdomain.com (the original email's sender) Sendgrid would be happy with this, because LISTDOMAIN.org is a validated domain. However, in my mailman3 implementation, the From: header lists the original email's sender. Sendgrid rejects this because the original email's sender's address is not one of the validated domains. How do I configure mailman3 to generate headers in the same style as the old mailman2 implementation? Thanks! -- Stephen Daniel

2 2

Request for help debugging a hyperkitty connection issue
by Stephen Daniel 06 Jan '22

06 Jan '22

Mailman folk -- I've recently completed a complete install of the mailman3 suite on a Debian VM in Google Cloud (GCP). I used the excellent directions given here: https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10 Most things appear to work. Postorius is working, and I can create accounts, email lists, etc. I have two problems. One is with getting list mail out of GCP. I am working on that. The issue I don't know how to address is a problem with hyperkitty. Nothing is being archived. When I send an email through my test list, this message shows up in the mailman log: Jan 04 11:57:26 2022 (806) Exception in "hyperkitty" archiver Traceback (most recent call last): File "/opt/mailman/mm/venv/lib/python3.7/site-packages/urllib3/connection.py", line 175, in _new_conn (self._dns_host, self.port), self.timeout, **extra_kw File "/opt/mailman/mm/venv/lib/python3.7/site-packages/urllib3/util/connection.py", line 73, in create_connection for res in socket.getaddrinfo(host, port, family, socket.SOCK_STREAM): File "/usr/lib/python3.7/socket.py", line 748, in getaddrinfo for res in _socket.getaddrinfo(host, port, family, type, proto, flags): socket.gaierror: [Errno -2] Name or service not known This triggers a bunch more tracebacks. Then I get this: Jan 04 11:57:27 2022 (797) Connection to HyperKitty failed: HTTPSConnectionPool(host='www.XXXXX.dev <http://www.xxxxx.dev/>', port=443): Max retries exceeded with url: /archives/api/mailman/archive (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f2114e14e10>: Failed to establish a new connection: [Errno -2] Name or service not known')) Jan 04 11:57:27 2022 (797) Exception in the HyperKitty archiver: HTTPSConnectionPool(host='www.XXXXX.dev <http://www.xxxxx.dev/>', port=443): Max retries exceeded with url: /archives/api/mailman/archive (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f2114e14e10>: Failed to establish a new connection: [Errno -2] Name or service not known')) Jan 04 11:57:27 2022 (797) Traceback (most recent call last): File "/opt/mailman/mm/venv/lib/python3.7/site-packages/urllib3/connection.py", line 175, in _new_conn (self._dns_host, self.port), self.timeout, **extra_kw File "/opt/mailman/mm/venv/lib/python3.7/site-packages/urllib3/util/connection.py", line 73, in create_connection for res in socket.getaddrinfo(host, port, family, socket.SOCK_STREAM): File "/usr/lib/python3.7/socket.py", line 748, in getaddrinfo for res in _socket.getaddrinfo(host, port, family, type, proto, flags): socket.gaierror: [Errno -2] Name or service not known I think this second error is just mailman3 reporting that it had trouble with hyperkitty because of the first error. How can I get more information about what connection is being attempted when this failure occurs? Thanks! -- Stephen Daniel

2 2

Postorius & multi domain
by Gelpi Andrea 06 Jan '22

06 Jan '22

Hi, on a fresh debian 10 (mail server) I added mailman3 with: apt-get install mailman3-full dpkg-reconfigure mailman3 dpkg-reconfigure mailman3-web The server name is webserver-A Then I log in in webserver-A/mailman3 as a superuser I created a domain for webserver-A and domain-A The I created a list-A Then I created a second domain for webserver-B and domain-B Then I added to apache config a virtual host for webserver-B I log in webserver-B as the some superuser of webserver-A and I created a list-B But when I list the lists I can see both under webserver-A and webserver-B. The some problem with archiving hyperkitty. I search internet for a while and I discovered that using FILTER_VHOST = True seems to solve the problem. >From posotrius config page: FILTER_VHOST Filter the list of available lists in Postorius and Hyperkitty depending on the domain they are being currently served from. Mailman 3 supports multiple domains in a single installation. But it doesn't work. I got err 500 form apache. Were can I find an explanation or a how to configure the system to have 2 webserver with different domains working on the some server as it was with mailman 2? P.S.: I upgrade postorius to V. 1.3.2 and djando V 2.2.12 using the packages in testing distribution. The debian 10 official postorius package is too old (1.2.24) and does not support FILTER_VHOST Thanks in advance - -- Gelpi ing. Andrea ************************************************** I documenti vitali dimostreranno la loro vitalitˆ spostandosi spontaneamente da dove li avevate lasciati a dove non riuscirete a trovarli. **************************************************

4 13

Hipperkitty failing to archive messages in a list
by Guillermo Hernandez (Oldno7) 06 Jan '22

06 Jan '22

First of all, best wishes and Happy New Year for everybody. Two days ago I had to reinstall all mailman3 related apps in a mailman 3 server (I tried to upgrade just hipperkitty, but it went bad). At first, all seemed running as before, but I just noted that the messages are not being archived. I did not change any config. Now the log is showing ERROR 2022-01-03 12:22:15,654 7165 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. ERROR 2022-01-03 12:22:15,674 7165 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. ERROR 2022-01-03 12:22:15,791 7165 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. ERROR 2022-01-03 12:22:16,208 7165 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. ERROR 2022-01-04 11:44:55,644 30518 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header ERROR 2022-01-04 11:44:55,664 30518 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header ERROR 2022-01-04 11:44:56,478 30518 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header ERROR 2022-01-04 11:44:56,620 30518 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header ERROR 2022-01-04 11:44:56,647 30518 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header (it's a very low traffic list: just two messages in two days) I do believe I did the upgrade/reinstall procedure as in previous upgrades (using pip: it's a system wide installation, not using dockers or venv), but seems that I did something wrong The messages are being delivered normally, but it fails archiving Before I make a bigger hole for myself, where to look for? Versions installed: HyperKitty 1.3.5 mailman 3.3.5 mailman-hyperkitty 1.2.0 mailmanclient 3.3.3 postorius 1.3.6 uWSGI 2.0.19.1 Mailman Core Version GNU Mailman 3.3.5 (Tom Sawyer) Mailman Core API Version 3.1 Mailman Core Python Version 3.7.9 (default, Nov 30 2020, 10:49:53) [Clang 10.0.1 (git@github.com:llvm/llvm-project.git llvmorg-10.0.1-0-gef32c611a -- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: firma-GHP-emails.png Replaced multipart/alternative part with first alternative.

2 8