No e-mail distribution after import of archive
Dear Mr. Sapiro,
on our test system we noticed the problem that after importing a mailing list archive from a Mailman system v2.1 into a Mailman system v3.3.8, e-mails are no longer distributed via this mailing list. E-mails that are written to the list find their way into the archive, but they are not sent to any member of the list.
Before the archive was imported, writing an e-mail to the list and distributing this e-mail via the list was not a problem. Unfortunately, we cannot find any indication of this issue in the log of the mailman system v3.3.8. Please help us to further analyze and solve this problem, as we are planning to import 188 archives into our new productive mailman system v3.3.8 during the next months.
With kind regards, Markus Grandpré
-- Markus Ludwig Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung und Lehre, B803, Tel: ++49 7531 88 4342
On Tue, Nov 12, 2024 at 10:34 AM Markus Grandpré < markus.grandpre@uni-konstanz.de> wrote:
Dear Mr. Sapiro,
on our test system we noticed the problem that after importing a mailing list archive from a Mailman system v2.1 into a Mailman system v3.3.8, e-mails are no longer distributed via this mailing list. E-mails that are written to the list find their way into the archive, but they are not sent to any member of the list.
Before the archive was imported, writing an e-mail to the list and distributing this e-mail via the list was not a problem. Unfortunately, we cannot find any indication of this issue in the log of the mailman system v3.3.8. Please help us to further analyze and solve this problem, as we are planning to import 188 archives into our new productive mailman system v3.3.8 during the next months.
Archives are imported into HyperKitty and should not in any way interfere with Mailman Core. From what I learnt recently, you can even import an archive into HyperKitty without having a ML in Core associated with it. So my starting point would be to look at mailman.log and see what goes in there. I could even up the debugging level if need be. For now, is there anything abnormal in mailman.log or smtp.log?
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]
Dear Mr Odhiambo,
thank you very much for your reply.
In mailman.log I see:
Nov 12 09:46:02 2024 (698086) ACCEPT: <d6723f50-7ca8-4ba9-85ef-bb5575dacd75@uni-konstanz.de> [12/Nov/2024:09:46:03 +0100] "GET /3.1/lists/import_mm3_testliste@mailman-test.uni-konstanz.de HTTP/1.1" 200 486 "-" "GNU Mailman REST client v3.3.5" [12/Nov/2024:09:46:03 +0100] "GET /3.1/lists/import_mm3_testliste@mailman-test.uni-konstanz.de/config HTTP/1.1" 200 3446 "-" "GNU Mailman REST client v3.3.5" [12/Nov/2024:09:46:03 +0100] "GET /3.1/users/markus.grandpre@uni-konstanz.de HTTP/1.1" 200 285 "-" "GNU Mailman REST client v3.3.5" [12/Nov/2024:09:46:03 +0100] "GET /3.1/lists/import_mm3_testliste.mailman-test.uni-konstanz.de/roster/owner HTTP/1.1" 200 789 "-" "GNU Mailman REST client v3.3.5" [12/Nov/2024:09:46:03 +0100] "GET /3.1/addresses/markus.grandpre@uni-konstanz.de HTTP/1.1" 200 436 "-" "GNU Mailman REST client v3.3.5" [12/Nov/2024:09:46:03 +0100] "GET /3.1/lists/import_mm3_testliste.mailman-test.uni-konstanz.de/roster/moderator HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.5" Nov 12 09:46:03 2024 (698083) HyperKitty archived message <d6723f50-7ca8-4ba9-85ef-bb5575dacd75@uni-konstanz.de> to https://mailman-test.uni-konstanz.de/mailman3/hyperkitty/list/import_mm3_tes...
In smtp.log I found:
Nov 12 09:46:02 2024 (698087) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Nov 12 09:46:02 2024 (698087) Peer: ('127.0.0.1', 57230) Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) handling connection Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) >> b'LHLO mailman-app-test.kim.uni-konstanz.de' Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) >> b'MAIL FROM:<markus.grandpre@uni-konstanz.de> SIZE=9649 BODY=8BITMIME' Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) sender: markus.grandpre@uni-konstanz.de Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) >> b'RCPT TO:<Import_mm3_testliste@mailman-test.uni-konstanz.de>' Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) recip: Import_mm3_testliste@mailman-test.uni-konstanz.de Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) >> b'DATA' Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) >> b'QUIT' Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) connection lost Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) Connection lost during _handle_client()
I have no idea why there is a "connection lost". What do you think? How can I increase the log level?
With kind regards, Markus
Am 12.11.24 um 09:38 schrieb Odhiambo Washington:
On Tue, Nov 12, 2024 at 10:34 AM Markus Grandpré < markus.grandpre@uni-konstanz.de> wrote:
Dear Mr. Sapiro,
on our test system we noticed the problem that after importing a mailing list archive from a Mailman system v2.1 into a Mailman system v3.3.8, e-mails are no longer distributed via this mailing list. E-mails that are written to the list find their way into the archive, but they are not sent to any member of the list.
Before the archive was imported, writing an e-mail to the list and distributing this e-mail via the list was not a problem. Unfortunately, we cannot find any indication of this issue in the log of the mailman system v3.3.8. Please help us to further analyze and solve this problem, as we are planning to import 188 archives into our new productive mailman system v3.3.8 during the next months.
Archives are imported into HyperKitty and should not in any way interfere with Mailman Core. From what I learnt recently, you can even import an archive into HyperKitty without having a ML in Core associated with it. So my starting point would be to look at mailman.log and see what goes in there. I could even up the debugging level if need be. For now, is there anything abnormal in mailman.log or smtp.log?
-- Markus Ludwig Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung und Lehre, B803, Tel: ++49 7531 88 4342
On Tue, Nov 12, 2024 at 11:52 AM Markus Grandpré < markus.grandpre@uni-konstanz.de> wrote:
Dear Mr Odhiambo,
thank you very much for your reply.
In mailman.log I see:
Nov 12 09:46:02 2024 (698086) ACCEPT: <d6723f50-7ca8-4ba9-85ef-bb5575dacd75@uni-konstanz.de> [12/Nov/2024:09:46:03 +0100] "GET /3.1/lists/import_mm3_testliste@mailman-test.uni-konstanz.de HTTP/1.1" 200 486 "-" "GNU Mailman REST client v3.3.5" [12/Nov/2024:09:46:03 +0100] "GET /3.1/lists/import_mm3_testliste@mailman-test.uni-konstanz.de/config HTTP/1.1" 200 3446 "-" "GNU Mailman REST client v3.3.5" [12/Nov/2024:09:46:03 +0100] "GET /3.1/users/markus.grandpre@uni-konstanz.de HTTP/1.1" 200 285 "-" "GNU Mailman REST client v3.3.5" [12/Nov/2024:09:46:03 +0100] "GET /3.1/lists/import_mm3_testliste.mailman-test.uni-konstanz.de/roster/owner HTTP/1.1" 200 789 "-" "GNU Mailman REST client v3.3.5" [12/Nov/2024:09:46:03 +0100] "GET /3.1/addresses/markus.grandpre@uni-konstanz.de HTTP/1.1" 200 436 "-" "GNU Mailman REST client v3.3.5" [12/Nov/2024:09:46:03 +0100] "GET /3.1/lists/ import_mm3_testliste.mailman-test.uni-konstanz.de/roster/moderator HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.5" Nov 12 09:46:03 2024 (698083) HyperKitty archived message <d6723f50-7ca8-4ba9-85ef-bb5575dacd75@uni-konstanz.de> to
https://mailman-test.uni-konstanz.de/mailman3/hyperkitty/list/import_mm3_tes...
Is that ALL you have from mailman.log for today,? I was expecting more - like some task runners being logged.
In smtp.log I found:
Nov 12 09:46:02 2024 (698087) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Nov 12 09:46:02 2024 (698087) Peer: ('127.0.0.1', 57230) Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) handling connection Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) >> b'LHLO mailman-app-test.kim.uni-konstanz.de' Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) >> b'MAIL FROM:<markus.grandpre@uni-konstanz.de> SIZE=9649 BODY=8BITMIME' Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) sender: markus.grandpre@uni-konstanz.de Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) >> b'RCPT TO:<Import_mm3_testliste@mailman-test.uni-konstanz.de>' Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) recip: Import_mm3_testliste@mailman-test.uni-konstanz.de Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) >> b'DATA' Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) >> b'QUIT' Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) connection lost Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) Connection lost during _handle_client()
I have no idea why there is a "connection lost". What do you think?
That 'connection lost' is normal. So there seems to be communication from mailman to your MTA. What do you see in your MTA (Postfix?) logs when you send an email to the list?
How can I increase the log level?
Actually, you do not need to, but mailman.cfg complete documentation is here: https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/config/schema.c...
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]
Dear Mr Odhiambo,
that is what i see in mail.log
- when sending an e-mail to list that owns an *imported* archive. This list does *not* distribute a received e-mail to any list member:
2024-11-12T10:42:25.921700+01:00 mailman-app-test postfix/smtpd[736246]: connect from mailout.uni-konstanz.de[134.34.240.38] 2024-11-12T10:42:25.962093+01:00 mailman-app-test postfix/smtpd[736246]: EACD47C: client=mailout.uni-konstanz.de[134.34.240.38] 2024-11-12T10:42:25.962943+01:00 mailman-app-test postfix/cleanup[736250]: EACD47C: message-id=<523343bc-3789-443e-8404-98a13d1e0adf@uni-konstanz.de> 2024-11-12T10:42:25.967472+01:00 mailman-app-test postfix/qmgr[736016]: EACD47C: from=<markus.grandpre@uni-konstanz.de>, size=9650, nrcpt=1 (queue active) 2024-11-12T10:42:25.967630+01:00 mailman-app-test postfix/smtpd[736246]: disconnect from mailout.uni-konstanz.de[134.34.240.38] ehlo=2 starttls=1 mail=1 rcpt=1 data=1 quit=1 commands=7 2024-11-12T10:42:26.059198+01:00 mailman-app-test postfix/lmtp[736251]: EACD47C: to=<Import_mm3_testliste@mailman-test.uni-konstanz.de>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.11, delays=0.02/0.01/0/0.08, dsn=2.0.0, status=sent (250 Ok) 2024-11-12T10:42:26.059525+01:00 mailman-app-test postfix/qmgr[736016]: EACD47C: removed
- when sending an e-mail to list that does *not* own an (imported) archive. This lists distributes a received e-mail to all list members:
2024-11-12T10:42:25.921700+01:00 mailman-app-test postfix/smtpd[736246]: connect from mailout.uni-konstanz.de[134.34.240.38] 2024-11-12T10:42:25.962093+01:00 mailman-app-test postfix/smtpd[736246]: EACD47C: client=mailout.uni-konstanz.de[134.34.240.38] 2024-11-12T10:42:25.962943+01:00 mailman-app-test postfix/cleanup[736250]: EACD47C: message-id=<523343bc-3789-443e-8404-98a13d1e0adf@uni-konstanz.de> 2024-11-12T10:42:25.967472+01:00 mailman-app-test postfix/qmgr[736016]: EACD47C: from=<markus.grandpre@uni-konstanz.de>, size=9650, nrcpt=1 (queue active) 2024-11-12T10:42:25.967630+01:00 mailman-app-test postfix/smtpd[736246]: disconnect from mailout.uni-konstanz.de[134.34.240.38] ehlo=2 starttls=1 mail=1 rcpt=1 data=1 quit=1 commands=7 2024-11-12T10:42:26.059198+01:00 mailman-app-test postfix/lmtp[736251]: EACD47C: to=<Import_mm3_testliste@mailman-test.uni-konstanz.de>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.11, delays=0.02/0.01/0/0.08, dsn=2.0.0, status=sent (250 Ok) 2024-11-12T10:42:26.059525+01:00 mailman-app-test postfix/qmgr[736016]: EACD47C: removed 2024-11-12T10:44:11.500683+01:00 mailman-app-test postfix/smtpd[736314]: connect from mailout.uni-konstanz.de[134.34.240.59] 2024-11-12T10:44:11.531183+01:00 mailman-app-test postfix/smtpd[736314]: 81A2B7C: client=mailout.uni-konstanz.de[134.34.240.59] 2024-11-12T10:44:11.532139+01:00 mailman-app-test postfix/cleanup[736316]: 81A2B7C: message-id=<802848fd-713b-4318-af7b-f868728edae3@uni-konstanz.de> 2024-11-12T10:44:11.535226+01:00 mailman-app-test postfix/smtpd[736314]: disconnect from mailout.uni-konstanz.de[134.34.240.59] ehlo=2 starttls=1 mail=1 rcpt=1 data=1 quit=1 commands=7 2024-11-12T10:44:11.535529+01:00 mailman-app-test postfix/qmgr[736016]: 81A2B7C: from=<markus.grandpre@uni-konstanz.de>, size=9595, nrcpt=1 (queue active) 2024-11-12T10:44:11.564063+01:00 mailman-app-test postfix/lmtp[736317]: 81A2B7C: to=<nochntest@mailman-test.uni-konstanz.de>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.04, delays=0.01/0.01/0/0.02, dsn=2.0.0, status=sent (250 Ok) 2024-11-12T10:44:11.564429+01:00 mailman-app-test postfix/qmgr[736016]: 81A2B7C: removed 2024-11-12T10:44:14.144185+01:00 mailman-app-test postfix/smtpd[736314]: connect from localhost[::1] 2024-11-12T10:44:14.149134+01:00 mailman-app-test postfix/smtpd[736314]: 245CC7C: client=localhost[::1] 2024-11-12T10:44:14.150698+01:00 mailman-app-test postfix/cleanup[736316]: 245CC7C: message-id=<802848fd-713b-4318-af7b-f868728edae3@uni-konstanz.de> 2024-11-12T10:44:14.155543+01:00 mailman-app-test postfix/qmgr[736016]: 245CC7C: from=<nochntest-bounces@mailman-test.uni-konstanz.de>, size=11569, nrcpt=2 (queue active) 2024-11-12T10:44:14.155843+01:00 mailman-app-test postfix/smtpd[736314]: disconnect from localhost[::1] ehlo=1 mail=1 rcpt=2 data=1 quit=1 commands=6 2024-11-12T10:44:15.883334+01:00 mailman-app-test postfix/smtp[736318]: 245CC7C: to=<christian.mack@uni-konstanz.de>, relay=thurn.uni-konstanz.de[134.34.240.38]:25, delay=1.7, delays=0.01/0.02/0.04/1.7, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 4XnhML1WGSz1q) 2024-11-12T10:44:15.883517+01:00 mailman-app-test postfix/smtp[736318]: 245CC7C: to=<markus.grandpre@uni-konstanz.de>, relay=thurn.uni-konstanz.de[134.34.240.38]:25, delay=1.7, delays=0.01/0.02/0.04/1.7, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 4XnhML1WGSz1q) 2024-11-12T10:44:15.883730+01:00 mailman-app-test postfix/qmgr[736016]: 245CC7C: removed
Postfix and mailman configurations for 1) and 2) are the same.
With kind regards, Markus
Am 12.11.24 um 10:27 schrieb Odhiambo Washington via Mailman-users:
On Tue, Nov 12, 2024 at 11:52 AM Markus Grandpré < markus.grandpre@uni-konstanz.de> wrote:
Dear Mr Odhiambo,
thank you very much for your reply.
In mailman.log I see:
Nov 12 09:46:02 2024 (698086) ACCEPT: <d6723f50-7ca8-4ba9-85ef-bb5575dacd75@uni-konstanz.de> [12/Nov/2024:09:46:03 +0100] "GET /3.1/lists/import_mm3_testliste@mailman-test.uni-konstanz.de HTTP/1.1" 200 486 "-" "GNU Mailman REST client v3.3.5" [12/Nov/2024:09:46:03 +0100] "GET /3.1/lists/import_mm3_testliste@mailman-test.uni-konstanz.de/config HTTP/1.1" 200 3446 "-" "GNU Mailman REST client v3.3.5" [12/Nov/2024:09:46:03 +0100] "GET /3.1/users/markus.grandpre@uni-konstanz.de HTTP/1.1" 200 285 "-" "GNU Mailman REST client v3.3.5" [12/Nov/2024:09:46:03 +0100] "GET /3.1/lists/import_mm3_testliste.mailman-test.uni-konstanz.de/roster/owner HTTP/1.1" 200 789 "-" "GNU Mailman REST client v3.3.5" [12/Nov/2024:09:46:03 +0100] "GET /3.1/addresses/markus.grandpre@uni-konstanz.de HTTP/1.1" 200 436 "-" "GNU Mailman REST client v3.3.5" [12/Nov/2024:09:46:03 +0100] "GET /3.1/lists/ import_mm3_testliste.mailman-test.uni-konstanz.de/roster/moderator HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.5" Nov 12 09:46:03 2024 (698083) HyperKitty archived message <d6723f50-7ca8-4ba9-85ef-bb5575dacd75@uni-konstanz.de> to
https://mailman-test.uni-konstanz.de/mailman3/hyperkitty/list/import_mm3_tes...
Is that ALL you have from mailman.log for today,? I was expecting more - like some task runners being logged.
In smtp.log I found:
Nov 12 09:46:02 2024 (698087) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Nov 12 09:46:02 2024 (698087) Peer: ('127.0.0.1', 57230) Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) handling connection Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) >> b'LHLO mailman-app-test.kim.uni-konstanz.de' Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) >> b'MAIL FROM:<markus.grandpre@uni-konstanz.de> SIZE=9649 BODY=8BITMIME' Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) sender: markus.grandpre@uni-konstanz.de Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) >> b'RCPT TO:<Import_mm3_testliste@mailman-test.uni-konstanz.de>' Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) recip: Import_mm3_testliste@mailman-test.uni-konstanz.de Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) >> b'DATA' Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) >> b'QUIT' Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) connection lost Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) Connection lost during _handle_client()
I have no idea why there is a "connection lost". What do you think?
That 'connection lost' is normal. So there seems to be communication from mailman to your MTA. What do you see in your MTA (Postfix?) logs when you send an email to the list?
How can I increase the log level?
Actually, you do not need to, but mailman.cfg complete documentation is here: https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/config/schema.c...
-- Markus Ludwig Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung und Lehre, B803, Tel: ++49 7531 88 4342
On 11/12/24 00:52, Markus Grandpré wrote:
In smtp.log I found:
Nov 12 09:46:02 2024 (698087) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Nov 12 09:46:02 2024 (698087) Peer: ('127.0.0.1', 57230) Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) handling connection Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) >> b'LHLO mailman-app-test.kim.uni-konstanz.de' Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) >> b'MAIL FROM:<markus.grandpre@uni-konstanz.de> SIZE=9649 BODY=8BITMIME' Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) sender: markus.grandpre@uni-konstanz.de Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) >> b'RCPT TO:<Import_mm3_testliste@mailman-test.uni-konstanz.de>' Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) recip: Import_mm3_testliste@mailman-test.uni-konstanz.de Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) >> b'DATA' Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) >> b'QUIT' Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) connection lost Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) Connection lost during _handle_client()
I have no idea why there is a "connection lost". What do you think? How can I increase the log level?
This is delivery of the message to Mailman. connection lost is normal
and not a problem. This has nothing to do with your issue.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 11/11/24 23:33, Markus Grandpré wrote:
Dear Mr. Sapiro,
on our test system we noticed the problem that after importing a mailing list archive from a Mailman system v2.1 into a Mailman system v3.3.8, e-mails are no longer distributed via this mailing list. E-mails that are written to the list find their way into the archive, but they are not sent to any member of the list.
Before the archive was imported, writing an e-mail to the list and distributing this e-mail via the list was not a problem. Unfortunately, we cannot find any indication of this issue in the log of the mailman system v3.3.8. Please help us to further analyze and solve this problem, as we are planning to import 188 archives into our new productive mailman system v3.3.8 during the next months.
Nothing in HyperKitty should affect Mail delivery from the list. The symptom you see could result in a file in Mailman's mailman/templates/lists/<THIS.LISTS.ID>/<LC>/ directory not being readable by the Mailman user. Check ownership and permissions on everything in var/templates/
See the latter part of the thread at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/K...
Note that if this is the issue, something other than hyperkitty_import did it.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Dear Mr Sapiro,
thank you so much for your advice:
Check ownership and permissions on everything in var/templates/
fixed the issue. All pending email has been delivered immediately after i changed ownership on our Debian12 server:
# chown list:list /var/lib/mailman3/templates -R
Best regards, Markus Grandpré
Am 11/12/24 um 22:45 schrieb Mark Sapiro:
On 11/11/24 23:33, Markus Grandpré wrote:
Dear Mr. Sapiro,
on our test system we noticed the problem that after importing a mailing list archive from a Mailman system v2.1 into a Mailman system v3.3.8, e-mails are no longer distributed via this mailing list. E-mails that are written to the list find their way into the archive, but they are not sent to any member of the list.
Before the archive was imported, writing an e-mail to the list and distributing this e-mail via the list was not a problem. Unfortunately, we cannot find any indication of this issue in the log of the mailman system v3.3.8. Please help us to further analyze and solve this problem, as we are planning to import 188 archives into our new productive mailman system v3.3.8 during the next months.
Nothing in HyperKitty should affect Mail delivery from the list. The symptom you see could result in a file in Mailman's mailman/templates/lists/<THIS.LISTS.ID>/<LC>/ directory not being readable by the Mailman user. Check ownership and permissions on everything in var/templates/
See the latter part of the thread at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/ KGYZXN2QP3RWRZOQKLHD2MKUSI7H2W6B/
Note that if this is the issue, something other than hyperkitty_import did it.
-- Markus Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung, Lehre und Infrastruktur, Tel: ++49 7531 88 4342
participants (3)
-
Mark Sapiro -
Markus Grandpré -
Odhiambo Washington