January 2022 - Mailman-users - lists.mailman3.org

Request for help with configuring "from" headers in mailman3 list
by Stephen Daniel Jan. 6, 2022

Jan. 6, 2022

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 Jan. 6, 2022

Jan. 6, 2022

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 Jan. 6, 2022

Jan. 6, 2022

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) Jan. 6, 2022

Jan. 6, 2022

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 Jan. 5, 2022

Jan. 5, 2022

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 Jan. 5, 2022

Jan. 5, 2022

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 Jan. 5, 2022

Jan. 5, 2022

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 Jan. 4, 2022

Jan. 4, 2022

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 Jan. 4, 2022

Jan. 4, 2022

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 Jan. 3, 2022

Jan. 3, 2022

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