September 2021 - Mailman-users - lists.mailman3.org

Installation -- error on mailman-web migrate
by Mark Dale 17 Sep '21

17 Sep '21

Thank you for your reply earlier regarding "creating the mailman.cfg permissions". Now that's clear I proceeded on through the installation instructions at: https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst… ========== Installing Web UI To install the web components, run the following commands with virtualenv activated: root@mx:~# su mailman (venv) mailman@mx:/root$ pip install mailman-web mailman-hyperkitty (venv) mailman@mx:~$ exit exit ========== Initial Configuration Then, create a new configuration file at /etc/mailman3/settings.py root@mx:~# nano /etc/mailman3/settings.py I note that in the sample "settings.py" file, there are lines that have the directory "web" in the file paths ... STATIC_ROOT = '/opt/mailman/web/static' LOGGING['handlers']['file']['filename'] = '/opt/mailman/web/logs/mailmanweb.log' ... but as yet there is no directory "web". root@mx:/opt/mailman# ls -la total 44 drwxr-xr-x 6 mailman mailman 4096 Sep 17 03:52 . drwxr-xr-x 3 root root 4096 Sep 13 01:48 .. -rw------- 1 mailman mailman 308 Sep 17 04:01 .bash_history -rw-r--r-- 1 mailman mailman 220 Aug 4 22:25 .bash_logout -rw-r--r-- 1 mailman mailman 3564 Sep 17 03:47 .bashrc drwxr-xr-x 3 mailman mailman 4096 Sep 13 01:52 .cache -rw-r--r-- 1 mailman mailman 0 Aug 15 16:21 .cloud-locale-test.skip drwxr-xr-x 3 mailman mailman 4096 Sep 13 01:55 .local drwxr-xr-x 3 mailman mailman 4096 Sep 17 03:43 mm -rw-r--r-- 1 mailman mailman 807 Aug 4 22:25 .profile -rw-r--r-- 1 mailman mailman 66 Sep 17 03:52 .selected_editor drwxr-xr-x 7 mailman mailman 4096 Sep 13 01:52 venv ========== Run database migrations root@mx:~# su mailman (venv) mailman@mx:/root$ mailman-web migrate Here a ton of errors get printed, but one in particular: Traceback (most recent call last): ... FileNotFoundError: [Errno 2] No such file or directory: '/opt/mailman/web/logs/mailmanweb.log' ... ========== Was I meant to create the directories "web/logs/" and the "mailmanweb.log" file at some point, or were they meant to get created during the mailman-web install process? Should the owner/group be "mailman"?

2 5

Running mailman shell commands in a script
by Eggert Ehmke 16 Sep '21

16 Sep '21

Hello, I understand that the mailman shell is basically interactive. I need to run some actions as adding and deleting users in a Linux shell script, or even from another python program. How does that work? In fact, I miss the commands that were in the bin directory of the old mailman2 installation. Wouldn't it be nice to add them again to mailman3? Cheers, Eggert

2 2

Blocking email addresses
by Eggert Ehmke 16 Sep '21

16 Sep '21

In mailman2 there was an option to put the email of rejected posts into the block list. The block list is still there in mailman3, but I have to insert the address manually. Are there any plans to activate this feature again?

3 2

Does anyone have a working DKIM/ARC configuration?
by Philip Colmer 16 Sep '21

16 Sep '21

I've configured a Mailman 3 server with Postfix and added OpenDKIM to the latter to provide the DKIM headers, and configured Mailman to provide the ARC headers. However, in sending test messages to a mailbox hosted by Microsoft, I'm seeing a header like this: ARC-Authentication-Results: i=2; mx.microsoft.com 1; spf=pass (sender ip is 1.2.3.4) smtp.rcpttodomain=destination.org smtp.mailfrom=mmserver.org; dmarc=bestguesspass action=none header.from=mmserver.org; dkim=test (signature was verified) header.d=mmserver.org; dkim=fail (signature did not verify) header.d=sender.org; arc=fail (47) (I've changed the domains and IP address) Manually sending an email from the server to the same external email address does give me an email with a valid DKIM header: Authentication-Results: spf=pass (sender IP is 1.2.3.4) smtp.mailfrom=mmserver.org; destination.org; dkim=test (signature was verified) header.d=mmserver.org;destination.org; dmarc=bestguesspass action=none header.from=mmserver.org;compauth=pass reason=109 So I'm unclear as to where the problem may lie ... Hence the question: does anyone have Mailman 3 + Postfix working successfully with DKIM and ARC? Thanks. Philip

3 7

Are the gitlab repositories kept in sync?
by Brett Delmage 13 Sep '21

13 Sep '21

See https://gitlab.com/search?search=mailman&group_id=&project_id=&snippets=fal… I see that core is update frequently but other packages such as Mailman web have not been. mailman-suite is two weeks old. Mailman Web has not been updated for wo weeks. Does that mean I can download that Postorius and it will work with the latest mailman core updated in the past day? I expect that most changes don't break interfaces. Is that correct? Brett

2 1

Installation - creating the mailman.cfg permissions
by Mark Dale 13 Sep '21

13 Sep '21

https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst… Following the instructions (at the above URL) to create the mailman.cfg, I'm getting a permissions problem when trying to do so as user "mailman" . Although the instructions say to create the file as user "mailman", should it be created by root (with/without virtualenv?) and then chown to "mailman"? ***** Make sure that you are running commands as mailman user from here forth. root@mx:/# su mailman Create the virtualenv for Mailman: mailman@mx:/$ cd /opt/mailman mailman@mx:~$ python3 -m venv venv Activate the created virtualenv: mailman@mx:~$ source /opt/mailman/venv/bin/activate The rest of this documentation assumes that virtualenv is activated. Installing Mailman Core (venv) mailman@mx:~$ pip install wheel mailman psycopg2-binary ...Successfully installed... After this, create a configuration file at /etc/mailman3/mailman.cfg for Mailman Core: (venv) mailman@mx:~$ nano /etc/mailman3/mailman.cfg [ Directory '/etc/mailman3' does not exist ] (venv) mailman@mx:~$ mkdir /etc/mailman3 mkdir: cannot create directory ‘/etc/mailman3’: Permission denied *****

4 3

External Mail-Server?
by Florian Schulze 12 Sep '21

12 Sep '21

Hi! Is it possible to use an external Mail-Server? Does mailman3 support that directly, or would I have to setup a local MTA which somehow fetches incoming mails from the external inbox and uses the external Mail-Server for delivery? Does anyone do that and have example configurations? Regards, Florian Schulze

6 7

User authentication against IMAP or AD
by Adam Minski 10 Sep '21

10 Sep '21

Hello, is there any supported way to authenticate users against IMAP or Microsoft Active Directory? As a workaround I thought about a OpenID-IMAP or OpenID-AD Bridge, are there any experiences? Thx.

2 1

New messages not being archived
by Sarah H 07 Sep '21

07 Sep '21

I have 2 active lists that are properly mailing out and working, plus an admin testing list that is as well. The list info pane correctly shows the mail volume and the imported archives from the previous 2.1 installation are present for both active lists. None of the 3 lists are generating new entries in the archive, all 3 are set up with default settings except 1 active and admin are set to private. I know that hyperkitty is showing some new content as admin was created in postorius and the list is present in hyperkitty and working in mailman. None of the logs show anything of note, mailmanweb.log has no new entries since it caused a serious issue when I changed the domain, uwsgi-error is the same and uwsgi.log has proper access logs. When trying to add a new thread via the hyperkitty interface I can see the email go through the maillog, I get the email with the entered content and everything else works, it just doesn't add a new thread to the archive. The installation is set up with the default settings from the virtualenv installation guide. Any assistance would be appreciated.

5 30

Mailman container images 0.3.12 is now out
by Abhilash Raj 05 Sep '21

05 Sep '21

Hey Everyone, I have just tagged release 0.3.12 on Github for container images for Mailman 3[1]. This release includes the fix for CVE-2021-40347 that was announced earlier today. For the folks using 0.3 or 0.3.11 release tags, it is highly recommended that you upgrade to this release. This release also bumps the version of Mailman Core to 3.3.4, Mailmanclient to 3.3.3 and Django-mailman3 to 1.3.7. Note that is since the main and v0.3.12 branches are different in many ways, the default documentation[2] and the docker-compose.yaml files in the main branch aren't accurate if you are using the stable release. Please refer to the README[3] at v0.3.12 tag in the Github repo for more accurate docker-compose.yaml and documentation. The project has grown large enough that we need to start versioning the documentation, if someone has experience with versioning docs using Github pages and mkdocs, then I very much need some help here! For those of you who are using the rolling release, it is recommended that you **don't** upgrade to this stable release. The fixes have been pulled into the rolling tags too, so just make sure that you upgrade to the latest published version of rolling release, which as of this writing should be based off on fda837f8d15540e190992c30f7971f50fca54dac commit[4]. This might not be the latest by the time you upgrade if I add a new commit, so look for versions published after 4:00 PM PST 9/5/2021. I am also working on cutting a new release, 0.4.0, which is backwards incompatible with the setup required to talk to web server and MTA (hence the minor version bump!). That should bring the rolling releases and stable releases closer to each other and add improvements around not needing static IPs in the docker network anymore, plus several bug fixes. If someone wants to test the upgrade to 0.4.0 from 0.3 release and is willing to try out the instructions at [5], it would give me some confidence in cutting out the release sooner. The only thing stopping the release of 0.4.0 images is that I haven't verified if the upgrade from 0.3 is documented enough or not. For all the registries listed in README[6], I am still trying to push to Quay (maybe I need to just skip pushing to Quay :-). So, just use the other two to pull the images, Github (ghcr.io) has more generous pull download policy for un-authenticated users though. [1]: https://github.com/maxking/docker-mailman/releases/tag/v0.3.12 [2]: https://asynchronous.in/docker-mailman/ [3]: https://github.com/maxking/docker-mailman/tree/v0.3.12 [4]: https://github.com/maxking/docker-mailman/commit/fda837f8d15540e190992c30f7… [5]: https://asynchronous.in/docker-mailman/news/#upgrading-to-040-release [6]: https://github.com/maxking/docker-mailman#container-registries -- thanks, Abhilash Raj (maxking)

1 0