So I thought I have everything running. Fresh install of MM3 on Ubuntu-22.04.
I have created a list in postorius - it has the same name as my old list in MM2.
[image: MM3.png] Now, following - https://docs.mailman3.org/en/latest/migration.html - I change user to mailman so as to run the migration.
mailman@lists:~$ pwd /opt/mailman mailman@lists:~$ id uid=1003(mailman) gid=1002(mailman) groups=1002(mailman),4(adm),38(list) mailman@lists:~$ */opt/mailman/mm/venv/bin/mailman import21 skunkworks@lists.my.co.ke <skunkworks@lists.my.co.ke> /var/list/lists/skunkworks/config.pck *# running without specifying the absolute path is not working! Usage: mailman import21 [OPTIONS] LISTSPEC PICKLE_FILE Try 'mailman import21 -h' for help.
Error: No such list: skunkworks@lists.my.co.ke mailman@lists:~$ ls -al /var/list/lists/skunkworks/config.pck -rw-rw---- 1 root list 63765 Aug 14 11:10 /var/list/lists/skunkworks/config.pck
mailman@lists:~$ exim -bt skunkworks@lists.my.co.ke skunkworks@lists.my.co.ke router = mailman3_router, transport = mailman3_transport mailman@lists:~$
What am I missing?
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)
Mailman's content filtering has removed the following MIME parts from this message.
Content-Type: image/png Name: MM3.png
Replaced multipart/alternative part with first alternative.
On 8/14/22 11:04, Odhiambo Washington wrote:
So I thought I have everything running. Fresh install of MM3 on Ubuntu-22.04.
I have created a list in postorius - it has the same name as my old list in MM2.
[image: MM3.png]
Your image didn't make it through content filtering.
What is the fully qualified name of the list
mailman@lists:~$ /opt/mailman/mm/venv/bin/mailman import21 skunkworks@lists.my.co.ke /var/list/lists/skunkworks/config.pck Usage: mailman import21 [OPTIONS] LISTSPEC PICKLE_FILE Try 'mailman import21 -h' for help.
Error: No such list: skunkworks@lists.my.co.ke
Apparently the list you created is not named skunkworks@lists.my.co.ke
What am I missing?
The Mailman 3 list skunkworks@lists.my.co.ke including that exact domain must exist in order to import to it. Try
/opt/mailman/mm/venv/bin/mailman create skunkworks@lists.my.co.ke
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Mon, Aug 15, 2022 at 1:31 AM Mark Sapiro <mark@msapiro.net> wrote:
On 8/14/22 11:04, Odhiambo Washington wrote:
So I thought I have everything running. Fresh install of MM3 on Ubuntu-22.04.
I have created a list in postorius - it has the same name as my old list in MM2.
[image: MM3.png]
Your image didn't make it through content filtering.
The image only showed a listing of the MLs that I created via postorius.
What is the fully qualified name of the list
skunkworks@lists.my.co.ke
mailman@lists:~$ /opt/mailman/mm/venv/bin/mailman import21 skunkworks@lists.my.co.ke /var/list/lists/skunkworks/config.pck Usage: mailman import21 [OPTIONS] LISTSPEC PICKLE_FILE Try 'mailman import21 -h' for help.
Error: No such list: skunkworks@lists.my.co.ke
Apparently the list you created is not named skunkworks@lists.my.co.ke
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
What am I missing?
The Mailman 3 list skunkworks@lists.my.co.ke including that exact domain must exist in order to import to it. Try
/opt/mailman/mm/venv/bin/mailman create skunkworks@lists.my.co.ke
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): File "/opt/mailman/mm/venv/bin/mailman", line 8, in <module> sys.exit(main()) File "/opt/mailman/mm/venv/lib/python3.10/site-packages/click/core.py", line 1130, in __call__ return self.main(*args, **kwargs) File "/opt/mailman/mm/venv/lib/python3.10/site-packages/click/core.py", line 1055, in main rv = self.invoke(ctx) File "/opt/mailman/mm/venv/lib/python3.10/site-packages/mailman/bin/mailman.py", line 69, in invoke return super().invoke(ctx) File "/opt/mailman/mm/venv/lib/python3.10/site-packages/click/core.py", line 1657, in invoke return _process_result(sub_ctx.command.invoke(sub_ctx)) File "/opt/mailman/mm/venv/lib/python3.10/site-packages/click/core.py", line 1404, in invoke return ctx.invoke(self.callback, **ctx.params) File "/opt/mailman/mm/venv/lib/python3.10/site-packages/click/core.py", line 760, in invoke return __callback(*args, **kwargs) File "/opt/mailman/mm/venv/lib/python3.10/site-packages/click/decorators.py", line 26, in new_func return f(get_current_context(), *args, **kwargs) File "/opt/mailman/mm/venv/lib/python3.10/site-packages/mailman/commands/cli_lists.py", line 184, in create mlist = create_list(fqdn_listname, owners) File "/opt/mailman/mm/venv/lib/python3.10/site-packages/mailman/app/lifecycle.py", line 100, in create_list call_name(config.mta.incoming).create(mlist) File "/opt/mailman/mm/venv/lib/python3.10/site-packages/mailman/mta/postfix.py", line 93, in create self.regenerate() File "/opt/mailman/mm/venv/lib/python3.10/site-packages/mailman/mta/postfix.py", line 133, in regenerate raise RuntimeError(NL.join(errors)) 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.
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)
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.
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.exim4
See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.ht...
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
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 '^$|^.*#' ¯\_(ツ)_/¯ :-)
On 8/15/22 06:53, Odhiambo Washington wrote:
That is exactly what I have in my mailman.cfg
Installing Postfix suppresses that message though. I installed Postfix and then disabled it.
Your /opt/mailman/mm/venv/bin/mailman is talking to a different Mailman core than the one reading that mailman.cfg and the one Postorius is talking to.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Mon, Aug 15, 2022 at 4:59 PM Mark Sapiro <mark@msapiro.net> wrote:
On 8/15/22 06:53, Odhiambo Washington wrote:
That is exactly what I have in my mailman.cfg
Installing Postfix suppresses that message though. I installed Postfix
and
then disabled it.
Your /opt/mailman/mm/venv/bin/mailman is talking to a different Mailman core than the one reading that mailman.cfg and the one Postorius is talking to.
How can I track the one it's talking to?
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)
On 8/15/22 7:28 AM, Odhiambo Washington wrote:
On Mon, Aug 15, 2022 at 4:59 PM Mark Sapiro <mark@msapiro.net> wrote:
Your /opt/mailman/mm/venv/bin/mailman is talking to a different Mailman core than the one reading that mailman.cfg and the one Postorius is talking to.
How can I track the one it's talking to?
Try /opt/mailman/mm/venv/bin/mailman info
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Mon, Aug 15, 2022 at 7:57 PM Mark Sapiro <mark@msapiro.net> wrote:
On 8/15/22 7:28 AM, Odhiambo Washington wrote:
On Mon, Aug 15, 2022 at 4:59 PM Mark Sapiro <mark@msapiro.net> wrote:
Your /opt/mailman/mm/venv/bin/mailman is talking to a different Mailman core than the one reading that mailman.cfg and the one Postorius is talking to.
How can I track the one it's talking to?
Try
/opt/mailman/mm/venv/bin/mailman info
So this command's output pointed to /opt/mailman/var/etc/mailman.cfg instead of my file that is in /opt/mailman/mm/mailman.cfg According to the HOWTO <https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10> I am following, mailman.cfg should be in /opt/mailman/mm/.
Now I am wondering what I am missing again. Did something change? Should I place all my config files in /opt/mailman/var/etc/ instead of /opt/mailman/mm/ ?
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)
participants (2)
-
Mark Sapiro -
Odhiambo Washington