- Mailman-users - lists.mailman3.org

List notices in French, but subject in English
by Mark Dale 12 Apr '23

12 Apr '23

Hi, I have a list set with it's preferred language set as French and the body of the standard notification emails (eg. Welcome message) is correctly sent in French, however the subject of the emails is in English. Can the list be configured so the subject is also in French, or is this an issue with gettext .mo files somewhere? This is on Debian package Mailman 3.3.3 Thanks, Mark

2 2

An archive/read-only list on a full setup?
by Andreas Schamanek 11 Apr '23

11 Apr '23

I have a working full installation of mailman3, postorius and hyperkitty (on Debian 11). Now I wanted to host the archive of a remote list, and I am wondering how to do this properly. After I found no documentation and no posting I simply created a list in mailman3 with only 1 dummy member. The list address is subscribed to the actual remote list. So, messages arrive and are archived. But that's not optimal because hyperkitty thinks it's a normal list where it should be read-only and do not allow subscriptions etc. What's the proper way to set up a hyperkitty-only list? -- -- Andreas :-)

2 2

Change base mailman URL path
by chad.hays86＠gmail.com 08 Apr '23

08 Apr '23

Hi, I recently completed the a Mailman3 install using these[1] instructions. I'm able to access the web interface, the Django admin app, etc off the root domain URL. For example: https://mydomain.org/mailman3, https://mydomain.org/admin, https://mydomain.org/archives What's the most straightforward way to put all of these URL paths behind a different context? For example: https://mydomain.org/lists/mailman3, https://mydomain.org/lists/admin, https://mydomain.org/lists/archives I'm running Apache2 as my web server and am using mod_proxy to proxy requests to uwsgi. [1] https://docs.mailman3.org/en/latest/install/virtualenv.html

2 2

Debian Package Install - Ownership and Permissions
by Dave Hall 07 Apr '23

07 Apr '23

Hello, I know that installing from Debian packages is not the preferred method - unfortunately that's what I'm stuck with at the moment. I have an installation that is sort of working, but there seems to be a lot of issues relating to ownership and permissions that I'll have to manage by hand, so I am asking for some guidance. I'm seeing an interplay between 'list' (the existing Mailman2 user), www-data (the Apache user) and root. Given that it seems like almost everything that's part of mailman3-web/django/hyperkitty is running in uwsgi, should I maybe change /etc/mailman3/uwsgi.ini to use 'list' as the uid/gid rather than www-data and then also change any user/group permission to 'list' as well? Thanks -Dave -- Dave Hall Binghamton University

4 9

Problem with starting core - problem getting a lock on something
by Jens Günther 06 Apr '23

06 Apr '23

Unfortunately our mailman-core-container doesn't start anymore correctly. We updated lately to v0.4.5 and it ran smoothly for the last 4 weeks. This morning the RAM crashed and I then had to restore some things since the RAID was affected. Anyway, the container doesn't get up anymore although we didn't change anything in the setup. Does anybody know what the error means and how we could fix that? "Could not acquire the lock" normally means that some permissions aren't right ... right? Actually I don't know where to start. What I already did: remove the container completely and rebuild it. Thank you in advance! Jens. Traceback (most recent call last): File "/usr/lib/python3.10/site-packages/mailman/bin/master.py", line 125, in acquire_lock_1 lock.lock(timedelta(seconds=0.1)) File "/usr/lib/python3.10/site-packages/flufl/lock/_lockfile.py", line 386, in lock raise TimeOutError('Could not acquire the lock') flufl.lock._lockfile.TimeOutError: Could not acquire the lock During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3.10/site-packages/flufl/lock/_lockfile.py", line 237, in details lockfile, hostname, pid, random_ignored = filename.split( ValueError: not enough values to unpack (expected 4, got 1) The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/usr/bin/master", line 8, in <module> sys.exit(main()) File "/usr/lib/python3.10/site-packages/click/core.py", line 1130, in __call__ return self.main(*args, **kwargs) File "/usr/lib/python3.10/site-packages/click/core.py", line 1055, in main rv = self.invoke(ctx) File "/usr/lib/python3.10/site-packages/click/core.py", line 1404, in invoke return ctx.invoke(self.callback, **ctx.params) File "/usr/lib/python3.10/site-packages/click/core.py", line 760, in invoke return __callback(*args, **kwargs) File "/usr/lib/python3.10/site-packages/mailman/bin/master.py", line 580, in main lock = acquire_lock(force) File "/usr/lib/python3.10/site-packages/mailman/bin/master.py", line 151, in acquire_lock lock = acquire_lock_1(force) File "/usr/lib/python3.10/site-packages/mailman/bin/master.py", line 131, in acquire_lock_1 hostname, pid, tempfile = lock.details File "/usr/lib/python3.10/site-packages/flufl/lock/_lockfile.py", line 241, in details raise NotLockedError('Details are unavailable') from error flufl.lock._lockfile.NotLockedError: Details are unavailable

1 1

Hyperkitty shows "<" as <
by Andreas Schamanek 05 Apr '23

05 Apr '23

Hi fellow Hyperkitties, I migrated from Mailman 2 to 3 and imported my 1st list via `manage.py hyperkitty_import` to Hyperkitty 1.3.4 (the Debian package), but that might not even be relevant to my problem: All "<" and ">" in old and new messages are shown as "<" and ">" in message views _however_ they are shown correctly in overview abstracts e.g. at //server/mm3/hyperkitty/list/testlist@server/latest Is this a bug in Hyperkitty? Or is our server doing something funky? -- -- Andreas :-)

2 4

Mailman and Mailman-web databases
by Andrew Hodgson 05 Apr '23

05 Apr '23

Hi. Just come out of a bit of a server reorg where I followed the new instructions to get Mailman3 up and running with Mailman-web. Virtualenv Installation - Mailman Suite 3.3 documentation (list.org)<https://docs.list.org/en/latest/install/virtualenv.html> In these instructions we are using 2 databases for the Mailman and Django components. I guess it doesn't harm anything to have just one database for both but wondered whether it was a good idea to split eventually? Thanks. Andrew.

3 2

Database Schema - v3.2.1 to v3.3.3
by Dave Hall 05 Apr '23

05 Apr '23

Hello. Have 4 Debian servers running Mailman3 v3.2.1 and sharing the same external MySql databases for Mailman3 and Mailman3-web. I am in the process of migrating to v3.3.3. It would be easiest to perform this upgrade one server at a time, but this would mean that for a short time I would have v3.2.1 and v3.3.3 using the same databases. I am wondering if there are any MySql schema differences between the two versions. If there are, having the two different versions 'cohabitating' won't work.. Thanks. -Dave -- Dave Hall Binghamton University

3 2

Held messages page not rendering the message
by mike-mailman＠earth.li 04 Apr '23

04 Apr '23

Hi When the list moderator goes to the held_messages page, they correctly get a list of the held messages and can accept/reject/discard them However, clicking on the individual message to read it doesn't work - it does nothing visible at all. From debug I can see it requests /mailman3/postorius/api/list/<list>/held_message/1/ which returns correctly (and the body includes the message as expected) - but it never renders it Any idea what could be wrong? Thanks -- Mike

5 14

upgrading in FreeBSD 13.1-p7: problem with aiosmtpd and lmtp runner
by Guillermo Hernandez (Oldno7) 04 Apr '23

04 Apr '23

As you could have read yesterday, I had problems upgrading to the last versions of mailman3 related apps. The lmtp runner stopped after upgrade and showed and error in aiosmtpd package. the O.S. version running may servers is FreeBSD 13.1-p7 That was in a mailman3 server with few lists and traffic. O did the upgrade today in the server that has many lists and hard traffic. When I restarted mailman it showed this trace: Generating MTA alias maps /usr/local/mailman3 # Traceback (most recent call last): File "/usr/local/bin/runner", line 33, in <module> sys.exit(load_entry_point('mailman==3.3.8', 'console_scripts', 'runner')()) File "/usr/local/lib/python3.9/site-packages/click/core.py", line 1130, in __call__ return self.main(*args, **kwargs) File "/usr/local/lib/python3.9/site-packages/click/core.py", line 1055, in main rv = self.invoke(ctx) File "/usr/local/lib/python3.9/site-packages/click/core.py", line 1404, in invoke return ctx.invoke(self.callback, **ctx.params) File "/usr/local/lib/python3.9/site-packages/click/core.py", line 760, in invoke return __callback(*args, **kwargs) File "/usr/local/lib/python3.9/site-packages/click/decorators.py", line 26, in new_func return f(get_current_context(), *args, **kwargs) File "/usr/local/lib/python3.9/site-packages/mailman/bin/runner.py", line 184, in main runner = make_runner(*runner_spec, once=once) File "/usr/local/lib/python3.9/site-packages/mailman/bin/runner.py", line 70, in make_runner return runner_class(name, slice) File "/usr/local/lib/python3.9/site-packages/mailman/runners/lmtp.py", line 295, in __init__ self.lmtp = LMTPController(LMTPHandler(), hostname=hostname, port=port) File "/usr/local/lib/python3.9/site-packages/aiosmtpd/controller.py", line 417, in __init__ self._localhost = get_localhost() File "/usr/local/lib/python3.9/site-packages/aiosmtpd/controller.py", line 66, in get_localhost with makesock(AF_INET6, SOCK_STREAM) as sock: File "/usr/local/lib/python3.9/socket.py", line 232, in __init__ _socket.socket.__init__(self, family, type, proto, fileno) OSError: [Errno 43] Protocol not supported As Mark pointed it can be circunverted modifying /PATH_TO_YOUR_PYTHON/site-packages/aiosmtpd/controller.py and changing the 49th line as this: # Helper function to assist in mocking^M ## return has_ipv6^M return False After that, restarting mailman 3 works perfectly. It seems that FreeBSD is handling IPv6 in a way that other OSs dont. It surprise me, because FreeBSD was the first OS where IPv6 was deployed, but it is what it is. Thaks to everybody for your patience, specially Odhiambo and Mark. -- ___________________________________________ 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.

4 11