- Mailman-users - lists.mailman3.org

Change digest frequency and default threshold
by Henrik Rasmussen 12 Oct '18

12 Oct '18

When creating a new list in Mailman 3, the Digest Size Threshold is set to 30KB, which is not much in my opnion. 1) How do I set another default for Digest Size Threshold for new lists. 2) How do I change the default for existing lists When Digest Size Threshold is not reached, mails seems to be sent according to digest_volume_frequency': which is set to 'monthly'. The web interface doesn't seem to have a setting for this. How do I change this setting, both on a single list and the default for new lists? Henrik Rasmussen

2 9

Can't remove footer(s)
by Henrik Rasmussen 11 Oct '18

11 Oct '18

I have a problem removing the footer(s) from a list imported from MM2.1. I have been testing by entering my message in Hyperkitty (the list forum). I an aware about the double footer issue[1], and I am aware that footers are cached, but I have removed the footer files according to [2], run Mailman shell according to [3], restarted the Mailman (Mailman core, Mailan web, Postgres database and postfix). Did I miss something in order to remove the footers? [1] https://gitlab.com/mailman/mailman/issues/407 [2] https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… [3] https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… I'm running Docker-Mailman (Mailman version 3.2.0a1). -- Henrik Rasmussen

2 5

Archiving error
by Enrique Terrazas 05 Oct '18

05 Oct '18

Hello, I'm hoping someone can help me configure hyperkitty correctly. I've got mailman3 installed and working. I created a test list and can send/receive, moderate message. However, archiving does not seem to be working. Below is a copy of my (sanitized) hyperkitty.cfg file and settings.py file(edited) along with the errors being logged to mailman.log hyperkitty.cfg ----- # Mailman-Hyperkitty Archiver plugin [general] base_url: http://localhost:8002/ api_key: ----- settings.py # Mailman API credentials MAILMAN_REST_API_URL = 'http://localhost:8001' MAILMAN_REST_API_USER = '' MAILMAN_REST_API_PASS = '' MAILMAN_ARCHIVER_KEY = '' MAILMAN_ARCHIVER_FROM = ('my.host.name', 'myIPaddress', '127.0.0.1', '::1') ------ This is the error being sent to maillog.log ------ Oct 05 01:54:59 2018 (15127) Exception in "hyperkitty" archiver Traceback (most recent call last): File "/opt/mailman/mailman/lib64/python3.6/site-packages/urllib3/connection.py", line 171, in _new_ conn (self._dns_host, self.port), self.timeout, **extra_kw) File "/opt/mailman/mailman/lib64/python3.6/site-packages/urllib3/util/connection.py", line 79, in c reate_connection raise err File "/opt/mailman/mailman/lib64/python3.6/site-packages/urllib3/util/connection.py", line 69, in c reate_connection sock.connect(sa) ConnectionRefusedError: [Errno 111] Connection refused During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/opt/mailman/mailman/lib64/python3.6/site-packages/urllib3/connectionpool.py", line 600, in urlopen chunked=chunked) File "/opt/mailman/mailman/lib64/python3.6/site-packages/urllib3/connectionpool.py", line 354, in _make_request conn.request(method, url, **httplib_request_kw) File "/opt/rh/rh-python36/root/usr/lib64/python3.6/http/client.py", line 1239, in request self._send_request(method, url, body, headers, encode_chunked) File "/opt/rh/rh-python36/root/usr/lib64/python3.6/http/client.py", line 1285, in _send_request self.endheaders(body, encode_chunked=encode_chunked) File "/opt/rh/rh-python36/root/usr/lib64/python3.6/http/client.py", line 1234, in endheaders self._send_output(message_body, encode_chunked=encode_chunked) File "/opt/rh/rh-python36/root/usr/lib64/python3.6/http/client.py", line 1026, in _send_output self.send(msg) File "/opt/rh/rh-python36/root/usr/lib64/python3.6/http/client.py", line 964, in send self.connect() File "/opt/mailman/mailman/lib64/python3.6/site-packages/urllib3/connection.py", line 196, in connect conn = self._new_conn() File "/opt/mailman/mailman/lib64/python3.6/site-packages/urllib3/connection.py", line 180, in _new_conn self, "Failed to establish a new connection: %s" % e) urllib3.exceptions.NewConnectionError: <urllib3.connection.HTTPConnection object at 0x7f0ba1c22048>: Failed to establish a new connection: [Errno 111] Connection refused During handling of the above exception, another exception occurred: ------ Thanks in advance, Enrique J. Terrazas

3 5

Hyperkitty 1.1.1 to HyperKitty 1.2.1
by Thomas G 05 Oct '18

05 Oct '18

Hi, I would like to migrate my current Mailman3.1/Hyperkitty data to a fresh install in Mailman3.2. I didn't found how migrate the archives. From : HyperKitty - Version: 1.1.1 - Python2.7 To : HyperKitty - Version: 1.2.1 - Python3.5 I exported a mbox from hyperkitty (web interface) and tried to re-import it, without result. """""""""""""""""""""""""""""""""""""""" xxxx @xxxxxx :/opt/mailman# python3.5 manage.py hyperkitty_import -l listedetests(a)hatlab.fr /home/admin/listedetests(a)hatlab.fr.mbox.gz Importing from mbox file /home/admin/listedetests(a)hatlab.fr.mbox.gz to listedetests(a)hatlab.fr Computing thread structure Synchronizing properties with Mailman Warming up cache The full-text search index is not updated for this list. It will not be updated by the 'minutely' incremental update job. To update the index for this list, run the 'manage.py update_index_one_list listedetests(a)hatlab.fr' command. """""""""""""""""""""""""""""""""""""" The database stay empty (and web interface): """""""""""""""""""""""""""""""""""""" mailmandbnameprod=# select * from hyperkitty_email; id | message_id | message_id_hash | subject | content | date | timezone | in_reply_to | archived_date | thread_depth | thread_order | mailinglist_id | parent_id | sender_id | thread_id | sender_name ----+------------+-----------------+---------+---------+------+----------+-------------+---------------+--------------+--------------+----------------+-----------+-----------+-----------+------------- (0 rows) """""""""""""""""""""""""""""""""""""" Any idea to do this importation ? Thanks !

3 7

Proper permissions for mailman installation under home directory, with layout: local
by Eric Abrahamsen 03 Oct '18

03 Oct '18

I recently upgraded my server from Ubuntu 16.04 to 18.04, and have hit some snags in the process. I've had my mailman3 installation under my home directory, running as my own user, without too many problems. var_dir was set to something in my home directory. Recently, while tracking down some weird behavior, I realized that with this sort of setup I'm supposed to use "layout: local", and that previously I'd had a sort of weird half-way installation where some things were kept in my /home/<me>/sites/mailman directory, and other bits (pids and whatnot) were scattered around the filesystem. Now that I'm using "layout: local", mailman really is trying to keep everything under that main directory, and now everything's breaking. The hyperkitty search indexer is saying it has no permissions to write into that directory, postfix won't deliver mail, saying the mailbox is unavailable, and in the web UI postorius shows no configured list domains (though hyperkitty still displays the archives correctly). So obviously I've got quite a big problem with permissions, but I don't know how to resolve it. My webserver is nginx, running as www-data. I'm starting mailman in a systemd script, with User and Group set to my user -- though maybe that should be set to root? I guess postfix runs as root, I'm not sure, but obviously it's not able to read the files in var/data/*, which appear all correct to me. What's the recommended solution here? I'd still like to keep this whole directory under my home directory, if possible... Thanks, Eric

1 0

About the link destination of the logo image of the homepage
by Ooyama Yosiyuki 01 Oct '18

01 Oct '18

At next page: https://www.gnu.org/software/mailman/ Despite the fact that "Mailman" is written in the logo on the upper left of the screen, However if I click the logo image on the upper left of the screen,then it is to move to https://www.gnu.org/software/ I think it is strange. In the Wikipedia English version, the following address is introduced as mailman's website. www.gnu.org/software/mailman/

3 2

Hyperkitty splitting threads?
by Marvin Gülker 30 Sep '18

30 Sep '18

Hi, I'm experiencing a problem with regard to how Hyperkitty decides how to group messages into a thread. It appearently randomly splits a thread and creates a new one from the replies, even though the replies have the proper In-Reply-To: header set. As of now, the front page for our mailing list[1] illustrates the issue nicely: the "TSC Boost Build Issues" topic has been split over three threads for no appearent reason, and the "Providing an APT repository" one in two. Sometimes replies are collected into the proper thread, though (see the latter thread). Exact links follow as the front page can change later on: * The "Boost Build Issues" topic (these should all be in one thread page): * https://lists.secretchronicles.org/hyperkitty/list/tsc-devel@lists.secretch… * https://lists.secretchronicles.org/hyperkitty/list/tsc-devel@lists.secretch… * https://lists.secretchronicles.org/hyperkitty/list/tsc-devel@lists.secretch… * The "APT repository" topic (these should all be in one thread page as well): * https://lists.secretchronicles.org/hyperkitty/list/tsc-devel@lists.secretch… * https://lists.secretchronicles.org/hyperkitty/list/tsc-devel@lists.secretch… This is Mailman 3.2.0 with Hyperkitty 1.2.0. We will shortly upgrade Hyperkitty to the current version, but since I didn't find something related in the release notes for newer versions, I thought I'd ask here if the problem is known. Also, is there a way to rebuild the thread structure so that the existing errorneous splits can be corrected? Marvin [1]: https://lists.secretchronicles.org/hyperkitty/list/tsc-devel@lists.secretch… -- Blog: https://mg.guelker.eu PGP/GPG ID: F1D8799FBCC8BC4F

2 2

Docker-mailman: Performance issue
by Henrik Rasmussen 28 Sep '18

28 Sep '18

I am using Docker-mailman (currently Mailman version 3.2.0a1). I have a list with 38513 subscribers and when I operate on a very large number of them (for example click Unsubscribe all), the web interface times out. The same happens if I use the REST API, one member at the time, but run from a python script i've made). The Docker containers for both Mailman core (mostly) and mailman web (sometimes) are using 100% CPU (quart of the server's amount of CPUs). By doubleing the CPU shares that the two docker containers can use (using RHEL Cockpit) from 1024 to 2048 for each, Mailman-core had a max usage of 190% and Mailman-web about 101%. Still, mass unsubscribing the members by clicking Unsubscribe all made theinterface time out. Using the REST API succeeded unsubscribing all, but still made the Mailman web interface inaccessible. How can I make Docker-mailman perform better, to avoid these timeouts. -- Henrik Rasmussen University of Copenhagen

2 2

Where is the site to translate HyperKitty?
by Ooyama Yosiyuki 27 Sep '18

27 Sep '18

Where can I translate HyperKitty(GNU Mailman v3)? please tell me.

3 3

Dump/restore users (with passwords) via API
by Dmitry Makovey 26 Sep '18

26 Sep '18

We are trying to dump/restore users using API calls and it seems that API allows us to dump password hashes (a good thing), but then API does not allow to insert users back using saved password hashes - only cleartext passwords. Aside from create_user is there any other way to create users/change their password? -- Sr System and DevOps Engineer SoM IRT

4 9