Trying to set up mailman3 on my mail server
I'm having a lot of trouble with trying to set up mailman3 on my mail server.
It's on an AWS instance, running Ubuntu 20.04 LTS. All software is installed from Ubuntu packages. Mailman version is 3.2.2.
The problem I am trying to troubleshoot first is how this can be happening:
Oct 14 11:27:26 2021 (2341) ACCEPT: <f36e1ed0-9d25-b661-9c94-4ce999f6d5fd@elyograg.org> Oct 14 11:27:27 2021 (2344) Cannot connect to SMTP server 127.0.0.1 on port 25
From the shell, I can "telnet localhost 25" successfully, even as the "list" user. Apparmor is disabled. The UFW firewall is enabled, which allows all traffic on the loopback interface. I disabled ipv6 at the kernel level, but had the same problem with ipv6 enabled, so I don't think ipv6 is related at all. I do not see any connections in the postfix log that correspond to the mailman connection error.
From a fresh install of mailman, I created two mailing lists. Once upon a time I had those lists active on a Debian 6 machine running mailman 2.1.13 ... I copied the mailing list config from that machine over and used the "import21" facility to import the configuration into the new mailman3 install. That worked without error and I can see the lists and their members with the "mailman" command. I found instructions for integration with postfix, and added the required three config lines to the postfix config.
When I try to send a message to the list, I get what I pasted above in the mailman log. I think that means the postfix integration is working, and is forwarding to mailman.
I'm hoping somebody can give me some pointers, and if more information is needed for troubleshooting, let me know what is needed.
I'm also having trouble with the web UI ... I thought I had found what to do with Apache, but it's having problems and I do not know what to do so it works. The UI is not super important right now, I'd like to get the lists working first.
I first tried to get help on the IRC channel, but that appears to be a dead end. I did give it several hours.
Thanks, Shawn
On 10/14/21 7:51 PM, Shawn Heisey wrote:
I'm having a lot of trouble with trying to set up mailman3 on my mail server.
It's on an AWS instance, running Ubuntu 20.04 LTS. All software is installed from Ubuntu packages. Mailman version is 3.2.2.
Please see <https://wiki.list.org/x/12812344>[1]
The problem I am trying to troubleshoot first is how this can be happening:
Oct 14 11:27:26 2021 (2341) ACCEPT: <f36e1ed0-9d25-b661-9c94-4ce999f6d5fd@elyograg.org> Oct 14 11:27:27 2021 (2344) Cannot connect to SMTP server 127.0.0.1 on port 25
From the shell, I can "telnet localhost 25" successfully, even as the "list" user. Apparmor is disabled. The UFW firewall is enabled, which allows all traffic on the loopback interface. I disabled ipv6 at the kernel level, but had the same problem with ipv6 enabled, so I don't think ipv6 is related at all. I do not see any connections in the postfix log that correspond to the mailman connection error.
There's a long thread on this at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/5HD4SBASMERP5CUEWCNQCB7KNAIQWSXF/>. Your issue may not be the same, but that one had to do with templates, perhaps created in Postorius, that couldn't be accessed.
From a fresh install of mailman, I created two mailing lists. Once upon a time I had those lists active on a Debian 6 machine running mailman 2.1.13 ... I copied the mailing list config from that machine over and used the "import21" facility to import the configuration into the new mailman3 install. That worked without error and I can see the lists and their members with the "mailman" command. I found instructions for integration with postfix, and added the required three config lines to the postfix config.
When I try to send a message to the list, I get what I pasted above in the mailman log. I think that means the postfix integration is working, and is forwarding to mailman.
Yes, and the message should be archived in whatever archivers are enabled. If the prototype archiver is enabled you should see the message in Mailman's var/archives/prototype/<list-id>/new/ directory and if HyperKitty is enabled, in mailman's database in the hyperkitty_email table.
I'm hoping somebody can give me some pointers, and if more information is needed for troubleshooting, let me know what is needed.
If your web UI isn't working, you probably haven't created any templates
in Postorius, but import21 will create templates and if you ran import21
as root, you may have created templates and perhaps other things that
can't be accessed by the Mailman user (list in your case). All Mailman
related commands should be run only by the Mailman user.
[1] This FAQ says you should be going to Debian/Ubuntu for support. If you've tried that and are not getting help there, I respectfully submit that you should purge the Debian/Ubuntu package and start over from here <https://docs.mailman3.org/en/latest/install/virtualenv.html>.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Oct 14, 2021, at 7:51 PM, Shawn Heisey <mailman@elyograg.org> wrote:
I'm having a lot of trouble with trying to set up mailman3 on my mail server.
It's on an AWS instance, running Ubuntu 20.04 LTS. All software is installed from Ubuntu packages. Mailman version is 3.2.2.
I REALLY encourage you not to install via the Ubuntu packages. A number of us here have done so and it always ends in tears. I ended up paying someone to re-install for me via pip so I had a clean baseline to admin from going forward.
Seriously, the packages are an outdated mess and you end up with a somewhat non-standard install, which makes it harder for this community to help you out.
Save yourself a lot of trouble and start over now before you have actual lists running. Use the docker images or install via pip. You really want to save yourself this grief. Ask me how I know.
- Mark
mark@pdc-racing.net | 408-348-2878
On 10/14/21 10:09 PM, Mark Dadgar wrote:
I REALLY encourage you not to install via the Ubuntu packages. A number of us here have done so and it always ends in tears. I ended up paying someone to re-install for me via pip so I had a clean baseline to admin from going forward.
I had lots of trouble with the pip/venv setup. So I decided to give the docker route a try. Having trouble with that too. Looking over the instructions, I seem to have missed some of the info on my first try. I will give it another whirl after my work shift ends today.
Thanks, Shawn
On Oct 15, 2021, at 7:46 AM, Shawn Heisey <mailman@elyograg.org> wrote:
On 10/14/21 10:09 PM, Mark Dadgar wrote:
I REALLY encourage you not to install via the Ubuntu packages. A number of us here have done so and it always ends in tears. I ended up paying someone to re-install for me via pip so I had a clean baseline to admin from going forward.
I had lots of trouble with the pip/venv setup. So I decided to give the docker route a try. Having trouble with that too. Looking over the instructions, I seem to have missed some of the info on my first try. I will give it another whirl after my work shift ends today.
That’s actually why I paid someone to do in the initial install. While I have 3+ decades of UNIX-like admin experience, I am not even remotely well-versed in Python and its ecosystem and/or Docker.
Unfortunately, the person I hired, who did a great job and has contributed mightily to this community, is no longer with us.
- Mark
mark@pdc-racing.net | 408-348-2878
On 10/15/21 9:32 AM, Mark Dadgar wrote:
That’s actually why I paid someone to do in the initial install. While I have 3+ decades of UNIX-like admin experience, I am not even remotely well-versed in Python and its ecosystem and/or Docker.
Unfortunately, the person I hired, who did a great job and has contributed mightily to this community, is no longer with us.
He did however post a writeup at <https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10>. There is also <https://docs.google.com/document/d/1xIcSsoNFp2nHi7r4eQys00s9a0k2sHhu1V5PlantPTs/> from another user.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (3)
-
Mark Dadgar -
Mark Sapiro -
Shawn Heisey