One more thing, I'm using the README.Debian addition to /etc/postfix/main.cf rather than the one in the instructions at https://docs.mailman3.org/en/latest/config-core.html#configuring-mta .

In other words, mine reads:

# Mailman related settings owner_request_special = no transport_maps = hash:/var/lib/mailman3/data/postfix_lmtp local_recipient_maps = proxy:unix:passwd.byname $alias_maps hash:/var/lib/mailman3/data/postfix_lmtp relay_domains = ${{$compatibility_level} < {2} ? {$mydestination} : {}} hash:/var/lib/mailman3/data/postfix_dom ains

instead of:

# Support the default VERP delimiter. recipient_delimiter = + unknown_local_recipient_reject_code = 550 owner_request_special = no transport_maps = hash:/path-to-mailman/var/data/postfix_lmtp local_recipient_maps = hash:/path-to-mailman/var/data/postfix_lmtp relay_domains = hash:/path-to-mailman/var/data/postfix_domains

.... but they both give the same error.

On Tue, 2022-10-11 at 15:31 -0400, William Oliver wrote:

I have had an installation of mailman3 running for a  year or so with no problems.  This was a manual installation.  I ended up having to change machines, so I decided to install using the debian 11 package. It seems to have gone well except.... when I restart mailman3 service, I get the following fail and error message:

oot@emergenis:/etc/nginx/sites-enabled# systemctl restart mailman3 Job for mailman3.service failed because the control process exited with error code. See "systemctl status mailman3.service" and "journalctl -xe" for details. root@emergenis:/etc/nginx/sites-enabled# systemctl status mailman3 ● mailman3.service - Mailman3 server Loaded: loaded (/lib/systemd/system/mailman3.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Tue 2022-10-11 15:09:45 EDT; 8s ago Docs: man:mailman(1) https://mailman.readthedocs.io/ Process: 1056 ExecStart=/usr/bin/mailman -C /etc/mailman3/mailman.cfg start --force (code=exited, status=1/FAILURE) CPU: 9.193s

Oct 11 15:09:43 emergenis.com mailman3[1056]: File "/usr/lib/python3/dist-packages/mailman/commands/cli_control.py", line 109, in start Oct 11 15:09:43 emergenis.com mailman3[1056]: call_name(config.mta.incoming).regenerate() Oct 11 15:09:43 emergenis.com mailman3[1056]: File "/usr/lib/python3/dist-packages/mailman/mta/postfix.py", line 133, in regenerate Oct 11 15:09:43 emergenis.com mailman3[1056]: raise RuntimeError(NL.join(errors)) Oct 11 15:09:43 emergenis.com mailman3[1056]: RuntimeError: command failure: /usr/sbin/postmap /var/lib/mailman3/data/postfix_lmtp, 1, Operation not permitted Oct 11 15:09:43 emergenis.com mailman3[1056]: command failure: /usr/sbin/postmap /var/lib/mailman3/data/postfix_domains, 1, Operation not permitted Oct 11 15:09:45 emergenis.com systemd[1]: mailman3.service: Control process exited, code=exited, status=1/FAILURE Oct 11 15:09:45 emergenis.com systemd[1]: mailman3.service: Failed with result 'exit-code'. Oct 11 15:09:45 emergenis.com systemd[1]: Failed to start Mailman3 server. Oct 11 15:09:45 emergenis.com systemd[1]: mailman3.service: Consumed 9.193s CPU time.

Heres the ls for /var/lib/mailman3/data:

root@emergenis:/var/lib/mailman3/data# ls -l total 8 -rw-rw---- 1 list list 315 Oct 11 15:09 postfix_domains -rw-rw---- 1 list list 318 Oct 11 15:09 postfix_lmtp

The web interface comes up and seems to "work" but of course complains that mailman3 isn't actually running.

I assume there's some posfix config I haven't done right, but I am clueless as to what it is.

Thanks in advance for any pointers.

billo

---

Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

OK. I apologize for wasting people's time.

In case anybody's interested, the problem was that when I cut an pasted from the debian README file, I didn't notice the hard line break. So, in main.cf, the line

hash:/var/lib/mailman3/data/postfix_dom ains

was actually two lines with a hard break rather than a continuation, and "ains" ain't a command.

Doh.

So, I have to say, with the exception of my stupid cut and paste, the Debian automatic installation is a breeze.  Good job to whomever did it.  It's a thousand times faster than downloading and configuring from scratch, like I did last time.

billo

On Tue, 2022-10-11 at 17:04 -0400, William Oliver wrote:

One more-one more thing...

Here's /var/lib/mailman3/data/postfix_lmtp:

root@emergenis:/var/lib/mailman3/data# more postfix_lmtp # AUTOMATICALLY GENERATED BY MAILMAN ON 2022-10-11 21:00:15 # # This file is generated by Mailman, and is kept in sync with the binary hash # file. YOU SHOULD NOT MANUALLY EDIT THIS FILE unless you know what you're # doing, and can keep the two files properly in sync. If you screw it up, # you're on your own.

So.. if it can write that, it shouldn't be a permissons problem...

billo

On Tue, 2022-10-11 at 15:39 -0400, William Oliver wrote:

...

  One more thing, I'm using the README.Debian addition to /etc/postfix/main.cf rather than the one in the instructions at  https://docs.mailman3.org/en/latest/config-core.html#configuring-mta .

In other words, mine reads:

# Mailman related settings owner_request_special = no transport_maps = hash:/var/lib/mailman3/data/postfix_lmtp local_recipient_maps = proxy:unix:passwd.byname $alias_maps hash:/var/lib/mailman3/data/postfix_lmtp relay_domains = ${{$compatibility_level} < {2} ? {$mydestination} : {}} hash:/var/lib/mailman3/data/postfix_dom ains

instead of:

# Support the default VERP delimiter. recipient_delimiter = + unknown_local_recipient_reject_code = 550 owner_request_special = no transport_maps = hash:/path-to-mailman/var/data/postfix_lmtp local_recipient_maps = hash:/path-to-mailman/var/data/postfix_lmtp relay_domains = hash:/path-to-mailman/var/data/postfix_domains

.... but they both give the same error.

On Tue, 2022-10-11 at 15:31 -0400, William Oliver wrote:

...

I have had an installation of mailman3 running for a  year or so with no problems.  This was a manual installation.  I ended up having to change machines, so I decided to install using the debian 11 package. It seems to have gone well except.... when I restart mailman3 service, I get the following fail and error message:

oot@emergenis:/etc/nginx/sites-enabled# systemctl restart mailman3 Job for mailman3.service failed because the control process exited with error code. See "systemctl status mailman3.service" and "journalctl -xe" for details. root@emergenis:/etc/nginx/sites-enabled# systemctl status mailman3 ● mailman3.service - Mailman3 server Loaded: loaded (/lib/systemd/system/mailman3.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Tue 2022-10-11 15:09:45 EDT; 8s ago Docs: man:mailman(1) https://mailman.readthedocs.io/ Process: 1056 ExecStart=/usr/bin/mailman -C /etc/mailman3/mailman.cfg start --force (code=exited, status=1/FAILURE) CPU: 9.193s

Oct 11 15:09:43 emergenis.com mailman3[1056]: File "/usr/lib/python3/dist-packages/mailman/commands/cli_control.py", line 109, in start Oct 11 15:09:43 emergenis.com mailman3[1056]: call_name(config.mta.incoming).regenerate() Oct 11 15:09:43 emergenis.com mailman3[1056]: File "/usr/lib/python3/dist-packages/mailman/mta/postfix.py", line 133, in regenerate Oct 11 15:09:43 emergenis.com mailman3[1056]: raise RuntimeError(NL.join(errors)) Oct 11 15:09:43 emergenis.com mailman3[1056]: RuntimeError: command failure: /usr/sbin/postmap /var/lib/mailman3/data/postfix_lmtp, 1, Operation not permitted Oct 11 15:09:43 emergenis.com mailman3[1056]: command failure: /usr/sbin/postmap /var/lib/mailman3/data/postfix_domains, 1, Operation not permitted Oct 11 15:09:45 emergenis.com systemd[1]: mailman3.service: Control process exited, code=exited, status=1/FAILURE Oct 11 15:09:45 emergenis.com systemd[1]: mailman3.service: Failed with result 'exit-code'. Oct 11 15:09:45 emergenis.com systemd[1]: Failed to start Mailman3 server. Oct 11 15:09:45 emergenis.com systemd[1]: mailman3.service: Consumed 9.193s CPU time.

Heres the ls for /var/lib/mailman3/data:

root@emergenis:/var/lib/mailman3/data# ls -l total 8 -rw-rw---- 1 list list 315 Oct 11 15:09 postfix_domains -rw-rw---- 1 list list 318 Oct 11 15:09 postfix_lmtp

The web interface comes up and seems to "work" but of course complains that mailman3 isn't actually running.

I assume there's some posfix config I haven't done right, but I am clueless as to what it is.

Thanks in advance for any pointers.

billo

---

Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

---

Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

---

Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

On Wed, 2022-10-12 at 15:50 +0900, Stephen J. Turnbull wrote:

Thanks for the report.  Glad to hear OS packaging is working on *some* platforms.

From recent (painful) experience, I cannot recommend doing using the OS packages on Ubuntu 20 LTS, unfortunately.

Steve

There were a couple of gotchas, but not too bad. Happily, the README.debian and a few web pages fleshed it out. The only thing is that the packages put a lot of stuff in places different than the manual installation tells you to do, so I had to keep poking around to find stuff.

I was never able to install it on Ubuntu, either by package or by hand. I can't remember why, now, because it was some months ago -- but that's why I switched to Debian.