On Mon, Aug 15, 2022 at 4:37 PM Mark Sapiro <mark@msapiro.net> wrote:
On 8/15/22 00:32, Odhiambo Washington wrote:
Apparently so, because: mailman@lists:~$ /opt/mailman/mm/venv/bin/mailman lists No matching mailing lists found mailman@lists:~$
Which is surprising, given this: https://imgur.com/a/LPrh42K
Postfix is talking to a different Mailman core.
There isn't any other. This server has only been running Mailam21.
root@lists:/home/wash# su - mailman mailman@lists:~$ /opt/mailman/mm/venv/bin/mailman create skunkworks@lists.my.co.ke sh: 1: /usr/sbin/postmap: not found sh: 1: /usr/sbin/postmap: not found Traceback (most recent call last): ... RuntimeError: command failure: /usr/sbin/postmap /opt/mailman/var/data/postfix_lmtp, 127, Key has expired command failure: /usr/sbin/postmap /opt/mailman/var/data/postfix_domains, 127, Key has expired
Now that wants Postfix, while I don't use Postfix, but Exim as the MTA.
In the [mta] section of mailman.cfg, put
incoming: mailman.mta.exim4.LMTP configuration: python:mailman.config.exim4See
https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.ht...
That is exactly what I have in my mailman.cfg
Installing Postfix suppresses that message though. I installed Postfix and then disabled it.
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)