Missing "Domain Name" when trying to create new Mailman list

I’ve installed Mailman 3 (3.8-2~deb12u2) and Webmin-virtualmin-mailman (6.11), and I’ve created a virtual server. All fine :slight_smile:

In Webmin, I then select Servers → Virtualmin Mailman Mailing Lists, and try to Add Mailing List. But the drop-down menu “Domain name” is empty. I can’t enter or choose anything. Why is that?

I’ve been a happy Mailman user for many years, but I’m quite new to Virtualmin. I really look forward to Virtualmin helping me administer my mailing lists :slight_smile:

| SYSTEM INFORMATION||
| OS type and version | Debian Linux 12 |
| Virtualmin version | 7.20.1.gpl-1 |

You need to enable the Mailman Feature for a domain.

The plugin also needs to be enabled in Features and Plugins.

Er, not in that order…enable it in Features and Plugins first.

Thanks a lot for your help.

So, here’s a brief summary of what to do, if you want to run Mailman3 with Virtualmin on Debian:

  1. In Virtualmin, create one or more virtual servers to host Mailman mailing lists

  2. $ apt install mailman3

  3. $ apt install webmin-virtualmin-mailman

  4. $ apt install python3-pymysql

  5. $ systemctl start mailman3

  6. In the web-interface go to “Virtualmin” → “System Settings” → “Features and Plugins”, and select “Mailman” as available for use by virtual servers

  7. In the web-interface go to ”Virtualmin” and select a virtual server, you want to host Mailman mailing lists. Then go to “Edit Virtual Server”, mark “Mailman mailing lists” as enabled, and click “Save Virtual Server”.

Does this seem ok?

/Jesper

Debian Linux 12
Virtualmin 7.20.1.gpl-1

OK, I tried this. But when I try to create a new Mailman mailing list, I get the error:

Failed to create mailing list : List creation command failed :
sh: 1: /var/lib/mailman3/bin/newlist: not found

It seems my installation of Mailman3 doesn’t have any commands in /var/lib/mailman3/bin

You’ll need to figure out where the commands are, and update the Module Configuration (click the gear icon :gear: in the upper left part of the content pane in the Mailman module).

I’m surprised it’s moved yet again. It seems like we updated the location for Debian 11. That’s annoying. virtualmin-mailman/config-debian-linux-11-ALL at master · virtualmin/virtualmin-mailman · GitHub

You can use your package manager to find where things are: dpkg -L mailman3

I looked into this and found out that the problem is related to the fact that in mailman3, the mailman binary now needs the “–run-as-root” parameter. I’ve made a temporary fix by adding this script as “/usr/lib/mailman3/bin/mailman3”

#!/usr/bin/sh
# echo "Calling mailman --run-as-root $@";
mailman --run-as-root $@

and setting the default binary for the plugin to “/usr/lib/mailman3/bin/mailman3”.

1 Like

I’m getting close to have Mailman 3 working on Debian with Virtualmin :slight_smile: I’ve followed the nice description here How to Install Mailman3 on Debian 11 | LinuxCloudVPS Blog for the installation, and the description here Migrating from Mailman 2.1 to Mailman 3 — Mailman Suite 3.3 documentation for importing lists from Mailman 2.

I still have some questions / issues, however:

When I try to delete a mailing list in Virtualmin, I get this error:
Undefined subroutine &virtualmin_mailman::get_postfix_version called at ./virtualmin-mailman-lib.pl line 347.
I can’t find this subroutine anywhere?

Also, I’m a bit confused about the relationship between the mailman interface in Virtualmin, and Mailman 3’s own interface. It seems to me, that a mailing list created outside of Virtualmin, doesn’t show up in Virtualmin?

Help and comments appreciated :slight_smile:
/Jesper Holck, Roskilde, Denmark

A mailing list created outside of Virtualmin doesn’t belong to any virtual server, and thus isn’t a concern of Virtualmin.

That looks like an artifact of a refactor of the code that missed a line. Jamie has since fixed it, but I guess didn’t tag a new version.

Here’s the commit where it was fixed:

But, there have been a number of other changes since the 6.11 release, probably also useful for your situation. I’ll ask @Jamie if we can do a new release of that.

1 Like

Sure, I’ve tagged a 6.12 version for release.

2 Likes

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.