- Mailman-users - lists.mailman3.org

mailman 2.1 or 3.0 (or another MLM)
by nate 29 Jan '22

29 Jan '22

Hello mailman users out there - I have been a casual user of mailman for 21 years now I think it is. Most of my lists were super small (my only current lists have no more than 8 members each), super low volume. It's "just worked" over the years, no issues. I have been using Linux since 1996, not a newbie here. 21 years ago I deployed mailman as part of our corporate email and then there were a lot more users. Since that time I just use mailman on my personal server. I did a apt-get dist-upgrade on my system and was surprised to see mailman had vanished. Wasn't expecting that.. not a big deal, or so I thought. I am running Devuan 4, which is based on Debian. Investigating further it seems Debian at some point dropped Mailman 2.1 and started including Mailman 3. OK, not too bad I thought.. I was/am prepared to start my mailing lists from scratch again, manually copy/paste over settings/users/etc. Don't care about archives etc. I setup mailman 2.1 on another Devuan 3.x system and copied my mailman configs over to it, and can view them fine via the mailman cgi scripts through Apache, I was planning on just copy/pasting list settings between the two systems for each list. Roughly 10-15mins into trying to get mailman3 off the ground I just find myself overwhelmed. That doesn't happen often. I'm honestly completely shocked at how it seems the complexity of the system has increased by orders of magnitude. I have been browsing around https://docs.mailman3.org/en/latest/pre-installation-guide.html (and other links on that documentation site) But as much information as there is, to me there really isn't any information there. If that makes sense. I'm sure it doesn't make sense so let me give an example. On this page: https://docs.mailman3.org/en/latest/config-web.html I assume that would lead me to how do I configure the web interface so I can do stuff with it. I setup an admin account, then it goes into scheduled tasks(which appear to be handled by the Debian package already but don't know what these tasks would have to do with a web interface). I tried sending a test email but that failed, I looked at the setting up email portion but it does not give any indication where that config would be stored, a recursive grep on /etc for EMAIL_BACKEND turns up nothing (there is a /etc/mailman3 directory with some files in there). Then it goes into other things like task queues, full text searching, here I am just looking for info on where this web interface is, where is the config, what port does it listen on? Is it a cgi like mailman2? It seems like it could be a standalone service. Then it shows a bunch of other settings, not indicating what file these are stored in(or what directory the file is in), etc etc etc. Debian's own documentation is severely lacking in this department as well, normally I am used to going to /usr/share/doc/<package>/ and there is some useful stuff. There is stuff for mailman3 but it's minimal at best. So I'm thinking mailman3 is not the package for me. I've really appreciated mailman 2.1 (and earlier versions) as I said they always just worked, never had to think about them. I'm sure a lot of good hard work has been put into 3, I just don't recall the last time I looked at a project and just honestly didn't even know where to begin which surprised me so much given my 20+ year history of mailman as a user and as an admin. Is there some document(s) out there that would be more beneficial to me in setting up mailman3? I see that mailman 2 looks like it's still being maintained, I assume mailman3 is the result of python3 code and mailman2 perhaps uses python 2.7? I am unsure on the ability to run mailman2 on a modern Debian-based distro since of course Python 2.7 is pretty obsolete at this point (or maybe Mailman 2.1 doesn't use python I don't recall). I could try to install the older mailman 2.1 package on Devuan 4 and see what happens I don't know if it would be that simple or not. Or is there a better MLM for simple use cases? I used Majordomo back in the 90s and was happy to get onto Mailman from that. Something similar to Mailman 2.1 in features/functionality. Worst case I could just use aliases in my postfix config at the end of the day that is all that is really needed, though I do like some level of access control on who can email the lists(even if nobody outside the list knows the list exists), I've had some of these lists for 2 decades, old habits die hard right? I did some searches for mailing list software on the Debian package archives and saw a few options, nothing really stood out at me as something super interesting yet though. I don't mean to come across as harsh or complaining or anything I'm just here in shock kind of. Thinking about what the best solution for me would be. My mailing lists have been broken for a couple of weeks but that's really not a big deal. thanks nate

6 14

Cannot request password reset: "The e-mail address is not assigned to any user account"
by dave＠aasv.org 28 Jan '22

28 Jan '22

I have set up Mailman Core Version GNU Mailman 3.3.5 with Mailman Core API Version 3.1 (Python 3.8.10) using the version 0.40 Docker images. I was able to get things set up and tested by requesting a password reset for the MAILMAN_ADMIN_USER specified in the docker.yaml. Using the web API, I have created several mailing lists and I have added members to these lists also using the web API (most relevant: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…), specifying that each member is already pre_verified, pre_confirmed, and pre_approved. The lists themselves seem to be working fine. The problem is when our staff try to reset their password (through Postorious) to get access and do moderation tasks. The error message "The e-mail address is not assigned to any user account" displays no matter which email address I enter (except the one from MAILMAN_ADMIN_USER which works). Using the MAILMAN_ADMIN_USER I can sign in, view the list of all the users, see their Addresses (one each) and Subscriptions, but even after toggling off "Verified" for the staff email address, clicking Update, then turning Verified back on and updating again, I still can't reset the password for that email address from the "forgot pasword" screen. Even tried adding that email address as another list owner. I have not made any API calls specific to adding users because the API documentation says, "Since her email address is not yet known to Mailman, a user is created for her." This does seem to have happened; GET 127.0.0.1:8001/3.1/users does show everyone's display name and unique user_id strings. I have tried using the API to PATCH a temporary password to the user but that didn't fix the inability to reset. The encrypted password does show in the /users/ data reported by the API (where previously there had been none), and a POST to users/<user_id>/login with that password return the 204 status shown to indicate success (instead of 403)... but I can't log in using Postorious with this user's email address and password. I also tried PATCHing the cleartext_password to /users/<email_address> and wasn't able to login or reset after that either. According to the API, each of the users -- webadmin where I can reset the password and staff where I can't -- does have a single address. (In the following, I redacted the API username and password ; changed email addresses, and IP address. And the display name, but left the timestamps and user_ids ) $ curl --user xxxx:xxxx "127.0.0.1:8001/3.1/users/29bf1eef2ee14f39a7990757544f11a9/addresses" {"start": 0, "total_size": 1, "entries": [{"email": "webadmin(a)example.com", "original_email": "webadmin(a)example.com", "registered_on": "2021-11-25T04:20:33.408184", "self_link": "http://1.2.3.4:8001/3.1/addresses/webadmin@example.com", "verified_on": "2021-11-25T04:20:33.960577", "user": "http://1.2.3.4:8001/3.1/users/29bf1eef2ee14f39a7990757544f11a9", "http_etag": "\"394c07148f3fd0479cc582358b63b919fd988e36\""}], "http_etag": "\"a6621373598d299c32aa946fef7e32167d796bf3\""} $ curl --user xxxx:xxxx "127.0.0.1:8001/3.1/users/73235926306843ccb41f288d0464240a/addresses" {"start": 0, "total_size": 1, "entries": [{"email": "staff(a)example.com", "original_email": "staff(a)example.com", "registered_on": "2021-12-15T02:25:24.055741", "self_link": "http://1.2.3.4:8001/3.1/addresses/staff@example.com", "display_name": "Staff Member", "verified_on": "2021-12-15T02:40:04.941153", "user": "http://1.2.3.4:8001/3.1/users/73235926306843ccb41f288d0464240a", "http_etag": "\"f24ba7ca9d71a7f814dc41d70c48ce947c1324be\""}], "http_etag": "\"e8d5b9f3ce0abbc7bbf51c03c69367f82679f93e\""} I am probably missing something, but this second query seems to confirm that the address "staff(a)example.com" is assigned to the user 73235926306843ccb41f288d0464240a and so shouldn't I should be able to request a password reset for "staff(a)example.com"? I've tried tailing all the log files I can find while attempting the reset and am not seeing any error messages, but I don't know exactly where to look. Thank you for any suggestions for what to try next! Dave

3 4

bounce handling in mm3 available?
by Stefan Bauer 28 Jan '22

28 Jan '22

Hi, what happens with bounce-mails that are processed by mailmans postfix instance? Jan 24 10:46:03 l01 postfix/lmtp[8432]: DF4AE600623: to=<company-newsletter-bounces(a)lists.company.tld>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.03, delays=0.01/0.01/0/0.01, dsn=2.0.0, status=sent (250 Ok) But the list-owner does not get any notification, nor do i see any bounce-information in the pistorious-gui. How are the bounce-mails handled? Thank you. Stefan

2 4

getting all registered users and their lists
by IOhannes m zmoelnig 27 Jan '22

27 Jan '22

hi, TL;DR is there a scriptable way to get all users that have registered in my mailman3 (3.2.1) instance and which lists they are subscribed to (if any)? longer version: we are running Mailman3-3.2.1 as shipped with Debian/buster (i know that this is not the newest version; at this point, please refrain from asking me to upgrade my Debian installation or even to switch to a venv installation of mailman3: i'll eventually do that but right now i've gt a problem to solve :-)) a few weeks ago, we invited a number of people to join a new mailinglist via a link that points to the subscription interface of the list, e.g. <https://lists.example.com/postorious/lists/foo.lists.example.com/> now of course a number of these people had problems with the webinterface, confusing the big "Subscribe" button at the bottom of the page with the much smaller "Sign Up" button in the header (in German this button reads "Registrieren" which has a meaning that is pretty similar to "Subscribe"). people that "Signed up" typically do not understand that they have not been subscribed to any mailinglist (yet), wondering why they do not get any emails. at least this is what we suspect from feedback we got. to fix the situtation, i would like to check which users had this problem (and eventually contact them to explain the problem). for this i would like to get a listing of all users that are not subscribed to any mailinglist. i would also like to query, when a given user has signed up (so i can reduce the number of false positives) how would i do that? ideally i would rather not work on an SQL level. gfdmfas IOhannes

2 3

Inline display of attachments
by Axel Rau 26 Jan '22

26 Jan '22

I have turned on HYPERKITTY_RENDER_INLINE_IMAGE and Archive Rendering mode set to Markdown text, but images in JPEG or PDF format are not displayed inline. Should this work or are my expectations to high? Thanks, Axel --- PGP-Key: CDE74120 ☀ computing @ chaos claudius

3 2

django request error
by tibor.molnar＠waltoninstitute.ie 26 Jan '22

26 Jan '22

I recently got postorius web interface stopped with an error, from web log: WARNING 2021-09-29 14:46:47,071 39320 django.request Not Found: /mailman//postorius/lists/ from website: This page either doesn't exist, or it moved somewhere else. I wonder what would be the source of this error / anyone else experienced this error since I haven't changed anything. Regards, Tibor

5 12

Held messages: Long time waiating for response of the Mailman API
by Stephan Krinetzki 25 Jan '22

25 Jan '22

Hello, We are using Mailman 3.3.5 with Hyperkitty 1.3.5. Mailman 3 is installed in a venv and deployed using Apache and uwsgi. This works quite well so far, only withheld messages cause us a problem: If we try to approve them via Postorius, the message is delivered to the list immediately, but the success message in Postorius takes a long time - on average the process hangs for three minutes until the message is no longer displayed. We have already adjusted the timeout in gunicorn.cfg, but this does not improve the situation. Are there any tips on how we can speed up the REST API? Or is it even a configuration error? Greetings Stephan

2 3

Re: Hyperkitty 403 Forbidden Error
by Josef Dietl 23 Jan '22

23 Jan '22

Dear all, Sorry for coming back to a topic that seems to be done for 18 months now. I'm staring at this issue for a few days now (on and off). But I still get these messages: Jan 19 22:43:27 2022 (149439) HyperKitty failure on https://lists.[...]/hyperkitty/api/mailman/urls: <html><title>Forbidden</title><body> <h1>Access is forbidden</h1><p>Please check the IP addresses assigned to MAILMAN_ARCHIVER_FROM in the settings file. </p></body></html> (403) . and consequently, nothing ends up in the archive. I have checked (among others): - MAILMAN_ARCHIVER_FROM - doesn't make a difference. 127.0.0.1, external IP address, different orders, '*'. (Asterisk makes a difference, see at the bottom) - MAILMAN_ARCHIVER_KEY in mailman-web.py matches api_key in mailman-hyperkitty.cfg (except for the quotes). According to the editor's color coding, the quotes are "right", too. I have removed special characters to circumvent diverging treatment in different environments - I guess it doesn't matter, but wget --user restadmin --password [.] http://localhost:8001/3.1/lists works, too. - ACCOUNT_DEFAULT_HTTP_PROTOCOL = "https" (probably also doesn't matter I'm running a fresh package installation from Debian Bullseye with certificates from Certbot with nginx, so Certbot may have messed with my nginx config, but even that seems to be OK: Yes, Certbot has inserted http->https redirection, but I'd expect that a https base_url and ACCOUNT_DEFAULT_HTTP_PROTOCOL = "https" circumvents that. Mailman info says GNU Mailman 3.3.3 (Tom Sawyer) Python 3.9.2 (default, Feb 28 2021, 17:03:44) [GCC 10.2.1 20210110] . REST root url: http://localhost:8001/3.1/ Hyperkitty is 1.3.4, Postorious is 1.3.4, too. To provide all possible information, I'm also adding the nginx log that seems to correspond to that request (no other requests at that time, give or take five minutes): Yes, everything yields 403 response codes. [.] - - [19/Jan/2022:22:43:27 +0000] "GET /hyperkitty/api/mailman/urls?mlist=demo%40lists.pro-digi-par.de&key=[.] HTTP/1.1" 403 175 "-" "python-requests/2.25.1" [.] - - [19/Jan/2022:22:43:27 +0000] "GET /hyperkitty/api/mailman/urls?mlist=demo%40lists.pro-digi-par.de&msgid=AM0PR0 4MB478573911C2A81B8898527E6C2599%40AM0PR04MB4785.eurprd04.prod.outlook.com&k ey=[.] HTTP/1.1 " 403 175 "-" "python-requests/2.25.1" [.] - - [19/Jan/2022:22:43:28 +0000] "GET /hyperkitty/api/mailman/urls?mlist=demo%40lists.pro-digi-par.de&msgid=AM0PR0 4MB478573911C2A81B8898527E6C2599%40AM0PR04MB4785.eurprd04.prod.outlook.com&k ey=[.] HTTP/1.1 " 403 175 "-" "python-requests/2.25.1" [.] - - [19/Jan/2022:22:43:28 +0000] "POST /hyperkitty/api/mailman/archive?key=[.] HTTP/1.1" 403 166 "-" "python-requests/2.25.1" [.] - - [19/Jan/2022:22:43:28 +0000] "POST /hyperkitty/api/mailman/archive?key=[.] HTTP/1.1" 403 166 "-" "python-requests/2.25.1" . repeated many times, there seems to be quite a few testmessages in the queue . [.] - - [19/Jan/2022:22:46:50 +0000] "GET /hyperkitty/api/mailman/urls?mlist=demo%40lists.pro-digi-par.de&key=[.] HTTP/1.1" 403 175 "-" "python-requests/2.25.1" [.] - - [19/Jan/2022:22:46:50 +0000] "GET /hyperkitty/api/mailman/urls?mlist=demo%40lists.pro-digi-par.de&msgid=AM0PR0 4MB4785430188B9C0E8DF248231C2599%40AM0PR04MB4785.eurprd04.prod.outlook.com&k ey=6xpENHLEHQ0kD53vXt5RpKzPDOsKbcN9 HTTP/1.1 " 403 175 "-" "python-requests/2.25.1" [.] - - [19/Jan/2022:22:46:50 +0000] "POST /hyperkitty/api/mailman/archive?key=[.] HTTP/1.1" 403 166 "-" "python-requests/2.25.1" . again repeated many times . [.] - - [19/Jan/2022:22:46:51 +0000] "GET /hyperkitty/api/mailman/urls?mlist=demo%40lists.pro-digi-par.de&msgid=AM0PR0 4MB4785430188B9C0E8DF248231C2599%40AM0PR04MB4785.eurprd04.prod.outlook.com&k ey=[.] HTTP/1.1" 403 175 "-" "python-requests/2.25.1" I'd appreciate a new idea where I could look for clues. Thanks a lot, Josef

2 3

Help needed with email deliverability to our list
by Terry Earley 23 Jan '22

23 Jan '22

We are looking to hire someone to help us with email deliverability. We are running MM3 Postorius Version 1.3.4. We are having too many bounces, causing cancellations. Our IP address is likely on one or more spam lists even though our list has never sent any spam and every post is moderated. We need help resolving all email deliverability issues. We are seeking professional help and we are willing to pay fair rates. Experts only please. Terry Earley FitEyes

1 0

Lost posting in archives
by Axel Rau 22 Jan '22

22 Jan '22

I created a list, did migration from 2.1 and run update_index_one_list. Then I posted a test mail to the list and it got distributed and was seen in the archive. Now 2 days later it does no longer show up in the archive. What is going on here? May this have to do with HYPERKITTY_RENDER_INLINE_IMAGE which I have turned on meanwhile. Clueless, Axel --- PGP-Key: CDE74120 ☀ computing @ chaos claudius

2 4

How to delete user completely?
by William Oliver 22 Jan '22

22 Jan '22

I have installed mailman3 and it's up and running great. However, I noticed that, during a mass subscribe, I mis-typed an address, e.g. name(a)domain.ned rather than name(a)domain.net. I found how to unsubscribe the bad address, but I haven't found a "delete" option under Users or anywhere else. How to I purge a user from the users list? As a related question, in docs.mailman.org, I can find a list member's manual, but I can't seem to find an admin manual. Is there one? Thanks! billo

3 3

Speed/progress of update_index_one_list?
by Philip Colmer 21 Jan '22

21 Jan '22

Yesterday, I ran "mailman-web update_index_one_list" against a mailing list. The command output "Indexing 328077 emails" and that is the last I've heard from it. The process is still running but, looking in ~mailman/web/logs, I can't see anything happening related to that list. Is there any way to determine how far this process has got, or what it is actually doing? (Without stopping it) For future indexing, what makes the most difference to the speed? Does it benefit from having multiple cores if I resize the AWS instance to a larger processor? What is the bottleneck for this process? Thank you. Regards Philip

4 7

No module named 'mailman3hyperkitty'
by Axel Rau 20 Jan '22

20 Jan '22

Still trying to setup my 1st list. mailman-hyperkitty 1.2.0 is installed. Axel PS: Backtrace 16/Jan/2022:16:43:35 +0000] "GET /3.1/lists/mailman.lists.framail.de HTTP/1.1" 200 373 "-" "GNU Mailman REST client v3.3.3" [16/Jan/2022:16:43:35 +0000] "GET /3.1/lists/mailman.lists.framail.de/roster/owner?fields=email&fields=address&fields=self_link HTTP/1.1" 200 371 "-" "GNU Mailman REST client v3.3.3" [16/Jan/2022:16:43:35 +0000] "GET /3.1/lists/mailman.lists.framail.de/roster/moderator?fields=email&fields=address&fields=self_link HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.3" [16/Jan/2022:16:43:35 +0000] "GET /3.1/lists/mailman(a)lists.framail.de/config HTTP/1.1" 200 3011 "-" "GNU Mailman REST client v3.3.3" 2022-01-16 16:43:35 [FALCON] [ERROR] GET /3.1/lists/mailman.lists.framail.de/archivers => Traceback (most recent call last): File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/falcon/app.py", line 361, in __call__ responder(req, resp, **params) File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/mailman/rest/lists.py", line 405, in on_get archiver_set = IListArchiverSet(self._mlist) File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/zope/component/_api.py", line 152, in adapter_hook return sitemanager.queryAdapter(object, interface, name, default) File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/zope/interface/registry.py", line 354, in queryAdapter return self.adapters.queryAdapter(object, interface, name, default) File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/mailman/database/transaction.py", line 85, in wrapper return function(args[0], config.db.store, *args[1:], **kws) File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/mailman/model/mailinglist.py", line 616, in __init__ for archiver in config.archivers: File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/mailman/config/config.py", line 280, in archivers archiver = call_name(class_path) File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/mailman/utilities/modules.py", line 69, in call_name named_callable = find_name(dotted_name) File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/mailman/utilities/modules.py", line 52, in find_name module = import_module(module_path) File "/usr/local/py_venv/mailman_33/lib/python3.9/importlib/__init__.py", line 127, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "<frozen importlib._bootstrap>", line 1030, in _gcd_import File "<frozen importlib._bootstrap>", line 1007, in _find_and_load File "<frozen importlib._bootstrap>", line 984, in _find_and_load_unlocked ModuleNotFoundError: No module named 'mailman3hyperkitty' --- PGP-Key: CDE74120 ☀ computing @ chaos claudius

3 6

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

One bounce, 5 bounce counts
by Henrik Rasmussen 13 Jan '22

13 Jan '22

I recently upgraded Mailman to GNU Mailman 3.3.4 (Tom Sawyer) that once again handles bounces. Thank you. In my setup, Mailman is with Maxking's Docker image maxking/mailman-core:0.3, and a Postfix outside Docker handling incoming and outgoing mails. Since the upgrade some list administrators have expectedly complained about every time they reenable subscribers, they are disabled again. I have explained to them why they are disabled and why they may be disabled again when re-disabled. My problem, though, is that some subscribers may be disabled even they are able to receive mails (confirmed with sendmail -bv), and I have been looking at one subscriber in particular. 1. Can there be (i'm not saying there are, maybe it's my lack of knowledge) somthing regarding Mailman? 2. And what would the appropeiate per list bounce settings, if not default? Actual example: * Mailman sent seemly 6 mails to a member on January 6th. * I see one bouce message D1426CE22A in Postfix log that was delivered back to Mailman * I see that Mailman is counting the bounce score from 1 to 5, one at the time, but that was day after receiving the bounce, and no other mails have been sent to the user on the 7th nor received as bounce on the 7th. I suspect that it must have been in the Postfix queue until then, but I wonder why that could be - but could be. * The bounce would be in the Postfix queue until sent to Mailman and thus removed from the Postfix queue. == /var/log/maillog == Jan 3 09:05:42 lstapp01pl postfix/smtp[10293]: EA1CC73105: to=recipient(a)example.com<mailto:heidi.ryssel@regionh.dk>, relay=rghhehspamfw001.regionh.dk[185.211.204.236]:25, delay=2.2, delays=0.14/0.03/0.1/1.9, dsn=2.0.0, status=sent (250 Ok: queued as 16A9084006E) Jan 3 11:27:35 lstapp01pl postfix/smtp[27118]: 0AD2F73117: to=recipient(a)example.com<mailto:heidi.ryssel@regionh.dk>, relay=rghhehspamfw002.regionh.dk[185.211.204.237]:25, delay=0.79, delays=0.14/0.03/0.15/0.47, dsn=2.0.0, status=sent (250 Ok: queued as C2CCDF20052) Jan 6 09:09:45 lstapp01pl postfix/smtp[2132]: EFAA673126: to=recipient(a)example.com<mailto:heidi.ryssel@regionh.dk>, relay=rghhvhspamfw002.regionh.dk[185.211.204.239]:25, delay=0.31, delays=0.09/0.01/0.07/0.14, dsn=2.0.0, status=sent (250 Ok: queued as 38094120005E) Jan 6 09:10:41 lstapp01pl postfix/smtp[2132]: 33F6373126: to=recipient(a)example.com<mailto:heidi.ryssel@regionh.dk>, relay=rghhehspamfw001.regionh.dk[185.211.204.236]:25, delay=0.35, delays=0.08/0/0.06/0.21, dsn=2.0.0, status=sent (250 Ok: queued as 86A0B840075) Jan 6 13:37:31 lstapp01pl postfix/qmgr[28946]: D1426CE22A: from=recipient(a)example.com<mailto:heidi.ryssel@regionh.dk>, size=11551, nrcpt=1 (queue active) Jan 6 14:06:43 lstapp01pl postfix/smtp[16749]: 89A68D5699: to=recipient(a)example.com<mailto:heidi.ryssel@regionh.dk>, relay=rghhvhspamfw001.regionh.dk[185.211.204.238]:25, delay=0.35, delays=0.09/0/0.07/0.2, dsn=2.0.0, status=sent (250 Ok: queued as D97EC37C0072) Jan 6 15:04:23 lstapp01pl postfix/smtp[6124]: A46527312C: to=recipient(a)example.com<mailto:heidi.ryssel@regionh.dk>, relay=rghhehspamfw002.regionh.dk[185.211.204.237]:25, delay=0.65, delays=0.12/0.03/0.03/0.48, dsn=2.0.0, status=sent (250 Ok: queued as 44ABBF2008C) == /opt/mailman/var/logs/bounce.log == Jan 07 03:36:38 2022 (25) Member recipient(a)example.com<mailto:heidi.ryssel@regionh.dk> on list listname.lists.example.com, bounce score = 1. Jan 07 03:36:56 2022 (25) Member recipient(a)example.com<mailto:heidi.ryssel@regionh.dk> already scored a bounce on list listname.lists.example.com today. Jan 07 03:37:27 2022 (25) Member recipient(a)example.com<mailto:heidi.ryssel@regionh.dk> already scored a bounce on list listname.lists.example.com today. Jan 07 03:54:04 2022 (25) Member recipient(a)example.com<mailto:heidi.ryssel@regionh.dk> already scored a bounce on list listname.lists.example.com today. Jan 07 03:58:10 2022 (25) Member recipient(a)example.com<mailto:heidi.ryssel@regionh.dk> on list listname.lists.example.com, bounce score = 2. Jan 07 04:05:04 2022 (25) Member recipient(a)example.com<mailto:heidi.ryssel@regionh.dk> already scored a bounce on list listname.lists.example.com today. Jan 07 04:25:08 2022 (25) Member recipient(a)example.com<mailto:heidi.ryssel@regionh.dk> already scored a bounce on list listname.lists.example.com today. Jan 07 04:51:22 2022 (25) Member recipient(a)example.com<mailto:heidi.ryssel@regionh.dk> on list listname.lists.example.com, bounce score = 3. Jan 07 05:04:20 2022 (25) Member recipient(a)example.com<mailto:heidi.ryssel@regionh.dk> on list listname.lists.example.com, bounce score = 4. Jan 07 05:05:22 2022 (25) Member recipient(a)example.com<mailto:heidi.ryssel@regionh.dk> already scored a bounce on list listname.lists.example.com today. Jan 07 22:55:06 2022 (25) Member recipient(a)example.com<mailto:heidi.ryssel@regionh.dk> on list listname.lists.example.com, bounce score = 5. Jan 07 22:55:06 2022 (25) Disabling delivery for recipient(a)example.com<mailto:heidi.ryssel@regionh.dk> on list listname.lists.example.com by bounce Jan 07 22:55:06 2022 (25) Member recipient(a)example.com<mailto:heidi.ryssel@regionh.dk> on list listname.lists.example.com, bounce score 5 >= threshold 5, disabling delivery. Regards, Henrik Rasmussen

2 1

Time Zone Problem In Postorius
by Brian Carpenter 13 Jan '22

13 Jan '22

I have the server TZ set to EST. I have the TZ for Postfix set to EST. I have the following set in my settings_local.py file: TIME_ZONE = 'America/New_York' USE_TZ = True However messages showing up in the pending moderation queue box shows UTC date. I am seeing this behavior in Affinity as well so I figured it is either a Mailman core setting or perhaps database? Can anyone shed light on that? Brian

5 6

Re: [Mailman-Users] Re: Member posting to a list but address not in membership list.
by Mark Sapiro 13 Jan '22

13 Jan '22

On 1/12/22 7:42 PM, Adam Morris wrote: > Hi Mark, > I've looked in all these places and the address isn't anywhere. (please keep the thread on the list) Then the address that's posting isn't what you think it is or something in your installation is broken. As I said, it could be that Reply-To: or Sender: is the list member, but depending on list settings, these things get overwritten in mail from the list, so you can't really know. If something is broken, you need to discuss this with your hosting provider who, unfortunately, may be no help. Many, not all, cPanel hosts offer mailman because it comes with cPanel, but actually know nothing about Mailman. See https://wiki.list.org/DOC/Mailman%20and%20CPanel > On 13-January-2022 11:31, Mark Sapiro wrote: >> On 1/11/22 7:51 PM, Adam Morris wrote: >>> I have someone who is posting to a list I run. >>> I subscribed them originally but their address doesn't show up in the >>> list of members so I can't change moderation status etc. >>> Where else could I look to find their address? >> >> >> The first check on a post is if any of the address in From:, Reply-To: >> or Sender: headers or the envelope sender is a list member, i.e. in >> the web admin Membership List. If so, that member's moderation is >> applied. If not, the next check is if the From:the *_these_nonmembers >> lists under Privacy options... -> Sender filters and finally Privacy >> options... -> Sender filters -> generic_nonmember_action. >> >> If a post to the list is being accepted without being held for >> moderation, either some address in From:, Reply-To: or Sender: headers >> or the envelope sender is in the Membership List with `mod` unchecked, >> or the From: or possibly Sender: address is in accept_these_nonmembers >> or generic_nonmember_action is Accept. >> > > -- > > Adam Morris > Mobile: 0414 431105 > Email, iMessage & FaceTime > adam(a)damorris.com > -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 0

Issues with international characters (replaced by ?) when mail is send as text/html
by Michal Soltys 12 Jan '22

12 Jan '22

Hi, I have noticed that any mail send with text/html, e.g. with following headers: Content-Language: en-US-large Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit is slightly transformed by mailman3 - the body is put into its own part, but all the international letters are replaced by question marks. Having searched the list I tried: 1) adding following to mailman.cfg: [language.master] description: English (USA) charset: utf-8 enabled: yes [language.en] description: English (USA) utf8 charset: utf-8 enabled: yes 2) changing preferred language of a mailing list to something else via shell, e.g.: m.preferred_language = 'pl' 3) changed default_language to 'pl' in mailman.cfg 4) Ensured all relevant glibc locales are generated (not sure if that matters though in this case) None of this seems to have any positive result - all mails, whether under 'pl' or 'en' setting still get all non-ascii chars replaced with question marks (in html case, probably(?) in any case where it becomes multipart). Any ideas what to do so html mails are passed without filtering out their characters ? Do I have to recreate all mailing lists under new [language.en/master] settings ?

2 5

Mailman3 is wrongly display name a list member
by Allan Hansen 11 Jan '22

11 Jan '22

All, I got an issue with one subscriber (multiple lists). When I subscribe 'A' <a(a)foo.com>, Mailman3 changes it to 'B' <a(a)foo.com>. I went into Django and added the name 'B' to the subscriber's account (the name was empty). I then unsubscribed <a(a)foo.com> from the lists and resubscribed 'A' <a(a)foo.com>. The subscription again lists as 'B' <a(a)foo.com>. This brings up a previous discussion of display names on this list, but I have not been able to find any solution to the need to change Mailman3's display names for a subscriber. It is beyond weird that unsubscribing, setting the account display name and resubscribing the member fishes back up the old and wrong display name. What can I do to help this member? Yours, Allan

3 5

Howto: Mass import of nonmembers in several lists?
by Paul Paulchen 11 Jan '22

11 Jan '22

Hi MM3 community, got a, perhaps easy question. Following situation, got 8 lists and up to 20 nonmember users missing to the list. The massimport with postorius is only for members, as far as I can use it (Postorius Version 1.3.4). So without adding all nonmembers with postorius step by step 8x20 times, there is an easier way to do it. I thought so, because the import21 command did this as well when we migrated to mailman3. I read about the command "mailman addmembers" https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/d… I am guessing, that I need to create a file like in the example of the addmembers, adding all my nonmember users with their email addy. But how can I add/ tell the command in this massimport that the new members are nonmembers in the existing lists?! Hope I explained my case properly. I appreciate your responds! Thanks in advance. - Paul

2 2

Newbie hyperkitty question
by Stephen Daniel 11 Jan '22

11 Jan '22

Mailman users -- I am setting up a new mailman3 installation, and this is my first experience with the suite. All of the software is up and running, but I cannot tell if hyperkitty is actually running. When I look at my test mailing list, two archive options are available, hyperkitty and "prototype", and both are enabled. I can see that my email is being archived, but I think "prototype" is what is doing the archiving. I see that a test message will end up in /opt/mailman/mm/var/archives/prototype/<LISTNAME>@<LISTDOMAIN.org>/new/164.... and nowhere else. This suggests that "prototype" is archiving, but hyperkitty is not. So, this opens up a raft of questions on hyperkitty: - How do I tell if hyperkitty is actually running? - Does hyperkitty have a web-UI for admins or users? How would I access it? - I can not find any documentation on hyperkitty, other than installation instructions and change logs. Does documentation exist? - How do I set policies on how long archives are kept? - Assuming I want to back up my archives, what do I need to back up? Thanks for your help! -- Stephen Daniel

3 5

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

Re-enable member after bouce processed disable
by Henrik Rasmussen 05 Jan '22

05 Jan '22

Recently I upgraded Mailman to GNU Mailman 3.3.4 (Tom Sawyer) (Postorius: 1.3.5 and HyperKitty: 1.3.4) which is now processing bounces. When a member have been disabled due to bounces, how is the member re-enabled? I would guess it would be under the "Users -> Members -> Member options -> Delivery status", but theses are both (Enabled and disabled) unchecked, not indicating whether or not the member is either or. How do I or the list admins re-enable a bounce-disabled member? Regards, Henrik

2 3

Healthchecks and Django
by Philip Colmer 05 Jan '22

05 Jan '22

Hello We have a number of Mailman 3 servers running on AWS infrastructure. To help us maintain that, we're using Route 53 Health Checks to alert us when something stops responding. For the MM3 servers, we're probing "/mailman3/lists/". We've observed that when a server gets patched during a maintenance window, it will get rebooted and there is a phase where Django responds to web queries but the underlying MM3 services aren't quite in place yet. As a result, we then get emails from Django telling us about the service not being available. Given the number of AWS health checkers, that can result in quite a few emails ... Is there another URL we could use to check the health of a MM3 server without triggering the emails during service startup? Or, if not, is there a way of stopping Django from sending out the emails? We'd get alerted of a problem via AWS anyway, so I'm not too worried about not receiving the Django emails. Thank you. Philip

2 5

If you delete a list but not the HyperKitty archive
by Philip Colmer 05 Jan '22

05 Jan '22

It seems that if you delete a list from the "Delete" option on a list's management page, the corresponding HyperKitty archive does not get deleted. That seems fair enough ... but now I wondering how HyperKitty manages visibility access to the archive when the list was private. HyperKitty certainly *seems* to have some knowledge of who was subscribed to a list as attempting to access a private archive with an account that wasn't subscribed prior to the list being deleted does deny access with "This mailing list is private. You must be subscribed to view the archives." But logging in as the server admin, going to the archive URL and then clicking on "Manage subscription" gives me a "Page not found" error ... which isn't too surprising as the list has been deleted. It suggests, though, that it isn't possible to manage access to the *archive* after the list has been removed. So ... should the archive be deleted when the list is deleted and it is a bug that it isn't? Or is it expected that access to the archive is "frozen" once a list is deleted? Many thanks. Philip

2 2

is there a mailman command/setting to periodically clean archives?
by William Oliver 04 Jan '22

04 Jan '22

Thanks to everyone's help, mailman3 is up and running for me on two servers with three lists, and they all work as far as I can see. I'm sending out invitations to users tomorrow. Yayy. Up until today, I had been stuck using a plugin in Joomla, which was not the best solution. I'm tickled pink, and my users will be, too. Now I'm just playing and tinkering a bit. I'd like to delete all my archives that are more than a certain age, e.g. more than a week old. I can easily do that with a cron job, deleting old files in /opt/mailman/mm/var/archives/prototype/testlist(a)example.com/* which is, as far as I can see the only place archive emails live. However... I was wondering if there was some mailman command or config variable that would accomplish this without using cron. billo

3 4

Strange behaviour when SSL (https) is activated
by fr-mm3＠tourde.org 04 Jan '22

04 Jan '22

Hi, I do a fresh install of Mailman3 and Mailman3-web on Debian 11 and all seems working fine using non-ssl access. But if I activate SSL on the web server, I'm unable to login. I go to the /admin, prompted for the user/pass, and got a Firefox error page saying "Échec de la connexion sécurisée". Main django account was created with: mailman-web createsuperuser --username XXXX --email xxxx(a)xxxx.xx extract of /var/log/mailman3/web/mailman-web.log : [pid: 103142|app: 0|req: 40/40] 192.168.200.252 () {48 vars in 1039 bytes} [Mon Jan 3 11:26:32 2022] GET /accounts/login/ => generated 9321 bytes in 37 msecs (HTTP/1.1 200) 7 headers in 429 bytes (1 switches on core 0) Mon Jan 3 11:26:40 2022 - uwsgi_response_write_headers_do(): Broken pipe [core/writer.c line 248] during POST /accounts/login/ (192.168.200.252) OSError: write error [pid: 103142|app: 0|req: 41/41] 192.168.200.252 () {54 vars in 1008 bytes} [Mon Jan 3 11:26:40 2022] POST /accounts/login/ => generated 0 bytes in 704 msecs (HTTP/1.1 302) 9 headers in 0 bytes (1 switches on core 1) All is working fine on non-ssl connection. Any hint appreciated ;)

3 5

Held for notification - runner exception: 'ascii' codec can't encode character
by Seth Seeger 03 Jan '22

03 Jan '22

Hello all, Happy new year! I have a case where a user (set to be moderated), posts a message. She got the appropriate email back saying she was being held for moderation. However, the moderator did not get the email. I found the following block in mailman.log: Dec 28 19:37:44 2021 (33) Uncaught runner exception: 'ascii' codec can't encode character '\u2019' in position 5: ordinal not in range(128) Dec 28 19:37:44 2021 (33) Traceback (most recent call last): File "/usr/lib/python3.8/site-packages/mailman/core/runner.py", line 173, in _one_iteration self._process_one_file(msg, msgdata) File "/usr/lib/python3.8/site-packages/mailman/core/runner.py", line 266, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/lib/python3.8/site-packages/mailman/runners/incoming.py", line 79, in _dispose process(mlist, msg, msgdata, start_chain) File "/usr/lib/python3.8/site-packages/mailman/core/chains.py", line 79, in process link.function(mlist, msg, msgdata) File "/usr/lib/python3.8/site-packages/mailman/chains/hold.py", line 234, in _process text = MIMEText(expand(template, mlist, substitutions), File "/usr/lib/python3.8/email/mime/text.py", line 42, in __init__ self.set_payload(_text, _charset) File "/usr/lib/python3.8/email/message.py", line 315, in set_payload payload = payload.encode(charset.output_charset) UnicodeEncodeError: 'ascii' codec can't encode character '\u2019' in position 5: ordinal not in range(128) Dec 28 19:37:44 2021 (33) SHUNTING: 1640720264.0541506+b139f885caa9444586b43093a09991b7c19581e6 There are two owners listed, one of them is also listed as the moderator. "mailman version" says: GNU Mailman 3.3.4 (Tom Sawyer) We are running from Docker. I can send you the pck file offline if that would help. Thank you, Seth

2 4

HyperKitty failure
by horvath.arpad.szfvar＠gmail.com 02 Jan '22

02 Jan '22

Hi, I try to connect mailman3 to hyperkitty, but there is no success so far. You can see the details below. How can I solve the problem? As I have several domain name (like lists.xxx.hu, xxx.hu, yyy.hu) on the same server, so I guess localhost won't work. In mailman-hyperkitty.cfg there is a line: base_url: http://lists.xxx.hu/hyperkitty/ /etc/mailman3/mailman-web.py includes "*" in ALLOWED_HOSTS I have an error message in /var/log/mailman3/mailman.log Dec 30 21:41:23 2021 (126976) HyperKitty failure on http://lists.xxx.hu/hyperkitty/api/mailman/archive: (405) Dec 30 21:41:23 2021 (126976) Exception in the HyperKitty archiver: Dec 30 21:41:23 2021 (126976) Traceback (most recent call last): File "/usr/lib/python3/dist-packages/mailman_hyperkitty/__init__.py", line 154, in _archive_message url = self._send_message(mlist, msg) File "/usr/lib/python3/dist-packages/mailman_hyperkitty/__init__.py", line 210, in _send_message raise ValueError(result.text) ValueError In /var/log/mailman3/web/mailman-web.log WARNING 2021-12-30 20:41:23,816 127032 django.request Method Not Allowed (GET): /hyperkitty/api/mailman/archive [pid: 127032|app: 0|req: 101/101] 109.230.236.204 () {38 vars in 592 bytes} [Thu Dec 30 20:41:23 2021] GET /hyperkitty/api/mailman/archive?key=lHzJB%2FzfSWUrbPKZ84JNSlLXHVyCDt8T => generated 0 bytes in 1 msecs (HTTP/1.1 405) 6 headers in 189 bytes (1 switches on core 0) WARNING 2021-12-30 20:41:23,854 127032 django.request Method Not Allowed (GET): /hyperkitty/api/mailman/archive On Debian 11, I have these packages ii mailman3 3.3.3-1 all Mailing list management system ii mailman3-full 3.3.3-1 all Full Mailman3 mailing list management suite (metapackage) ii mailman3-web 0+20200530-2 all Django project integrating Mailman3 Postorius and HyperKitty ii python3-django-mailman3 1.3.5-2 all Django library to help interaction with Mailman3 (Python 3 version) ii python3-mailman-hyperkitty 1.1.0-10 all Mailman3 plugin to archive emails with HyperKitty Thanks, Arpad

3 8

signup / registration error - permissions and cert chains
by David Newman 01 Jan '22

01 Jan '22

I'd like for regular (non-admin) list subscribers to be able to manage their subscription preferences and view list archives. However, when new users attempt to create logins from the Postorius "Sign Up" page, the server returns the error pasted below, and displays a "server error" page to users. If I'm reading the error correctly, this is related to an inability to verify the cert chain. The /etc/mailman3/settings.py file points to the same cert and key files used by Nginx, Postfix, and Dovecot. Since TLS works OK with these other services, it appears the cert and key are valid. (Viewing the cert in a web browser also supports this.) The keyfile has 0400 permissions. I tried changing this to 0640 and making the keyfile owned by root:mailman. Even after restarting mailman3 and mailmanweb the same error occurs. (Permissions in the cert and key directories and above are not blocking access.) The etc/mailman3/settings.py file includes these settings: EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' EMAIL_HOST = 'localhost' EMAIL_PORT = 25 EMAIL_HOST_USER = 'dnewman(a)networktest.com' EMAIL_HOST_PASSWORD = 'wouldnt-you-like-to-know' EMAIL_USE_TLS = 'True' EMAIL_SSL_CERTFILE = '/etc/ssl/certs/myhost.crt' EMAIL_SSL_KEYFILE = '/etc/ssl/private/myhost.key' But this might only be for email, not Postorius/Django. I checked the Mailman Web docs and settings reference but didn't see anything relevant on either page. https://docs.mailman3.org/en/latest/config-web.html https://docs.mailman3.org/projects/mailman-web/en/latest/settings.html What additional configuration is needed to allow regular users to create and manage their own accounts? Thanks. dn ERROR 2021-12-30 16:03:53,787 436935 django.request Internal Server Error: /accounts/signup/ Traceback (most recent call last): File "/opt/mailman/venv/lib/python3.9/site-packages/django/core/handlers/exception.py", line 34, in inner response = get_response(request) File "/opt/mailman/venv/lib/python3.9/site-packages/django/core/handlers/base.py", line 115, in _get_response response = self.process_exception_by_middleware(e, request) File "/opt/mailman/venv/lib/python3.9/site-packages/django/core/handlers/base.py", line 113, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/opt/mailman/venv/lib/python3.9/site-packages/django/views/generic/base.py", line 71, in view return self.dispatch(request, *args, **kwargs) File "/opt/mailman/venv/lib/python3.9/site-packages/django/utils/decorators.py", line 43, in _wrapper return bound_method(*args, **kwargs) File "/opt/mailman/venv/lib/python3.9/site-packages/django/views/decorators/debug.py", line 76, in sensitive_post_parameters_wrapper return view(request, *args, **kwargs) File "/opt/mailman/venv/lib/python3.9/site-packages/allauth/account/views.py", line 230, in dispatch return super(SignupView, self).dispatch(request, *args, **kwargs) File "/opt/mailman/venv/lib/python3.9/site-packages/allauth/account/views.py", line 74, in dispatch response = super(RedirectAuthenticatedUserMixin, self).dispatch( File "/opt/mailman/venv/lib/python3.9/site-packages/allauth/account/views.py", line 204, in dispatch return super(CloseableSignupMixin, self).dispatch(request, *args, **kwargs) File "/opt/mailman/venv/lib/python3.9/site-packages/django/views/generic/base.py", line 97, in dispatch return handler(request, *args, **kwargs) File "/opt/mailman/venv/lib/python3.9/site-packages/allauth/account/views.py", line 102, in post response = self.form_valid(form) File "/opt/mailman/venv/lib/python3.9/site-packages/allauth/account/views.py", line 248, in form_valid return complete_signup( File "/opt/mailman/venv/lib/python3.9/site-packages/allauth/account/utils.py", line 209, in complete_signup return perform_login( File "/opt/mailman/venv/lib/python3.9/site-packages/allauth/account/utils.py", line 175, in perform_login send_email_confirmation(request, user, signup=signup, email=email) File "/opt/mailman/venv/lib/python3.9/site-packages/allauth/account/utils.py", line 346, in send_email_confirmation email_address.send_confirmation(request, signup=signup) File "/opt/mailman/venv/lib/python3.9/site-packages/allauth/account/models.py", line 62, in send_confirmation confirmation.send(request, signup=signup) File "/opt/mailman/venv/lib/python3.9/site-packages/allauth/account/models.py", line 169, in send get_adapter(request).send_confirmation_mail(request, self, signup) File "/opt/mailman/venv/lib/python3.9/site-packages/allauth/account/adapter.py", line 464, in send_confirmation_mail self.send_mail(email_template, emailconfirmation.email_address.email, ctx) File "/opt/mailman/venv/lib/python3.9/site-packages/allauth/account/adapter.py", line 136, in send_mail msg.send() File "/opt/mailman/venv/lib/python3.9/site-packages/django/core/mail/message.py", line 284, in send return self.get_connection(fail_silently).send_messages([self]) File "/opt/mailman/venv/lib/python3.9/site-packages/django/core/mail/backends/smtp.py", line 102, in send_messages new_conn_created = self.open() File "/opt/mailman/venv/lib/python3.9/site-packages/django/core/mail/backends/smtp.py", line 67, in open self.connection.starttls(keyfile=self.ssl_keyfile, certfile=self.ssl_certfile) File "/usr/lib/python3.9/smtplib.py", line 772, in starttls context = ssl._create_stdlib_context(certfile=certfile, File "/usr/lib/python3.9/ssl.py", line 787, in _create_unverified_context context.load_cert_chain(certfile, keyfile) PermissionError: [Errno 13] Permission denied

3 6

multiple sites on a mailman3 server question
by William Oliver 29 Dec '21

29 Dec '21

So, I have successfully installed mailman3 and it's working great. However, the way it works now, if someone goes to the domain website, he or she will get the mailman page. I'd prefer that it work something like: My www.example.com goes to a home page lists.example.com goes to the mailman3 page mail.example.com goes to a roundcube page I'm using nginx, and this is the first time I've set up an nginx server (I have traditionally done apache), and I'm still figuring out the syntax. My sites-available file is below, for the domain emergenus.com. The behavior I'm getting is that if I go to mail.emergenus.com, it still redirects to mail.emergenus.com/mailman3/lists, but gives a 404 page not found. If I go to lists.emergenus.com, it redirects to lists.emergenus.com/mailman3/lists and gives the nice postorius page, and works fine. So, I'm trying to figure out how to stop that redirect. When I look at my nginx access.log file for mail.emergenus.com, I see: 174.212.104.153 - - [28/Dec/2021:21:03:21 -0500] "GET /mailman3/lists/ HTTP/1.1" 404 188 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4664.93 Safari/537.36" Aha! says I. My ip address is 203.159.80.234, not 174.212.104.153. Thus, uwsgi (I think) is sneaking in there and taking over regardless of what I'm trying to do. Is there a way to tell mailman to only take over for lists.emergenus.com and not for www.emergenus.com or mail.emergenus.com? Here's my uwsgi.ini (without then env= PYTHONPATH change discussed in another thread: # /etc/mailman3/uwsgi.ini # [uwsgi] # Port on which uwsgi will be listening. http-socket = 0.0.0.0:8000 # If running uwsgi from the virtual environment ... virtualenv = /opt/mailman/venv/ module=mailman_web.wsgi:application # Add to python import path. pythonpath = /etc/mailman3/ # The default settings module. env = DJANGO_SETTINGS_MODULE=settings # Setup default number of processes and threads per process. master = true processes = 2 threads = 2 # Setup the django_q related worker processes. attach-daemon = /opt/mailman/venv/bin/mailman-web qcluster # Setup the request log. req-logger = file:/opt/mailman/web/logs/uwsgi.log # Log qcluster commands separately. logger = qcluster file:/opt/mailman/web/logs/uwsgi-qcluster.log log-route = qcluster uwsgi-daemons # Last log and it logs the rest of the stuff. logger = file:/opt/mailman/web/logs/uwsgi-error.log Here's my /etc/nginx/sites-enabled/emergenus.com looks like: server { root /var/www/html2; index index.html index.htm index.nginx-debian.html; server_name emergenus.com, mail.emergenus.com, www.emergenus.com; location /{ try_files $uri $uri/ =404; } ##### added 12/19 listen 443 ssl default_server; listen [::]:443 ssl default_server; ########## ssl_certificate /etc/letsencrypt/live/emergenus.com/fullchain.pem; # managed by Certbot ssl_certificate_key /etc/letsencrypt/live/emergenus.com/privkey.pem; # managed by Certbot include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot } server { root /var/www/html; index index.html index.htm index.nginx-debian.html; server_name lists.emergenus.com; location /{ proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; # proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Host $host; proxy_set_header X-Forwarded-Server $host; proxy_set_header X-Forwarded-Proto $scheme; proxy_redirect off; } listen 443 ssl ; listen [::]:443 ssl ; location /static/ { alias /opt/mailman/web/static/; } ########## ssl_certificate /etc/letsencrypt/live/emergenus.com/fullchain.pem; # managed by Certbot ssl_certificate_key /etc/letsencrypt/live/emergenus.com/privkey.pem; # managed by Certbot include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot } server { if ($host = mail.emergenus.com) { # return 301 https://$host$request_uri; return 301 https://mail.emergenus.com; } # managed by Certbot if ($host = www.emergenus.com) { return 301 https://$host$request_uri; } # managed by Certbot if ($host = lists.emergenus.com) { return 301 https://$host$request_uri; } # managed by Certbot listen 80 ; listen [::]:80 ; server_name www.emergenus.com lists.emergenus.com mail.emergenus.com emergenus.com; return 404; # managed by Certbot } Thanks billo

3 6

Question about lists and domains on Mailman 3
by Philip Colmer 29 Dec '21

29 Dec '21

I've got a single server hosting multiple domains. I've got Apache working as the proxy in front of MM3. Regardless of whether I go to https://lists.domainA.org/mailman3/lists/ or https://lists.domainB.org/mailman3/lists/, Postorius lists ALL of the lists across both domains. Is there a way of configuring the system so that, if a user goes to "domain A", only the lists for that domain are listed? Thanks. Philip

2 2