MM2 -> MM3 Migration: listinfo page
I have migrated from MM2 to MM3. However, writing HTML is not one of my strengths. I need to edit my MM2 listinfo page to:
a. Remove everything below the "Subscribing to LISTNAME" heading and below that add a link to the new http://WEBSERVER/accounts/signup/ which ideally should open on a new browser tab. b. Add a link to the new archives at https://WEBSERVER/archives/list/$list_id/
For those who have migrated from MM2 to MM3, does someone have an elegantly modified listinfo page they are willing to share?
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)
On 3/8/23 02:21, Odhiambo Washington wrote:
For those who have migrated from MM2 to MM3, does someone have an elegantly modified listinfo page they are willing to share?
I remove the MM 2.1 list, but leave the archives. Instead of having any kind of listinfo page, I put a redirect in Apache for each migrated list. E.g.
RedirectMatch permanent /mailman/listinfo/mailman-users(/.*)?$ \
https://mail.python.org/mailman3/lists/mailman-users.python.org/For archives, I add a note to archives/private/<listname>/index.html. See https://mail.python.org/pipermail/mailman-users/ for an example. This works for public archives, but not for private archives because there is no longer a list to use for private archive authentication.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Wed, Mar 8, 2023 at 6:16 PM Mark Sapiro <mark@msapiro.net> wrote:
On 3/8/23 02:21, Odhiambo Washington wrote:
For those who have migrated from MM2 to MM3, does someone have an
elegantly
modified listinfo page they are willing to share?
I remove the MM 2.1 list, but leave the archives. Instead of having any kind of listinfo page, I put a redirect in Apache for each migrated list. E.g.
RedirectMatch permanent /mailman/listinfo/mailman-users(/.*)?$ \ https://mail.python.org/mailman3/lists/mailman-users.python.org/For archives, I add a note to archives/private/<listname>/index.html. See https://mail.python.org/pipermail/mailman-users/ for an example. This works for public archives, but not for private archives because there is no longer a list to use for private archive authentication.
I'd rather not touch the MM2.1 domain because references have been made to it in publications. What I am struggling with is the listinfo.html file:
https://lists.kictanet.or.ke/mailman/listinfo/kictanet
I am struggling to add reference to the MM3 subscription link user the " Subscribe to KICTANet by filling out the following form:" The HTML code to insert there beats me :)
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)
On 2023-03-09 13:49:09 +0300 (+0300), Odhiambo Washington wrote: [...]
I'd rather not touch the MM2.1 domain because references have been made to it in publications. What I am struggling with is the listinfo.html file:
https://lists.kictanet.or.ke/mailman/listinfo/kictanetI am struggling to add reference to the MM3 subscription link user the " Subscribe to KICTANet by filling out the following form:" The HTML code to insert there beats me :)
Redirecting the listinfo pages to your Postorius interface should be sufficient to keep those URLs which are referred to in publications working. We do basically the same thing Mark mentioned, for the reasons you say you don't want to:
https://opendev.org/opendev/system-config/src/commit/ae7884a/playbooks/roles...
If someone follows a link to the old MM2 https://lists.opendev.org/cgi-bin/mailman/listinfo/service-discuss URL they get redirected to https://lists.opendev.org/mailman3/lists/service-discuss.lists.opendev.org/ so that there's no risk they'll try to use the old MM2 subscription form.
Jeremy Stanley
I created a new list using via the form. I sent a test message to the new list and it appears in the list archive. However I am not receiving the distribution.
What should I check for please?
Thank you ahead of time!
Are you having issues with only this list or all lists?
Did you configure and test smtp configuration?
Check for mailman and smtp log files, usually placed in /var/log/mailman3/
On Thu, Mar 9, 2023 at 4:51 PM Christian via Mailman-users < mailman-users@mailman3.org> wrote:
I created a new list using via the form. I sent a test message to the new list and it appears in the list archive. However I am not receiving the distribution.
What should I check for please?
Thank you ahead of time!
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/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/...
This message sent to zaheer.psg@gmail.com
--
*Zaheer Abbas*
*Cell:+44-740-5511766*
*Personal*
- Web: www.zaheerabbas.info <http://www.zaheerabbas.info> * *'SAVE WATER **~ **SAVE ENERGY* ~ *~ **SAVE EARTH*
I am only having issues with the new list.
Below are logfile entries
Smtp.log
++++++
Mar 09 20:57:09 2023 (9401) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin)
Mar 09 20:57:09 2023 (9401) Peer: ('127.0.0.1', 35982)
Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) handling connection
Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) >> b'LHLO zarathustra.ccalternatives.org'
Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) >> b'MAIL FROM:<christian@naturalintelligence.us> SIZE=3653'
Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) sender: christian@naturalintelligence.us
Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) >> b'RCPT TO:<redlatinleg@lists.ccalternatives.org>'
Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) recip: redlatinleg@lists.ccalternatives.org
Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) >> b'DATA'
Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) >> b'QUIT'
Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) connection lost
Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) Connection lost during _handle_client()
Access.log
++++++++
127.0.0.1 - - [09/Mar/2023:13:08:22 -0800] "GET /archives/list/redlatinleg@lists.ccalternatives.org/recent-threads HTTP/1.0" 200 4676 "https://lists.ccalternatives.org/archives/list/redlatinleg@lists.ccalternati..." "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/110.0.0.0 Safari/537.36"
127.0.0.1 - - [09/Mar/2023:13:08:22 -0800] "GET /archives/list/redlatinleg@lists.ccalternatives.org/favorites HTTP/1.0" 200 58 "https://lists.ccalternatives.org/archives/list/redlatinleg@lists.ccalternati..." "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/110.0.0.0 Safari/537.36"
127.0.0.1 - - [09/Mar/2023:13:08:22 -0800] "GET /archives/list/redlatinleg@lists.ccalternatives.org/top-threads HTTP/1.0" 200 4676 "https://lists.ccalternatives.org/archives/list/redlatinleg@lists.ccalternati..." "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/110.0.0.0 Safari/537.36"
127.0.0.1 - - [09/Mar/2023:13:08:22 -0800] "GET /archives/list/redlatinleg@lists.ccalternatives.org/posted-to HTTP/1.0" 200 54 "https://lists.ccalternatives.org/archives/list/redlatinleg@lists.ccalternati..." "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/110.0.0.0 Safari/537.36"
Mailman.log
++++++++
Mar 09 20:57:09 2023 (9400) ACCEPT: <032101d952c9$caf09990$60d1ccb0$@naturalintelligence.us>
Mar 09 13:03:42 2023 (9397) HyperKitty archived message <032101d952c9$caf09990$60d1ccb0$@naturalintelligence.us> to https://lists.ccalternatives.org/archives/list/redlatinleg@lists.ccalternati...
[09/Mar/2023:21:03:42 +0000] "GET /3.1/lists/redlatinleg@lists.ccalternatives.org HTTP/1.1" 200 497 "-" "GNU Mailman REST client v3.3.3"
[09/Mar/2023:21:03:42 +0000] "GET /3.1/lists/redlatinleg@lists.ccalternatives.org/config HTTP/1.1" 200 3805 "-" "GNU Mailman REST client v3.3.3"
[09/Mar/2023:21:03:42 +0000] "GET /3.1/addresses/cs@safecomputing.org HTTP/1.1" 200 402 "-" "GNU Mailman REST client v3.3.3"
[09/Mar/2023:21:03:42 +0000] "GET /3.1/lists/redlatinleg.lists.ccalternatives.org/roster/owner HTTP/1.1" 200 665 "-" "GNU Mailman REST client v3.3.3"
[09/Mar/2023:21:03:42 +0000] "GET /3.1/lists/redlatinleg.lists.ccalternatives.org/roster/moderator HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.3"
[09/Mar/2023:21:03:42 +0000] "GET /3.1/users/christian@naturalintelligence.us HTTP/1.1" 200 297 "-" "GNU Mailman REST client v3.3.3"
[09/Mar/2023:21:08:22 +0000] "GET /3.1/users/58f1e71ff425473d935fda2a7f9c2171 HTTP/1.1" 200 395 "-" "GNU Mailman REST client v3.3.3"
mailmansuite.log
++++++++++++
File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django_mailman3/lib/paginator.py", line 56, in count
return self.function(count=0, page=1).total_sizeFile "/opt/mailman/mm/venv/lib/python3.7/site-packages/postorius/views/list.py", line 962, in _get_list_page
advertised=advertised, mail_host=mail_host, count=count, page=page)File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailmanclient/client.py", line 210, in get_list_page
return Page(self._connection, url, MailingList, count, page)File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailmanclient/restbase/page.py", line 37, in __init__
self._create_page()File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailmanclient/restbase/page.py", line 62, in _create_page
response, content = self._connection.call(self._build_url())File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailmanclient/restbase/connection.py", line 169, in call
'Could not connect to Mailman API: ', repr(e))mailmanclient.restbase.connection.MailmanConnectionError: ('Could not connect to Mailman API: ', 'ConnectionError(MaxRetryError("HTTPConnectionPool(host=\'localhost\', port=8001): Max retries exceeded with url: /3.1/lists?advertised=true&count=0&page=1 (Caused by NewConnectionError(\'<urllib3.connection.HTTPConnection object at 0x7f910b1d7da0>: Failed to establish a new connection: [Errno 111] Connection refused\'))"))')
ERROR 2023-03-08 13:52:33,078 623 django.request Service Unavailable: /mailman3/lists/
ERROR 2023-03-08 13:52:33,078 623 django.request Service Unavailable: /mailman3/lists/
INFO 2023-03-08 14:12:32,804 5421 hyperkitty.views.mailman Archived message <01e001d9520a$3ca64320$b5f2c960$@sewagesludgeactionnetwork.com> to https://lists.ccalternatives.org/archives/list/ssan@lists.ccalternatives.org...
INFO 2023-03-08 14:16:54,400 5423 hyperkitty.views.mailman Archived message <01d801d95207$e34e52b0$a9eaf810$@sewagesludgeactionnetwork.com> to https://lists.ccalternatives.org/archives/list/ssan@lists.ccalternatives.org...
INFO 2023-03-08 15:01:16,764 8917 hyperkitty.views.mailman Archived message <021201d95210$d2818c00$7784a400$@safecomputing.org> to https://lists.ccalternatives.org/archives/list/medialist@lists.ccalternative...
ERROR 2023-03-08 17:18:00,624 8915 django.security.DisallowedHost Invalid HTTP_HOST header: 'www.vsooth.com'. You may need to add 'www.vsooth.com' to ALLOWED_HOSTS.
ERROR 2023-03-09 06:45:21,849 8916 django.security.DisallowedHost Invalid HTTP_HOST header: 'icook.tw'. You may need to add 'icook.tw' to ALLOWED_HOSTS.
INFO 2023-03-09 07:46:33,940 8915 hyperkitty.lib.mailman Imported the new list redlatinleg@lists.ccalternatives.org from Mailman
INFO 2023-03-09 08:01:35,590 8916 hyperkitty.views.mailman Archived message <02ab01d9529f$967afae0$c370f0a0$@naturalintelligence.us> to https://lists.ccalternatives.org/archives/list/redlatinleg@lists.ccalternati...
INFO 2023-03-09 08:27:34,189 8919 hyperkitty.views.mailman Archived message <02c301d952a3$37279c70$a576d550$@naturalintelligence.us> to https://lists.ccalternatives.org/archives/list/redlatinleg@lists.ccalternati...
INFO 2023-03-09 08:50:56,941 8916 hyperkitty.views.mailman Archived message <02cc01d952a6$7bdfbed0$739f3c70$@naturalintelligence.us> to https://lists.ccalternatives.org/archives/list/redlatinleg@lists.ccalternati...
INFO 2023-03-09 13:03:42,385 8916 hyperkitty.views.mailman Archived message <032101d952c9$caf09990$60d1ccb0$@naturalintelligence.us> to https://lists.ccalternatives.org/archives/list/redlatinleg@lists.ccalternati...
From: Zaheer Abbas <zaheer.psg@gmail.com> Sent: Thursday, March 9, 2023 9:00 AM To: csa@web-analysts.net; Christian <eric@safecomputing.org> Cc: mailman-users@mailman3.org Subject: Re: [MM3-users] new list not working
Are you having issues with only this list or all lists?
Did you configure and test smtp configuration?
Check for mailman and smtp log files, usually placed in /var/log/mailman3/
On Thu, Mar 9, 2023 at 4:51 PM Christian via Mailman-users <mailman-users@mailman3.org <mailto:mailman-users@mailman3.org> > wrote:
I created a new list using via the form. I sent a test message to the new list and it appears in the list archive. However I am not receiving the distribution.
What should I check for please?
Thank you ahead of time!
Mailman-users mailing list -- mailman-users@mailman3.org <mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave@mailman3.org <mailto:mailman-users-leave@mailman3.org> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/...
This message sent to zaheer.psg@gmail.com <mailto:zaheer.psg@gmail.com>
--
Zaheer Abbas
Cell:+44-740-5511766
Personal Web: www.zaheerabbas.info <http://www.zaheerabbas.info>
'SAVE WATER ~ SAVE ENERGY ~ ~ SAVE EARTH
On 3/9/23 13:26, Christian via Mailman-users wrote:
I am only having issues with the new list.
Below are logfile entries
Smtp.log
++++++
Mar 09 20:57:09 2023 (9401) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin)
Mar 09 20:57:09 2023 (9401) Peer: ('127.0.0.1', 35982)
Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) handling connection
Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) >> b'LHLO zarathustra.ccalternatives.org'
Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) >> b'MAIL FROM:<christian@naturalintelligence.us> SIZE=3653'
Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) sender: christian@naturalintelligence.us
Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) >> b'RCPT TO:<redlatinleg@lists.ccalternatives.org>'
Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) recip: redlatinleg@lists.ccalternatives.org
Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) >> b'DATA'
Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) >> b'QUIT'
Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) connection lost
Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) Connection lost during _handle_client()
This is the post being delivered to mailman and is expected.
Access.log
Irrelevant.
Mailman.log
++++++++
Mar 09 20:57:09 2023 (9400) ACCEPT: <032101d952c9$caf09990$60d1ccb0$@naturalintelligence.us>
Mar 09 13:03:42 2023 (9397) HyperKitty archived message <032101d952c9$caf09990$60d1ccb0$@naturalintelligence.us> to https://lists.ccalternatives.org/archives/list/redlatinleg@lists.ccalternati...
These are the expected messages (there seems to be a time zone difference) and in the absence of any other error type messages say the message should have been delivered to the eligible recipients. Are there any? See https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/... or the results from
mailman members -r -n enabled redlatinleg@lists.ccalternatives.org
mailmansuite.log
not relevant.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
When I ran
mailman members -r -n enabled redlatinleg@lists.ccalternatives.orgI did receive a list of subscribers for the new list I created, not just the owner or moderator.
Upon closer examination, another of my longtime working lists is also not working. Similar behavior as the new list I created in that I see the message has been archived, but not distributed to the subscribers.
-----Original Message----- From: Mark Sapiro <mark@msapiro.net> Sent: Thursday, March 9, 2023 1:44 PM To: mailman-users@mailman3.org Subject: [MM3-users] Re: new list not working
On 3/9/23 13:26, Christian via Mailman-users wrote:
I am only having issues with the new list.
Below are logfile entries
Smtp.log
++++++
Mar 09 20:57:09 2023 (9401) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin)
Mar 09 20:57:09 2023 (9401) Peer: ('127.0.0.1', 35982)
Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) handling connection
Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) >> b'LHLO zarathustra.ccalternatives.org'
Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) >> b'MAIL FROM:<christian@naturalintelligence.us> SIZE=3653'
Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) sender: christian@naturalintelligence.us
Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) >> b'RCPT TO:<redlatinleg@lists.ccalternatives.org>'
Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) recip: redlatinleg@lists.ccalternatives.org
Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) >> b'DATA'
Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) >> b'QUIT'
Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) connection lost
Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) Connection lost during _handle_client()
This is the post being delivered to mailman and is expected.
Access.log
Irrelevant.
Mailman.log
++++++++
Mar 09 20:57:09 2023 (9400) ACCEPT: <032101d952c9$caf09990$60d1ccb0$@naturalintelligence.us>
Mar 09 13:03:42 2023 (9397) HyperKitty archived message <032101d952c9$caf09990$60d1ccb0$@naturalintelligence.us> to https://lists.ccalternatives.org/archives/list/redlatinleg@lists.ccalt ernatives.org/message/PAJ5GDGGK74LWHQINB32BDV22BMR6LRQ/
These are the expected messages (there seems to be a time zone difference) and in the absence of any other error type messages say the message should have been delivered to the eligible recipients. Are there any? See https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/ CTAF4RDJ2CTNCGI7MXFYL3Q5HTGYMZH6/ or the results from
mailman members -r -n enabled redlatinleg@lists.ccalternatives.org
mailmansuite.log
not relevant.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
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/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/ ZVY3EFBA5WQKYS6E7AS475TNY6C4NJQU/
This message sent to csa@web-analysts.net
On 3/9/23 14:32, Christian via Mailman-users wrote:
When I ran
mailman members -r -n enabled redlatinleg@lists.ccalternatives.org
I did receive a list of subscribers for the new list I created, not just the owner or moderator.
Upon closer examination, another of my longtime working lists is also not working. Similar behavior as the new list I created in that I see the message has been archived, but not distributed to the subscribers.
What do your MTA logs show?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mail.log
Mar 9 22:03:30 zarathustra postfix/smtpd[27337]: connect from box.ecovillage.cc[45.79.28.18] Mar 9 22:03:30 zarathustra postfix/smtpd[27337]: 11516101258: client=box.ecovillage.cc[45.79.28.18] Mar 9 22:03:30 zarathustra postfix/cleanup[26926]: 11516101258: warning: header Subject: fifth test message from box.ecovillage.cc[45.79.28.18]; from=<christian@naturalintelligence.us> to=<redlatinleg@lists.ccalternatives.org> proto=ESMTP helo=<box.ecovillage.cc> Mar 9 22:03:30 zarathustra postfix/cleanup[26926]: 11516101258: message-id=<033101d952d3$0fe82730$2fb87590$@naturalintelligence.us> Mar 9 22:03:30 zarathustra postfix/qmgr[9973]: 11516101258: from=<christian@naturalintelligence.us>, size=3496, nrcpt=1 (queue active) Mar 9 22:03:30 zarathustra postfix/smtpd[27337]: disconnect from box.ecovillage.cc[45.79.28.18] ehlo=2 starttls=1 mail=1 rcpt=1 data=1 quit=1 commands=7 Mar 9 22:03:30 zarathustra postfix/lmtp[27338]: 11516101258: to=<redlatinleg@lists.ccalternatives.org>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.02, delays=0/0.01/0/0.01, dsn=2.0.0, status=sent (250 Ok) Mar 9 22:03:30 zarathustra postfix/qmgr[9973]: 11516101258: removed
-----Original Message----- From: Mark Sapiro <mark@msapiro.net> Sent: Thursday, March 9, 2023 2:39 PM To: mailman-users@mailman3.org Subject: [MM3-users] Re: new list not working
On 3/9/23 14:32, Christian via Mailman-users wrote:
When I ran
mailman members -r -n enabled redlatinleg@lists.ccalternatives.org
I did receive a list of subscribers for the new list I created, not just the owner or moderator.
Upon closer examination, another of my longtime working lists is also not working. Similar behavior as the new list I created in that I see the message has been archived, but not distributed to the subscribers.
What do your MTA logs show?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
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/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/ EOYMZXS4WPQGLDLVVWOGC67WY576665F/
This message sent to csa@web-analysts.net
On 3/9/23 15:49, Christian via Mailman-users wrote:
Mail.log
Mar 9 22:03:30 zarathustra postfix/smtpd[27337]: connect from box.ecovillage.cc[45.79.28.18] Mar 9 22:03:30 zarathustra postfix/smtpd[27337]: 11516101258: client=box.ecovillage.cc[45.79.28.18] Mar 9 22:03:30 zarathustra postfix/cleanup[26926]: 11516101258: warning: header Subject: fifth test message from box.ecovillage.cc[45.79.28.18]; from=<christian@naturalintelligence.us> to=<redlatinleg@lists.ccalternatives.org> proto=ESMTP helo=<box.ecovillage.cc> Mar 9 22:03:30 zarathustra postfix/cleanup[26926]: 11516101258: message-id=<033101d952d3$0fe82730$2fb87590$@naturalintelligence.us> Mar 9 22:03:30 zarathustra postfix/qmgr[9973]: 11516101258: from=<christian@naturalintelligence.us>, size=3496, nrcpt=1 (queue active) Mar 9 22:03:30 zarathustra postfix/smtpd[27337]: disconnect from box.ecovillage.cc[45.79.28.18] ehlo=2 starttls=1 mail=1 rcpt=1 data=1 quit=1 commands=7 Mar 9 22:03:30 zarathustra postfix/lmtp[27338]: 11516101258: to=<redlatinleg@lists.ccalternatives.org>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.02, delays=0/0.01/0/0.01, dsn=2.0.0, status=sent (250 Ok) Mar 9 22:03:30 zarathustra postfix/qmgr[9973]: 11516101258: removed
That's only the delivery of the post to Mailman. What about any log messages relating to messages from redlatinleg-bounces@lists.ccalternatives.org?
Also, one other thing you might check. Do these non-working lists have templates defined in postorius, in particular, one for list:member:regular:footer, and if not, are there any in Mailman's var/templates/lists/redlatinleg@lists.ccalternatives.org/ derectory that Mailman doesn't have permission to find and read?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 3/9/23 13:26, Christian via Mailman-users wrote:
Smtp.log
++++++
Mar 09 20:57:09 2023 (9401) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin)
Mar 09 20:57:09 2023 (9401) Peer: ('127.0.0.1', 35982)
Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) handling connection
Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) >> b'LHLO zarathustra.ccalternatives.org'
Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) >> b'MAIL FROM:christian@naturalintelligence.us SIZE=3653'
Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) sender: christian@naturalintelligence.us
Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) >> b'RCPT TO:redlatinleg@lists.ccalternatives.org'
Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) recip: redlatinleg@lists.ccalternatives.org
Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) >> b'DATA'
Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) >> b'QUIT'
Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) connection lost
Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) Connection lost during _handle_client()
What else is in the smtp.log? There should be messages like
<timestamp> (<pid>) <message-id> smtp to redlatinleg@lists.ccalternatives.org for nn recips, completed in n.nnn seconds
<timestamp> (<pid>) <message-id> post to redlatinleg@lists.ccalternatives.org from christian@naturalintelligence.us nnn bytes
If there aren't, try setting
[logging.smtp] level: debug
in mailman.cfg, restarting Mailman core and see what you then get in smtp.log.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
There are no such messages as you describe.
After turning on debugging I got this from a test message sent to the new list:
Mar 10 04:39:51 2023 (1005) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Mar 10 04:39:51 2023 (1005) Peer: ('127.0.0.1', 51982) Mar 10 04:39:51 2023 (1005) ('127.0.0.1', 51982) handling connection Mar 10 04:39:51 2023 (1005) ('127.0.0.1', 51982) >> b'LHLO zarathustra.ccalternatives.org' Mar 10 04:39:51 2023 (1005) ('127.0.0.1', 51982) >> b'MAIL FROM:<christian@naturalintelligence.us> SIZE=3499' Mar 10 04:39:51 2023 (1005) ('127.0.0.1', 51982) sender: christian@naturalintelligence.us Mar 10 04:39:51 2023 (1005) ('127.0.0.1', 51982) >> b'RCPT TO:<redlatinleg@lists.ccalternatives.org>' Mar 10 04:39:51 2023 (1005) ('127.0.0.1', 51982) recip: redlatinleg@lists.ccalternatives.org Mar 10 04:39:51 2023 (1005) ('127.0.0.1', 51982) >> b'DATA' Mar 10 04:39:51 2023 (1005) ('127.0.0.1', 51982) >> b'QUIT' Mar 10 04:39:51 2023 (1005) ('127.0.0.1', 51982) connection lost Mar 10 04:39:51 2023 (1005) ('127.0.0.1', 51982) Connection lost during _handle_client()
-----Original Message----- From: Mark Sapiro <mark@msapiro.net> Sent: Thursday, March 9, 2023 7:51 PM To: mailman-users@mailman3.org Subject: [MM3-users] Re: new list not working
On 3/9/23 13:26, Christian via Mailman-users wrote:
Smtp.log
++++++
Mar 09 20:57:09 2023 (9401) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin)
Mar 09 20:57:09 2023 (9401) Peer: ('127.0.0.1', 35982)
Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) handling connection
Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) >> b'LHLO zarathustra.ccalternatives.org'
Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) >> b'MAIL FROM:christian@naturalintelligence.us SIZE=3653'
Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) sender: christian@naturalintelligence.us
Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) >> b'RCPT TO:redlatinleg@lists.ccalternatives.org'
Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) recip: redlatinleg@lists.ccalternatives.org
Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) >> b'DATA'
Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) >> b'QUIT'
Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) connection lost
Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) Connection lost during _handle_client()
What else is in the smtp.log? There should be messages like
<timestamp> (<pid>) <message-id> smtp to redlatinleg@lists.ccalternatives.org for nn recips, completed in n.nnn seconds
<timestamp> (<pid>) <message-id> post to redlatinleg@lists.ccalternatives.org from christian@naturalintelligence.us nnn bytes
If there aren't, try setting
[logging.smtp] level: debug
in mailman.cfg, restarting Mailman core and see what you then get in smtp.log.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
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/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/ WPMR4JUQOQ6FMT24V3W6WWJQQU4Q6O7E/
This message sent to csa@web-analysts.net
On 3/10/23 05:07, Christian via Mailman-users wrote:
There are no such messages as you describe.
After turning on debugging I got this from a test message sent to the new list:
Mar 10 04:39:51 2023 (1005) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Mar 10 04:39:51 2023 (1005) Peer: ('127.0.0.1', 51982) Mar 10 04:39:51 2023 (1005) ('127.0.0.1', 51982) handling connection Mar 10 04:39:51 2023 (1005) ('127.0.0.1', 51982) >> b'LHLO zarathustra.ccalternatives.org' Mar 10 04:39:51 2023 (1005) ('127.0.0.1', 51982) >> b'MAIL FROM:<christian@naturalintelligence.us> SIZE=3499' Mar 10 04:39:51 2023 (1005) ('127.0.0.1', 51982) sender: christian@naturalintelligence.us Mar 10 04:39:51 2023 (1005) ('127.0.0.1', 51982) >> b'RCPT TO:<redlatinleg@lists.ccalternatives.org>' Mar 10 04:39:51 2023 (1005) ('127.0.0.1', 51982) recip: redlatinleg@lists.ccalternatives.org Mar 10 04:39:51 2023 (1005) ('127.0.0.1', 51982) >> b'DATA' Mar 10 04:39:51 2023 (1005) ('127.0.0.1', 51982) >> b'QUIT' Mar 10 04:39:51 2023 (1005) ('127.0.0.1', 51982) connection lost Mar 10 04:39:51 2023 (1005) ('127.0.0.1', 51982) Connection lost during _handle_client()
Again, that's only the post being delivered to Mailman. What comes after that in the log?
And have you checked if Mailman's out runner is running? Note that if it died for some reason and wasn't restarted or used up its restarts, restarting Mailman core won't start it. You need to stop Mailman core and then start it.
Are there files in mailman's var/queue/out/ or var/queue/shunt/ directories?
You say that only the new list and one other have this issue, but I wonder if the issue is not with specific lists, but rather with posts after a certain time.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
See below please...
-----Original Message----- From: Mark Sapiro <mark@msapiro.net> Sent: Friday, March 10, 2023 7:02 AM To: mailman-users@mailman3.org Subject: [MM3-users] Re: new list not working
On 3/10/23 05:07, Christian via Mailman-users wrote:
There are no such messages as you describe.
After turning on debugging I got this from a test message sent to the new list:
Mar 10 04:39:51 2023 (1005) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Mar 10 04:39:51 2023 (1005) Peer: ('127.0.0.1', 51982) Mar 10 04:39:51 2023 (1005) ('127.0.0.1', 51982) handling connection Mar 10 04:39:51 2023 (1005) ('127.0.0.1', 51982) >> b'LHLO zarathustra.ccalternatives.org' Mar 10 04:39:51 2023 (1005) ('127.0.0.1', 51982) >> b'MAIL FROM:<christian@naturalintelligence.us> SIZE=3499' Mar 10 04:39:51 2023 (1005) ('127.0.0.1', 51982) sender: christian@naturalintelligence.us Mar 10 04:39:51 2023 (1005) ('127.0.0.1', 51982) >> b'RCPT TO:<redlatinleg@lists.ccalternatives.org>' Mar 10 04:39:51 2023 (1005) ('127.0.0.1', 51982) recip: redlatinleg@lists.ccalternatives.org Mar 10 04:39:51 2023 (1005) ('127.0.0.1', 51982) >> b'DATA' Mar 10 04:39:51 2023 (1005) ('127.0.0.1', 51982) >> b'QUIT' Mar 10 04:39:51 2023 (1005) ('127.0.0.1', 51982) connection lost Mar 10 04:39:51 2023 (1005) ('127.0.0.1', 51982) Connection lost during _handle_client()
Again, that's only the post being delivered to Mailman. What comes after that in the log?
Mar 10 08:39:28 2023 (1005) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Mar 10 08:39:28 2023 (1005) Peer: ('127.0.0.1', 55662) Mar 10 08:39:28 2023 (1005) ('127.0.0.1', 55662) handling connection Mar 10 08:39:28 2023 (1005) ('127.0.0.1', 55662) >> b'LHLO zarathustra.ccalternatives.org' Mar 10 08:39:28 2023 (1005) ('127.0.0.1', 55662) >> b'MAIL FROM:<christian@naturalintelligence.us> SIZE=3498' Mar 10 08:39:28 2023 (1005) ('127.0.0.1', 55662) sender: christian@naturalintelligence.us Mar 10 08:39:28 2023 (1005) ('127.0.0.1', 55662) >> b'RCPT TO:<redlatinleg@lists.ccalternatives.org>' Mar 10 08:39:28 2023 (1005) ('127.0.0.1', 55662) recip: redlatinleg@lists.ccalternatives.org Mar 10 08:39:28 2023 (1005) ('127.0.0.1', 55662) >> b'DATA' Mar 10 08:39:28 2023 (1005) ('127.0.0.1', 55662) >> b'QUIT' Mar 10 08:39:28 2023 (1005) ('127.0.0.1', 55662) connection lost Mar 10 08:39:28 2023 (1005) ('127.0.0.1', 55662) Connection lost during _handle_client() Mar 10 08:44:05 2023 (1005) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Mar 10 08:44:05 2023 (1005) Peer: ('127.0.0.1', 54800) Mar 10 08:44:05 2023 (1005) ('127.0.0.1', 54800) handling connection Mar 10 08:44:05 2023 (1005) ('127.0.0.1', 54800) >> b'LHLO zarathustra.ccalternatives.org' Mar 10 08:44:05 2023 (1005) ('127.0.0.1', 54800) >> b'MAIL FROM:<> SIZE=1139191' Mar 10 08:44:05 2023 (1005) ('127.0.0.1', 54800) sender: <> Mar 10 08:44:05 2023 (1005) ('127.0.0.1', 54800) >> b'RCPT TO:<medialist-bounces+kkeys=courier-tribune.com@lists.ccalternatives.org>' Mar 10 08:44:05 2023 (1005) ('127.0.0.1', 54800) recip: medialist-bounces+kkeys=courier-tribune.com@lists.ccalternatives.org Mar 10 08:44:05 2023 (1005) ('127.0.0.1', 54800) >> b'DATA' Mar 10 08:44:05 2023 (1005) ('127.0.0.1', 54800) >> b'QUIT' Mar 10 08:44:05 2023 (1005) ('127.0.0.1', 54800) connection lost Mar 10 08:44:05 2023 (1005) ('127.0.0.1', 54800) Connection lost during _handle_client() Mar 10 08:45:15 2023 (1005) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Mar 10 08:45:15 2023 (1005) Peer: ('127.0.0.1', 38820) Mar 10 08:45:15 2023 (1005) ('127.0.0.1', 38820) handling connection Mar 10 08:45:15 2023 (1005) ('127.0.0.1', 38820) >> b'LHLO zarathustra.ccalternatives.org' Mar 10 08:45:15 2023 (1005) ('127.0.0.1', 38820) >> b'MAIL FROM:<> SIZE=1155595' Mar 10 08:45:15 2023 (1005) ('127.0.0.1', 38820) sender: <> Mar 10 08:45:15 2023 (1005) ('127.0.0.1', 38820) >> b'RCPT TO:<medialist-bounces+john.harbin=blueridgenow.com@lists.ccalternatives.org> ' Mar 10 08:45:15 2023 (1005) ('127.0.0.1', 38820) recip: medialist-bounces+john.harbin=blueridgenow.com@lists.ccalternatives.org Mar 10 08:45:15 2023 (1005) ('127.0.0.1', 38820) >> b'DATA' Mar 10 08:45:15 2023 (1005) ('127.0.0.1', 38820) >> b'QUIT' Mar 10 08:45:15 2023 (1005) ('127.0.0.1', 38820) connection lost Mar 10 08:45:15 2023 (1005) ('127.0.0.1', 38820) Connection lost during _handle_client()
And have you checked if Mailman's out runner is running? Note that if it died for some reason and wasn't restarted or used up its restarts, restarting Mailman core won't start it. You need to stop Mailman core and then start it.
OK I DID THAT
Are there files in mailman's var/queue/out/ or var/queue/shunt/ directories?
root@zarathustra:/opt/mailman/mm/var# ls -la queue/out total 4416 drwxrwx--- 2 mailman mailman 4096 Mar 10 04:44 . drwxr-xr-x 14 mailman mailman 4096 Mar 8 12:07 .. -rw-rw---- 1 mailman mailman 1126829 Mar 10 04:39 1678316345.5510073+678e72d483278a233b12cc38ebc3786fbfd50a44.bak -rw-rw---- 1 mailman mailman 1083682 Mar 8 20:00 1678334445.1113052+b43224b03f1ba2aa2610301331195b0cbaa151b7.pck -rw-rw---- 1 mailman mailman 1083744 Mar 8 20:00 1678334445.1324928+10c5ec711b7a4364407685b7899a9e8ea25a1a8b.pck -rw-rw---- 1 mailman mailman 1083680 Mar 8 20:00 1678334445.1501603+f2d2895ae7fa80ad387df77ffa17361294fe781c.pck -rw-rw---- 1 mailman mailman 2922 Mar 9 07:49 1678376944.9032273+9923c3da8724cff6ff71b585d1971a90a0ae65cb.pck -rw-rw---- 1 mailman mailman 2862 Mar 9 07:49 1678376944.9125621+2635b96fc6cd2ebb98a2c60a269d07517c1f5046.pck -rw-rw---- 1 mailman mailman 2886 Mar 9 07:57 1678377458.4585488+73f68f6f05d6ee64020e05c8ba2569378e4238f0.pck -rw-rw---- 1 mailman mailman 6600 Mar 9 07:59 1678377564.335885+63793d373c7668947ce4ef2c4a89644ba288d775.pck -rw-rw---- 1 mailman mailman 8290 Mar 9 08:25 1678379122.8619912+bfba87ac1c5e97473ea9c9645a99719d11179308.pck -rw-rw---- 1 mailman mailman 5966 Mar 9 08:48 1678380525.743866+d6f70271750015293a249f9ffae8200367eee509.pck -rw-rw---- 1 mailman mailman 6124 Mar 9 13:01 1678395691.1910245+9e087862cd317d77af8586d5390d60d483af8123.pck -rw-rw---- 1 mailman mailman 2789 Mar 9 13:31 1678397516.4386168+14bb385ad36166aef4a23e1d2b9dd92b50af254d.pck -rw-rw---- 1 mailman mailman 2752 Mar 9 13:31 1678397516.4514658+00546161e5310c988ca3b4d0be4c4a96d3295969.pck -rw-rw---- 1 mailman mailman 2321 Mar 9 13:58 1678399097.1614358+b7b3bfa9cdef9ada94045eed945862664aff065e.pck -rw-rw---- 1 mailman mailman 2390 Mar 9 13:58 1678399097.172284+7188ab4729863b3781c0890ec3b1be7de642454a.pck -rw-rw---- 1 mailman mailman 6031 Mar 9 14:07 1678399672.4968731+2caeb7c82672c9051be407b1cdb7a8b21a87d348.pck -rw-rw---- 1 mailman mailman 2095 Mar 9 14:08 1678399689.8167183+199b2da6cd1f8a00d10c1cd79ccc6cbcb4bdd503.pck -rw-rw---- 1 mailman mailman 7179 Mar 9 14:08 1678399689.8327854+a8d1dc73e5979bde43dccf48caa9bc58de575f41.pck -rw-rw---- 1 mailman mailman 8357 Mar 9 14:19 1678400356.5360696+62b6dce2428e420d6cb53c337c61db69a6fe4d44.pck -rw-rw---- 1 mailman mailman 5939 Mar 9 14:28 1678400903.3894706+d3f5dad6c67057edd0f2888e193dd71de14d2bf9.pck -rw-rw---- 1 mailman mailman 2096 Mar 10 04:43 1678452191.4875023+2e00a89aa5454f965d35a7b8be6a4f620944b8a1.pck -rw-rw---- 1 mailman mailman 7181 Mar 10 04:43 1678452191.4984088+1fd6f3aff9ef79aff269f4edc920f2424a8b35b7.pck -rw-rw---- 1 mailman mailman 6036 Mar 10 04:44 1678452252.847286+552f758b7fca32c2f082bd922f68de1f850dec2d.pck root@zarathustra:/opt/mailman/mm/var# ls -la queue/shunt total 12 drwxrwx--- 2 mailman mailman 4096 Mar 8 12:07 . drwxr-xr-x 14 mailman mailman 4096 Mar 8 12:07 .. -rw-rw---- 1 mailman mailman 447 Apr 26 2021 1619433583.1513886+2626ca223f3fc4368f6cf90fecc1e0e50705c36a.pck
You say that only the new list and one other have this issue, but I wonder if the issue is not with specific lists, but rather with posts after a certain time.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
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/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/ JNZIPCHBZIUUAO5KAQEWQX3UPZ7CZYPV/
This message sent to csa@web-analysts.net
On 3/10/23 09:03, Christian via Mailman-users wrote:
Again, that's only the post being delivered to Mailman. What comes after that in the log?
Mar 10 08:39:28 2023 (1005) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Mar 10 08:39:28 2023 (1005) Peer: ('127.0.0.1', 55662) Mar 10 08:39:28 2023 (1005) ('127.0.0.1', 55662) handling connection Mar 10 08:39:28 2023 (1005) ('127.0.0.1', 55662) >> b'LHLO zarathustra.ccalternatives.org' Mar 10 08:39:28 2023 (1005) ('127.0.0.1', 55662) >> b'MAIL FROM:<christian@naturalintelligence.us> SIZE=3498' Mar 10 08:39:28 2023 (1005) ('127.0.0.1', 55662) sender: christian@naturalintelligence.us Mar 10 08:39:28 2023 (1005) ('127.0.0.1', 55662) >> b'RCPT TO:<redlatinleg@lists.ccalternatives.org>' Mar 10 08:39:28 2023 (1005) ('127.0.0.1', 55662) recip: redlatinleg@lists.ccalternatives.org Mar 10 08:39:28 2023 (1005) ('127.0.0.1', 55662) >> b'DATA' Mar 10 08:39:28 2023 (1005) ('127.0.0.1', 55662) >> b'QUIT' Mar 10 08:39:28 2023 (1005) ('127.0.0.1', 55662) connection lost Mar 10 08:39:28 2023 (1005) ('127.0.0.1', 55662) Connection lost during _handle_client() Mar 10 08:44:05 2023 (1005) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Mar 10 08:44:05 2023 (1005) Peer: ('127.0.0.1', 54800) Mar 10 08:44:05 2023 (1005) ('127.0.0.1', 54800) handling connection Mar 10 08:44:05 2023 (1005) ('127.0.0.1', 54800) >> b'LHLO zarathustra.ccalternatives.org' Mar 10 08:44:05 2023 (1005) ('127.0.0.1', 54800) >> b'MAIL FROM:<> SIZE=1139191' Mar 10 08:44:05 2023 (1005) ('127.0.0.1', 54800) sender: <> Mar 10 08:44:05 2023 (1005) ('127.0.0.1', 54800) >> b'RCPT TO:<medialist-bounces+kkeys=courier-tribune.com@lists.ccalternatives.org>' Mar 10 08:44:05 2023 (1005) ('127.0.0.1', 54800) recip: medialist-bounces+kkeys=courier-tribune.com@lists.ccalternatives.org Mar 10 08:44:05 2023 (1005) ('127.0.0.1', 54800) >> b'DATA' Mar 10 08:44:05 2023 (1005) ('127.0.0.1', 54800) >> b'QUIT' Mar 10 08:44:05 2023 (1005) ('127.0.0.1', 54800) connection lost Mar 10 08:44:05 2023 (1005) ('127.0.0.1', 54800) Connection lost during _handle_client() Mar 10 08:45:15 2023 (1005) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Mar 10 08:45:15 2023 (1005) Peer: ('127.0.0.1', 38820) Mar 10 08:45:15 2023 (1005) ('127.0.0.1', 38820) handling connection Mar 10 08:45:15 2023 (1005) ('127.0.0.1', 38820) >> b'LHLO zarathustra.ccalternatives.org' Mar 10 08:45:15 2023 (1005) ('127.0.0.1', 38820) >> b'MAIL FROM:<> SIZE=1155595' Mar 10 08:45:15 2023 (1005) ('127.0.0.1', 38820) sender: <> Mar 10 08:45:15 2023 (1005) ('127.0.0.1', 38820) >> b'RCPT TO:<medialist-bounces+john.harbin=blueridgenow.com@lists.ccalternatives.org> ' Mar 10 08:45:15 2023 (1005) ('127.0.0.1', 38820) recip: medialist-bounces+john.harbin=blueridgenow.com@lists.ccalternatives.org Mar 10 08:45:15 2023 (1005) ('127.0.0.1', 38820) >> b'DATA' Mar 10 08:45:15 2023 (1005) ('127.0.0.1', 38820) >> b'QUIT' Mar 10 08:45:15 2023 (1005) ('127.0.0.1', 38820) connection lost Mar 10 08:45:15 2023 (1005) ('127.0.0.1', 38820) Connection lost during _handle_client()
There are no messages from the out runner process. it isn't running or it's hung.
And have you checked if Mailman's out runner is running? Note that if it died for some reason and wasn't restarted or used up its restarts, restarting Mailman core won't start it. You need to stop Mailman core and then start it.
OK I DID THAT
Did the mail start flowing?
Are there files in mailman's var/queue/out/ or var/queue/shunt/ directories?
root@zarathustra:/opt/mailman/mm/var# ls -la queue/out total 4416 drwxrwx--- 2 mailman mailman 4096 Mar 10 04:44 . drwxr-xr-x 14 mailman mailman 4096 Mar 8 12:07 .. -rw-rw---- 1 mailman mailman 1126829 Mar 10 04:39 1678316345.5510073+678e72d483278a233b12cc38ebc3786fbfd50a44.bak -rw-rw---- 1 mailman mailman 1083682 Mar 8 20:00 1678334445.1113052+b43224b03f1ba2aa2610301331195b0cbaa151b7.pck -rw-rw---- 1 mailman mailman 1083744 Mar 8 20:00 1678334445.1324928+10c5ec711b7a4364407685b7899a9e8ea25a1a8b.pck -rw-rw---- 1 mailman mailman 1083680 Mar 8 20:00 1678334445.1501603+f2d2895ae7fa80ad387df77ffa17361294fe781c.pck -rw-rw---- 1 mailman mailman 2922 Mar 9 07:49 1678376944.9032273+9923c3da8724cff6ff71b585d1971a90a0ae65cb.pck -rw-rw---- 1 mailman mailman 2862 Mar 9 07:49 1678376944.9125621+2635b96fc6cd2ebb98a2c60a269d07517c1f5046.pck -rw-rw---- 1 mailman mailman 2886 Mar 9 07:57 1678377458.4585488+73f68f6f05d6ee64020e05c8ba2569378e4238f0.pck -rw-rw---- 1 mailman mailman 6600 Mar 9 07:59 1678377564.335885+63793d373c7668947ce4ef2c4a89644ba288d775.pck -rw-rw---- 1 mailman mailman 8290 Mar 9 08:25 1678379122.8619912+bfba87ac1c5e97473ea9c9645a99719d11179308.pck -rw-rw---- 1 mailman mailman 5966 Mar 9 08:48 1678380525.743866+d6f70271750015293a249f9ffae8200367eee509.pck -rw-rw---- 1 mailman mailman 6124 Mar 9 13:01 1678395691.1910245+9e087862cd317d77af8586d5390d60d483af8123.pck -rw-rw---- 1 mailman mailman 2789 Mar 9 13:31 1678397516.4386168+14bb385ad36166aef4a23e1d2b9dd92b50af254d.pck -rw-rw---- 1 mailman mailman 2752 Mar 9 13:31 1678397516.4514658+00546161e5310c988ca3b4d0be4c4a96d3295969.pck -rw-rw---- 1 mailman mailman 2321 Mar 9 13:58 1678399097.1614358+b7b3bfa9cdef9ada94045eed945862664aff065e.pck -rw-rw---- 1 mailman mailman 2390 Mar 9 13:58 1678399097.172284+7188ab4729863b3781c0890ec3b1be7de642454a.pck -rw-rw---- 1 mailman mailman 6031 Mar 9 14:07 1678399672.4968731+2caeb7c82672c9051be407b1cdb7a8b21a87d348.pck -rw-rw---- 1 mailman mailman 2095 Mar 9 14:08 1678399689.8167183+199b2da6cd1f8a00d10c1cd79ccc6cbcb4bdd503.pck -rw-rw---- 1 mailman mailman 7179 Mar 9 14:08 1678399689.8327854+a8d1dc73e5979bde43dccf48caa9bc58de575f41.pck -rw-rw---- 1 mailman mailman 8357 Mar 9 14:19 1678400356.5360696+62b6dce2428e420d6cb53c337c61db69a6fe4d44.pck -rw-rw---- 1 mailman mailman 5939 Mar 9 14:28 1678400903.3894706+d3f5dad6c67057edd0f2888e193dd71de14d2bf9.pck -rw-rw---- 1 mailman mailman 2096 Mar 10 04:43 1678452191.4875023+2e00a89aa5454f965d35a7b8be6a4f620944b8a1.pck -rw-rw---- 1 mailman mailman 7181 Mar 10 04:43 1678452191.4984088+1fd6f3aff9ef79aff269f4edc920f2424a8b35b7.pck -rw-rw---- 1 mailman mailman 6036 Mar 10 04:44 1678452252.847286+552f758b7fca32c2f082bd922f68de1f850dec2d.pck
Was this before or after you stopped and started Mailman core. If before, what is the situation now? Is mail being delivered?
If after, is there still a
1678316345.5510073+678e72d483278a233b12cc38ebc3786fbfd50a44.bak file in
que/out? If this file is still there, it is hanging the out runner. Stop
Mailman, move this file aside and start Mailman and see if the rest of
the messages are processed. If that fixes it, there is something in that
one message causing this. You can examine it with mailman qfile. That
message arrived at Wed Mar 8 14:59:05 2023 (1678316345.5510073 is a
time stamp) and is apparently causing the problem.
If moving it aside fixes things, you can send it to me off list and I will try to figure out what the issue is.
root@zarathustra:/opt/mailman/mm/var# ls -la queue/shunt total 12 drwxrwx--- 2 mailman mailman 4096 Mar 8 12:07 . drwxr-xr-x 14 mailman mailman 4096 Mar 8 12:07 .. -rw-rw---- 1 mailman mailman 447 Apr 26 2021 1619433583.1513886+2626ca223f3fc4368f6cf90fecc1e0e50705c36a.pck
This is an old shunted message. The exception that caused it and a
traceback were written to mailman.log on April 26 2021. If you still
have that log, the exception and traceback will show what happened. In
any case, mailman qfile queue/shunt/1619433583.1513886+2626ca223f3fc4368f6cf90fecc1e0e50705c36a.pck
will show the msg and its metadata.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 3/9/23 08:51, Christian via Mailman-users wrote:
I created a new list using via the form. I sent a test message to the new list and it appears in the list archive. However I am not receiving the distribution.
What should I check for please?
Does the list have members, i.e. actual members, not just owners and moderators, and do the members have Delivery status Enabled and Delivery mode Regular. If those show as '-----' in list based preferences, then the address based preferences if any or the global preferences apply.
Also check Mailman's var/logs/mailman.log for errors resulting in shunted messages or other messages about the disposition of this message..
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 3/9/23 02:49, Odhiambo Washington wrote:
I'd rather not touch the MM2.1 domain because references have been made to it in publications. What I am struggling with is the listinfo.html file:
https://lists.kictanet.or.ke/mailman/listinfo/kictanetI am struggling to add reference to the MM3 subscription link user the " Subscribe to KICTANet by filling out the following form:" The HTML code to insert there beats me :)
Where you have
Subscribe to KICTANet by filling out the following form:<br>
replace that with
Subscribe to KICTANet <a
href="https://example.com/mailman3/lists/kictanet@example.com>here</a><br>
where https://example.com/mailman3/lists/kictanet@example.com is the URL to the Mailman3 list's info page.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Keeping this on the list.
On 3/9/23 16:54, Christian wrote:
There are no log messages relating to messages from redlatinleg-bounces@lists.ccalternatives.org
...
Mar 9 22:03:30 zarathustra postfix/cleanup[26926]: 11516101258: message-id=033101d952d3$0fe82730$2fb87590$@naturalintelligence.us
So if you grep the mail log for 033101d952d3$0fe82730$2fb87590$@naturalintelligence.us the above is the only message you see?
Is Mailman's out runner running? Are there messages in Mailman's var/queue/out/ or var/queue/shunt/ directories?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (5)
-
Christian -
Jeremy Stanley -
Mark Sapiro -
Odhiambo Washington -
Zaheer Abbas