mailman2 import not working
Hello.
Recently I migrated a mailman2 mailing list to mailmam3. There was one problem[1] I faced. Currently I am running Debian packaged version (3.2.2-1) which don't have this fix. But it was manually done with this[2] method.
Basically this is what I did for migration:
mailman create -o <foo@example.com> foo-bar@lists.example.com mailman import 21 foo-bar@lists.example.com path/to/config.pck
Then imported archives with
python3 manage.py hyperkitty_import --pythonpath /usr/share/mailman3-web --settings settings -l foo-list@list.example.com <path to>/foo-list.mbox
python3 manage.py update_index_one_list foo-list@example.com --pythonpath /usr/share/mailman3-web --settings settings
After everything done tried a test mail, but didn't reach any of the inbox though mail is archived. mailman.log says message is accepted
ACCEPT: <FEE2E515-C054-41E6-9853-744D3312A137@xxxxxx.org> Nothing after this.
On smtp.log we have
Jul 29 16:11:52 2020 (16161) Peer: ('127.0.0.1', 54792) Jul 29 16:11:52 2020 (16161) ('127.0.0.1', 54792) handling connection Jul 29 16:11:52 2020 (16161) ('127.0.0.1', 54792) Data: b'LHLO lists.xxxxxxx.in' Jul 29 16:11:52 2020 (16161) ('127.0.0.1', 54792) Data: b'MAIL FROM:<abhijith@xxxxxxxxx.org>' Jul 29 16:11:52 2020 (16161) ('127.0.0.1', 54792) sender: abhijith@xxxxxxx.org Jul 29 16:11:52 2020 (16161) ('127.0.0.1', 54792) Data: b'RCPT TO:<temptest@lists.xxxxxxxxxx.in>' Jul 29 16:11:52 2020 (16161) ('127.0.0.1', 54792) recip: temptest@lists.xxxxxxxxxx.in Jul 29 16:11:52 2020 (16161) ('127.0.0.1', 54792) Data: b'DATA' Jul 29 16:11:52 2020 (16161) ('127.0.0.1', 54792) Data: b'QUIT'
Please help.
Abhijith
[1] https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/J...
[2] - https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/...
On 7/29/20 9:33 AM, Abhijith PA via Mailman-users wrote:
mailman create -o <foo@example.com> foo-bar@lists.example.com mailman import 21 foo-bar@lists.example.com path/to/config.pck
You don't need to specify an owner for mailman create. The owners will
be imported.
After everything done tried a test mail, but didn't reach any of the inbox though mail is archived. mailman.log says message is accepted
ACCEPT: <FEE2E515-C054-41E6-9853-744D3312A137@xxxxxx.org> Nothing after this.
It is surprising that no exception/traceback/SHUNTING message(s) are
logged. That would seem to say that Mailman's out runner is not running.
I think Mailman's var/ directory in the Debian package is
/var/lib/mailman3/, so what does ls -aR /var/lib/mailman3/queue show?
Is there a .pck file either in shunt/ or in out/?
what does ps -fwwu list show? There should be a lot of runner
processes. Is there one with argument --runner=out:0:1?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 29/07/20 10:38 pm, Mark Sapiro wrote:
On 7/29/20 9:33 AM, Abhijith PA via Mailman-users wrote:
mailman create -o <foo@example.com> foo-bar@lists.example.com mailman import 21 foo-bar@lists.example.com path/to/config.pck
You don't need to specify an owner for
mailman create. The owners will be imported.
Ok, noted.
After everything done tried a test mail, but didn't reach any of the inbox though mail is archived. mailman.log says message is accepted
ACCEPT: <FEE2E515-C054-41E6-9853-744D3312A137@xxxxxx.org> Nothing after this.
It is surprising that no exception/traceback/SHUNTING message(s) are logged. That would seem to say that Mailman's
outrunner is not running.
When I restarted mailman. I got,
Jul 29 16:58:21 2020 (14473) SHUNTING: 1596041901.2833998+efbeb949a9c248bae23ea6bcc644450f497a4d8d
I think Mailman's var/ directory in the Debian package is /var/lib/mailman3/, so what does
ls -aR /var/lib/mailman3/queueshow? Is there a .pck file either in shunt/ or in out/?
There is many .pck files in /var/lib/mailman3/queue/shunt and /var/lib/mailman3/queue/out. And a lot of .psv files in /var/lib/mailman3/queue/bad
what does
ps -fwwu listshow? There should be a lot of runner processes. Is there one with argument --runner=out:0:1?
Yes. I can confirm.
--a
On 7/29/20 10:16 AM, Abhijith PA via Mailman-users wrote:
When I restarted mailman. I got,
Jul 29 16:58:21 2020 (14473) SHUNTING: 1596041901.2833998+efbeb949a9c248bae23ea6bcc644450f497a4d8d
I think Mailman's var/ directory in the Debian package is /var/lib/mailman3/, so what does
ls -aR /var/lib/mailman3/queueshow? Is there a .pck file either in shunt/ or in out/?There is many .pck files in /var/lib/mailman3/queue/shunt and /var/lib/mailman3/queue/out. And a lot of .psv files in /var/lib/mailman3/queue/bad
The .pck and (presumably one) .bak files in queue/out are messages waiting to be processed by out runner, the .bak is the one currently being processed. It appears your out queue is backlogged, but that is a separate issue and may just be transient.
For every message in queue/shunt there should be a SHUNTING message and also an exception with Traceback logged in mailman.log. It is these Tracebacks we need to see to know what the issue might be. (If they're all the same exception, we only need one.)
The .psv files in queue/bad are unparseable messages. There should be a
"Skipping and preserving unparseable message:" entry in mailman.log for
each of these. The messages can be seen with mailman qfile pointing to
the .psv file. If they look like legitimate messages, it is possible a
permissions issue that caused them to be unparseable.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (2)
-
Abhijith PA -
Mark Sapiro