Search results for query "Cannot connect to SMTP server"
- 73 messages
[MM3-users] Re: Mails for 1 specific mailinglist not being send and looping in out queue
by Eric Broens
In my mailclient it looks like the LF's have been removed.
I'll attach the log extracts to make them better readable.
Best Regards,
Eric On Saturday, January 9, 2021, 02:17:18 PM GMT+1, Eric Broens <ebroens(a)yahoo.com> wrote:
----- Forwarded Message ----- From: Eric Broens via Mailman-users <mailman-users(a)mailman3.org>To: Mailman Users <mailman-users(a)mailman3.org>Sent: Saturday, January 9, 2021, 02:14:42 PM GMT+1Subject: [MM3-users] Mails for 1 specific mailinglist not being send and looping in out queue
For some reason, the mail for 1 specific mailinglist doesn't get distributed.
It worked fine before, and no changes have been made.The mailman3 debug log shows that mailman keeps attempting to distribute the mail.
The mailman3 error log show that there is a connection failure to port 25.
A tcpdump however shows that there are *NO* further connection attempts on port 25 (postfix) to distribute this mail.
Also after stopping and starting mailman3 again, no further connection attempts to the mailserver (postfix) are being made for this mail.
Using qfile, the pck file of this mail looks fine.
New emails on this specific mailinglist are not distributed either.
For all other mailinglists on this server, and which are on the same domain, there are no problems.
Does anyone know how to get this mailinglist functioning properly again, and what is causing this issue?
Below are the relevant extracts from the log files for the particular case.
mailman smtp.log:
Jan 09 12:00:57 2021 (1571668) Peer: ('127.0.0.1', 51752)Jan 09 12:00:57 2021 (1571668) ('127.0.0.1', 51752) handling connectionJan 09 12:00:57 2021 (1571668) ('127.0.0.1', 51752) Data: b'LHLO ****'Jan 09 12:00:57 2021 (1571668) ('127.0.0.1', 51752) Data: b'MAIL FROM:<****@****>'Jan 09 12:00:57 2021 (1571668) ('127.0.0.1', 51752) sender: *****@*****Jan 09 12:00:57 2021 (1571668) ('127.0.0.1', 51752) Data: b'RCPT TO:<*****@*****>'Jan 09 12:00:57 2021 (1571668) ('127.0.0.1', 51752) recip: ******@********Jan 09 12:00:57 2021 (1571668) ('127.0.0.1', 51752) Data: b'DATA'Jan 09 12:00:57 2021 (1571668) ('127.0.0.1', 51752) Data: b'QUIT'Jan 09 12:00:57 2021 (1571668) ('127.0.0.1', 51752) connection lost...
Message has been archived properly, mailmansuite.logINFO 2021-01-09 12:01:00,277 1164814 hyperkitty.views.mailman Archived message <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> to ***
mailman error.logJan 09 12:01:00 2021 (1571670) Cannot connect to SMTP server 127.0.0.1 on port 25
mailman debug.log
Jan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: validate-authenticityJan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: mime-deleteJan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: taggerJan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: member-recipientsJan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: avoid-duplicatesJan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: cleanseJan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: cleanse-dkimJan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: cook-headersJan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: subject-prefixJan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: rfc-2369Jan 09 12:00:59 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: to-archiveJan 09 12:00:59 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: to-digestJan 09 12:00:59 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: to-usenetJan 09 12:00:59 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: after-deliveryJan 09 12:00:59 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: acknowledgeJan 09 12:00:59 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: dmarcJan 09 12:00:59 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: arc-signJan 09 12:00:59 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: to-outgoingJan 09 12:00:59 2021 (1571667) [IncomingRunner] starting oneloopJan 09 12:00:59 2021 (1571667) [IncomingRunner] ending oneloop: 0Jan 09 12:00:59 2021 (1571671) [PipelineRunner] finishing filebase: 1610190058.1544778+e952a743e8df115e8fff9c60f98b189d4800e7e6Jan 09 12:00:59 2021 (1571671) [PipelineRunner] doing periodicJan 09 12:00:59 2021 (1571671) [PipelineRunner] committing transactionJan 09 12:00:59 2021 (1571671) [PipelineRunner] checking short circuitJan 09 12:00:59 2021 (1571671) [PipelineRunner] ending oneloop: 1Jan 09 12:00:59 2021 (1571671) [PipelineRunner] starting oneloopJan 09 12:00:59 2021 (1571671) [PipelineRunner] ending oneloop: 0Jan 09 12:00:59 2021 (1571674) [VirginRunner] starting oneloopJan 09 12:00:59 2021 (1571674) [VirginRunner] ending oneloop: 0Jan 09 12:00:59 2021 (1571669) [NNTPRunner] starting oneloopJan 09 12:00:59 2021 (1571669) [NNTPRunner] ending oneloop: 0Jan 09 12:00:59 2021 (1571675) [DigestRunner] starting oneloopJan 09 12:00:59 2021 (1571675) [DigestRunner] ending oneloop: 0Jan 09 12:01:00 2021 (1571670) [OutgoingRunner] starting oneloopJan 09 12:01:00 2021 (1571670) [OutgoingRunner] processing filebase: 1610190059.1591551+dcfcb22d5156b0a4d4267eabf83c5bb68f945e41Jan 09 12:01:00 2021 (1571670) [OutgoingRunner] processing onefileJan 09 12:01:00 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>Jan 09 12:01:00 2021 (1571664) [ArchiveRunner] starting oneloopJan 09 12:01:00 2021 (1571664) [ArchiveRunner] processing filebase: 1610190059.1079752+2644b9a3eab17d52203a2c2648a1db5ff146eb6dJan 09 12:01:00 2021 (1571664) [ArchiveRunner] processing onefileJan 09 12:01:00 2021 (1571666) [CommandRunner] starting oneloopJan 09 12:01:00 2021 (1571666) [CommandRunner] ending oneloop: 0Jan 09 12:01:00 2021 (1571670) [OutgoingRunner] finishing filebase: 1610190059.1591551+dcfcb22d5156b0a4d4267eabf83c5bb68f945e41Jan 09 12:01:00 2021 (1571670) [OutgoingRunner] doing periodicJan 09 12:01:00 2021 (1571670) [OutgoingRunner] committing transactionJan 09 12:01:00 2021 (1571670) [OutgoingRunner] checking short circuitJan 09 12:01:00 2021 (1571670) [OutgoingRunner] ending oneloop: 1Jan 09 12:01:00 2021 (1571670) [OutgoingRunner] starting oneloopJan 09 12:01:00 2021 (1571670) [OutgoingRunner] processing filebase: 1610190060.1351898+91420b755194277d1236a36b6e2195eff547c8b0Jan 09 12:01:00 2021 (1571670) [OutgoingRunner] processing onefileJan 09 12:01:00 2021 (1571667) [IncomingRunner] starting oneloopJan 09 12:01:00 2021 (1571667) [IncomingRunner] ending oneloop: 0Jan 09 12:01:00 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:41 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:41 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:41 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:41 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:41 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:42 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:42 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:42 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:42 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:42 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>......Jan 09 14:06:30 2021 (1601275) [outgoing] <function deliver at 0x7f038df80ea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...
Thanks in advance,Eric
_______________________________________________
Mailman-users mailing list -- mailman-users(a)mailman3.org
To unsubscribe send an email to mailman-users-leave(a)mailman3.org
https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
4 years, 5 months
[MM3-users] Re: Migration from 2.1 to 3
by brunol＠agro.uba.ar
> What do you mean by constantly appearing? Do you mean endlessly
repeating or that they just repeat a number of times equal to the number
of expected recipients of the post?
Sorry, I meant endlessly repeating.
This is a piece from debug after sending an email to the list from a recipient that does not need moderation:
Dec 27 11:41:10 2019 (11473) [outgoing] <function deliver at 0x7f7c3de987b8>: <CAOwJ5NX+K3CORg9riHc2T1dbdKZLZojHT1MVs44Wd3SbTJju6A(a)mail.gmail.com>
Dec 27 11:41:10 2019 (11473) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7f7c3de264a8>
Dec 27 11:41:10 2019 (11468) [BounceRunner] starting oneloop
Dec 27 11:41:10 2019 (11468) [BounceRunner] ending oneloop: 0
Dec 27 11:41:10 2019 (11473) Cannot connect to SMTP server 127.0.0.1 on port 25
Dec 27 11:41:10 2019 (11473) [OutgoingRunner] finishing filebase: 1577457670.0510046+6fe6039c1b0b65672aade3bfced1aca2fe8afa16
Dec 27 11:41:10 2019 (11473) [OutgoingRunner] doing periodic
Dec 27 11:41:10 2019 (11473) [OutgoingRunner] committing transaction
Dec 27 11:41:10 2019 (11473) [OutgoingRunner] checking short circuit
Dec 27 11:41:10 2019 (11473) [OutgoingRunner] ending oneloop: 1
Dec 27 11:41:10 2019 (11473) [OutgoingRunner] starting oneloop
Dec 27 11:41:10 2019 (11473) [OutgoingRunner] processing filebase: 1577457670.5784276+6f5454f4a57da4dc15912e789f0719be53c74616
Dec 27 11:41:10 2019 (11473) [OutgoingRunner] processing onefile
Dec 27 11:41:10 2019 (11473) [outgoing] <function deliver at 0x7f7c3de987b8>: <CAOwJ5NX+K3CORg9riHc2T1dbdKZLZojHT1MVs44Wd3SbTJju6A(a)mail.gmail.com>
Dec 27 11:41:10 2019 (11473) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7f7c3de26e10>
Dec 27 11:41:10 2019 (11470) [IncomingRunner] starting oneloop
Dec 27 11:41:10 2019 (11470) [IncomingRunner] ending oneloop: 0
Dec 27 11:41:10 2019 (11473) [OutgoingRunner] finishing filebase: 1577457670.5784276+6f5454f4a57da4dc15912e789f0719be53c74616
Dec 27 11:41:10 2019 (11473) [OutgoingRunner] doing periodic
Dec 27 11:41:10 2019 (11473) [OutgoingRunner] committing transaction
Dec 27 11:41:10 2019 (11473) [OutgoingRunner] checking short circuit
Dec 27 11:41:10 2019 (11473) [OutgoingRunner] ending oneloop: 1
Dec 27 11:41:10 2019 (11473) [OutgoingRunner] starting oneloop
Dec 27 11:41:10 2019 (11473) [OutgoingRunner] processing filebase: 1577457670.61572+a2844469514ead14dedcee020ad8e2a34036f8ef
Dec 27 11:41:10 2019 (11473) [OutgoingRunner] processing onefile
Dec 27 11:41:10 2019 (11473) [outgoing] <function deliver at 0x7f7c3de987b8>: <CAOwJ5NX+K3CORg9riHc2T1dbdKZLZojHT1MVs44Wd3SbTJju6A(a)mail.gmail.com>
Dec 27 11:41:10 2019 (11473) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7f7c3de26f28>
Dec 27 11:41:10 2019 (11473) [OutgoingRunner] finishing filebase: 1577457670.61572+a2844469514ead14dedcee020ad8e2a34036f8ef
Dec 27 11:41:10 2019 (11473) [OutgoingRunner] doing periodic
Dec 27 11:41:10 2019 (11473) [OutgoingRunner] committing transaction
Dec 27 11:41:10 2019 (11473) [OutgoingRunner] checking short circuit
Dec 27 11:41:10 2019 (11473) [OutgoingRunner] ending oneloop: 1
Dec 27 11:41:10 2019 (11473) [OutgoingRunner] starting oneloop
Dec 27 11:41:10 2019 (11473) [OutgoingRunner] processing filebase: 1577457670.6512213+13fe7854257bb1a494f797f480cb10733bd440ac
Dec 27 11:41:10 2019 (11473) [OutgoingRunner] processing onefile
Dec 27 11:41:10 2019 (11473) [outgoing] <function deliver at 0x7f7c3de987b8>: <CAOwJ5NX+K3CORg9riHc2T1dbdKZLZojHT1MVs44Wd3SbTJju6A(a)mail.gmail.com>
Dec 27 11:41:10 2019 (11473) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7f7c3dd44390>
Dec 27 11:41:10 2019 (11469) [CommandRunner] starting oneloop
Dec 27 11:41:10 2019 (11469) [CommandRunner] ending oneloop: 0
This is endlessly repeating with different filebase
5 years, 5 months
[MM3-users] Re: Migration from 2.1 to 3
by Mark Sapiro
On 12/27/19 6:54 AM, brunol(a)agro.uba.ar wrote:
>> What do you mean by constantly appearing? Do you mean endlessly
> repeating or that they just repeat a number of times equal to the number
> of expected recipients of the post?
>
> Sorry, I meant endlessly repeating.
>
> This is a piece from debug after sending an email to the list from a recipient that does not need moderation:
>
> Dec 27 11:41:10 2019 (11473) [outgoing] <function deliver at 0x7f7c3de987b8>: <CAOwJ5NX+K3CORg9riHc2T1dbdKZLZojHT1MVs44Wd3SbTJju6A(a)mail.gmail.com>
> Dec 27 11:41:10 2019 (11473) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7f7c3de264a8>
> Dec 27 11:41:10 2019 (11468) [BounceRunner] starting oneloop
> Dec 27 11:41:10 2019 (11468) [BounceRunner] ending oneloop: 0
> Dec 27 11:41:10 2019 (11473) Cannot connect to SMTP server 127.0.0.1 on port 25
This message is logged only once, but the issue occurs every time.
deliver is getting a socket.error exception on its attempt to connect to
the MTA. Thus, sending of this message fails and the message is requeued
and the process repeats.
Is an MTA listening on 127.0.0.1 on port 25?
The only question is if we can't send this mail, how can we send the
'held for moderation' notices?. These are sent the same way.
> Dec 27 11:41:10 2019 (11473) [OutgoingRunner] finishing filebase: 1577457670.0510046+6fe6039c1b0b65672aade3bfced1aca2fe8afa16
> Dec 27 11:41:10 2019 (11473) [OutgoingRunner] doing periodic
> Dec 27 11:41:10 2019 (11473) [OutgoingRunner] committing transaction
> Dec 27 11:41:10 2019 (11473) [OutgoingRunner] checking short circuit
> Dec 27 11:41:10 2019 (11473) [OutgoingRunner] ending oneloop: 1
> Dec 27 11:41:10 2019 (11473) [OutgoingRunner] starting oneloop
> Dec 27 11:41:10 2019 (11473) [OutgoingRunner] processing filebase: 1577457670.5784276+6f5454f4a57da4dc15912e789f0719be53c74616
> Dec 27 11:41:10 2019 (11473) [OutgoingRunner] processing onefile
> Dec 27 11:41:10 2019 (11473) [outgoing] <function deliver at 0x7f7c3de987b8>: <CAOwJ5NX+K3CORg9riHc2T1dbdKZLZojHT1MVs44Wd3SbTJju6A(a)mail.gmail.com>
> Dec 27 11:41:10 2019 (11473) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7f7c3de26e10>
> Dec 27 11:41:10 2019 (11470) [IncomingRunner] starting oneloop
> Dec 27 11:41:10 2019 (11470) [IncomingRunner] ending oneloop: 0
> Dec 27 11:41:10 2019 (11473) [OutgoingRunner] finishing filebase: 1577457670.5784276+6f5454f4a57da4dc15912e789f0719be53c74616
> Dec 27 11:41:10 2019 (11473) [OutgoingRunner] doing periodic
> Dec 27 11:41:10 2019 (11473) [OutgoingRunner] committing transaction
> Dec 27 11:41:10 2019 (11473) [OutgoingRunner] checking short circuit
> Dec 27 11:41:10 2019 (11473) [OutgoingRunner] ending oneloop: 1
> Dec 27 11:41:10 2019 (11473) [OutgoingRunner] starting oneloop
> Dec 27 11:41:10 2019 (11473) [OutgoingRunner] processing filebase: 1577457670.61572+a2844469514ead14dedcee020ad8e2a34036f8ef
> Dec 27 11:41:10 2019 (11473) [OutgoingRunner] processing onefile
> Dec 27 11:41:10 2019 (11473) [outgoing] <function deliver at 0x7f7c3de987b8>: <CAOwJ5NX+K3CORg9riHc2T1dbdKZLZojHT1MVs44Wd3SbTJju6A(a)mail.gmail.com>
> Dec 27 11:41:10 2019 (11473) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7f7c3de26f28>
> Dec 27 11:41:10 2019 (11473) [OutgoingRunner] finishing filebase: 1577457670.61572+a2844469514ead14dedcee020ad8e2a34036f8ef
> Dec 27 11:41:10 2019 (11473) [OutgoingRunner] doing periodic
> Dec 27 11:41:10 2019 (11473) [OutgoingRunner] committing transaction
> Dec 27 11:41:10 2019 (11473) [OutgoingRunner] checking short circuit
> Dec 27 11:41:10 2019 (11473) [OutgoingRunner] ending oneloop: 1
> Dec 27 11:41:10 2019 (11473) [OutgoingRunner] starting oneloop
> Dec 27 11:41:10 2019 (11473) [OutgoingRunner] processing filebase: 1577457670.6512213+13fe7854257bb1a494f797f480cb10733bd440ac
> Dec 27 11:41:10 2019 (11473) [OutgoingRunner] processing onefile
> Dec 27 11:41:10 2019 (11473) [outgoing] <function deliver at 0x7f7c3de987b8>: <CAOwJ5NX+K3CORg9riHc2T1dbdKZLZojHT1MVs44Wd3SbTJju6A(a)mail.gmail.com>
> Dec 27 11:41:10 2019 (11473) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7f7c3dd44390>
> Dec 27 11:41:10 2019 (11469) [CommandRunner] starting oneloop
> Dec 27 11:41:10 2019 (11469) [CommandRunner] ending oneloop: 0
>
> This is endlessly repeating with different filebase
> _______________________________________________
> Mailman-users mailing list -- mailman-users(a)mailman3.org
> To unsubscribe send an email to mailman-users-leave(a)mailman3.org
> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
>
--
Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
5 years, 5 months
[MM3-users] Re: Mails for 1 specific mailinglist not being send and looping in out queue
by Eric Broens
These mails keep looping for days in the out queue and are never shunted.
Looks to me as a serious bug.
Is there anything that can be done for this?
Note that the 29 other mailinglists are working fine.
Best Regards,
Eric
On Saturday, January 9, 2021, 03:52:40 PM GMT+1, Eric Broens via Mailman-users <mailman-users(a)mailman3.org> wrote:
In my mailclient it looks like the LF's have been removed.
I'll attach the log extracts to make them better readable.
Best Regards,
Eric On Saturday, January 9, 2021, 02:17:18 PM GMT+1, Eric Broens <ebroens(a)yahoo.com> wrote:
----- Forwarded Message ----- From: Eric Broens via Mailman-users <mailman-users(a)mailman3.org>To: Mailman Users <mailman-users(a)mailman3.org>Sent: Saturday, January 9, 2021, 02:14:42 PM GMT+1Subject: [MM3-users] Mails for 1 specific mailinglist not being send and looping in out queue
For some reason, the mail for 1 specific mailinglist doesn't get distributed.
It worked fine before, and no changes have been made.The mailman3 debug log shows that mailman keeps attempting to distribute the mail.
The mailman3 error log show that there is a connection failure to port 25.
A tcpdump however shows that there are *NO* further connection attempts on port 25 (postfix) to distribute this mail.
Also after stopping and starting mailman3 again, no further connection attempts to the mailserver (postfix) are being made for this mail.
Using qfile, the pck file of this mail looks fine.
New emails on this specific mailinglist are not distributed either.
For all other mailinglists on this server, and which are on the same domain, there are no problems.
Does anyone know how to get this mailinglist functioning properly again, and what is causing this issue?
Below are the relevant extracts from the log files for the particular case.
mailman smtp.log:
Jan 09 12:00:57 2021 (1571668) Peer: ('127.0.0.1', 51752)Jan 09 12:00:57 2021 (1571668) ('127.0.0.1', 51752) handling connectionJan 09 12:00:57 2021 (1571668) ('127.0.0.1', 51752) Data: b'LHLO ****'Jan 09 12:00:57 2021 (1571668) ('127.0.0.1', 51752) Data: b'MAIL FROM:<****@****>'Jan 09 12:00:57 2021 (1571668) ('127.0.0.1', 51752) sender: *****@*****Jan 09 12:00:57 2021 (1571668) ('127.0.0.1', 51752) Data: b'RCPT TO:<*****@*****>'Jan 09 12:00:57 2021 (1571668) ('127.0.0.1', 51752) recip: ******@********Jan 09 12:00:57 2021 (1571668) ('127.0.0.1', 51752) Data: b'DATA'Jan 09 12:00:57 2021 (1571668) ('127.0.0.1', 51752) Data: b'QUIT'Jan 09 12:00:57 2021 (1571668) ('127.0.0.1', 51752) connection lost...
Message has been archived properly, mailmansuite.logINFO 2021-01-09 12:01:00,277 1164814 hyperkitty.views.mailman Archived message <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> to ***
mailman error.logJan 09 12:01:00 2021 (1571670) Cannot connect to SMTP server 127.0.0.1 on port 25
mailman debug.log
Jan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: validate-authenticityJan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: mime-deleteJan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: taggerJan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: member-recipientsJan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: avoid-duplicatesJan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: cleanseJan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: cleanse-dkimJan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: cook-headersJan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: subject-prefixJan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: rfc-2369Jan 09 12:00:59 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: to-archiveJan 09 12:00:59 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: to-digestJan 09 12:00:59 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: to-usenetJan 09 12:00:59 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: after-deliveryJan 09 12:00:59 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: acknowledgeJan 09 12:00:59 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: dmarcJan 09 12:00:59 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: arc-signJan 09 12:00:59 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: to-outgoingJan 09 12:00:59 2021 (1571667) [IncomingRunner] starting oneloopJan 09 12:00:59 2021 (1571667) [IncomingRunner] ending oneloop: 0Jan 09 12:00:59 2021 (1571671) [PipelineRunner] finishing filebase: 1610190058.1544778+e952a743e8df115e8fff9c60f98b189d4800e7e6Jan 09 12:00:59 2021 (1571671) [PipelineRunner] doing periodicJan 09 12:00:59 2021 (1571671) [PipelineRunner] committing transactionJan 09 12:00:59 2021 (1571671) [PipelineRunner] checking short circuitJan 09 12:00:59 2021 (1571671) [PipelineRunner] ending oneloop: 1Jan 09 12:00:59 2021 (1571671) [PipelineRunner] starting oneloopJan 09 12:00:59 2021 (1571671) [PipelineRunner] ending oneloop: 0Jan 09 12:00:59 2021 (1571674) [VirginRunner] starting oneloopJan 09 12:00:59 2021 (1571674) [VirginRunner] ending oneloop: 0Jan 09 12:00:59 2021 (1571669) [NNTPRunner] starting oneloopJan 09 12:00:59 2021 (1571669) [NNTPRunner] ending oneloop: 0Jan 09 12:00:59 2021 (1571675) [DigestRunner] starting oneloopJan 09 12:00:59 2021 (1571675) [DigestRunner] ending oneloop: 0Jan 09 12:01:00 2021 (1571670) [OutgoingRunner] starting oneloopJan 09 12:01:00 2021 (1571670) [OutgoingRunner] processing filebase: 1610190059.1591551+dcfcb22d5156b0a4d4267eabf83c5bb68f945e41Jan 09 12:01:00 2021 (1571670) [OutgoingRunner] processing onefileJan 09 12:01:00 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>Jan 09 12:01:00 2021 (1571664) [ArchiveRunner] starting oneloopJan 09 12:01:00 2021 (1571664) [ArchiveRunner] processing filebase: 1610190059.1079752+2644b9a3eab17d52203a2c2648a1db5ff146eb6dJan 09 12:01:00 2021 (1571664) [ArchiveRunner] processing onefileJan 09 12:01:00 2021 (1571666) [CommandRunner] starting oneloopJan 09 12:01:00 2021 (1571666) [CommandRunner] ending oneloop: 0Jan 09 12:01:00 2021 (1571670) [OutgoingRunner] finishing filebase: 1610190059.1591551+dcfcb22d5156b0a4d4267eabf83c5bb68f945e41Jan 09 12:01:00 2021 (1571670) [OutgoingRunner] doing periodicJan 09 12:01:00 2021 (1571670) [OutgoingRunner] committing transactionJan 09 12:01:00 2021 (1571670) [OutgoingRunner] checking short circuitJan 09 12:01:00 2021 (1571670) [OutgoingRunner] ending oneloop: 1Jan 09 12:01:00 2021 (1571670) [OutgoingRunner] starting oneloopJan 09 12:01:00 2021 (1571670) [OutgoingRunner] processing filebase: 1610190060.1351898+91420b755194277d1236a36b6e2195eff547c8b0Jan 09 12:01:00 2021 (1571670) [OutgoingRunner] processing onefileJan 09 12:01:00 2021 (1571667) [IncomingRunner] starting oneloopJan 09 12:01:00 2021 (1571667) [IncomingRunner] ending oneloop: 0Jan 09 12:01:00 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:41 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:41 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:41 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:41 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:41 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:42 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:42 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:42 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:42 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:42 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>......Jan 09 14:06:30 2021 (1601275) [outgoing] <function deliver at 0x7f038df80ea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...
Thanks in advance,Eric
_______________________________________________
Mailman-users mailing list -- mailman-users(a)mailman3.org
To unsubscribe send an email to mailman-users-leave(a)mailman3.org
https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
_______________________________________________
Mailman-users mailing list -- mailman-users(a)mailman3.org
To unsubscribe send an email to mailman-users-leave(a)mailman3.org
https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
4 years, 4 months
[MM3-users] Re: Pck files stuck in out queue
by Mark Sapiro
On 2/6/25 15:21, Lieuallen, Thomas Otis via Mailman-users wrote:
> Mark,
>
> There were no apparent permissions problems on templates. I was getting the ‘Cannot connect to SMTP server’ message in mailman.log.
>
> I did end up applying the patch to decorate.py and messages went through. I’ve since removed the patch, as I’m still looking for an answer and might as well let it queue up again.
Per the above, template access is definitely the problem.
> The only thing that is making me ponder at the moment is that the list owners setup a template for list:member:regular:footer in postorius. It appears that each list has a copy of that file. The modifications I see in postorius are not in their …/templates/list/<listname>/en/list:member:regular:footer.txt file. Are their modifications stored somewhere else and causing the problem?
Templates set in Postorius are stored in the database in the
postorius_emailtemplate table. At the same time an entry is made in the
template table with a uri to retrieve the template from a Postorius API.
The uri is something like
http(s)://host/mailman3/api/templates/list/LIST-ID/list:member:regular:footer
where the http(s)://host part is from the setting for
POSTORIUS_TEMPLATE_BASE_URL.
The issue is that uri is not retrievable probably because the setting
for POSTORIUS_TEMPLATE_BASE_URL is wrong.
You should look at the uris in the template table in the database and
figure out what they should be, probably by trying to retrieve one in a
browser with the scheme and host what you actually use to access
Postorius. Once you figure out what the correct uri is you can set
POSTORIUS_TEMPLATE_BASE_URL appropriately, but this won't fix the
existing template table entries. You can fix those manually in the
database or you can delete and recreate the templates in Postorius after
fixing POSTORIUS_TEMPLATE_BASE_URL and restarting the Mailman web service.
--
Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
4 months
[MM3-users] Re: Pck files stuck in out queue
by Lieuallen, Thomas Otis
Mark,
There were no apparent permissions problems on templates. I was getting the ‘Cannot connect to SMTP server’ message in mailman.log.
I did end up applying the patch to decorate.py and messages went through. I’ve since removed the patch, as I’m still looking for an answer and might as well let it queue up again.
The only thing that is making me ponder at the moment is that the list owners setup a template for list:member:regular:footer in postorius. It appears that each list has a copy of that file. The modifications I see in postorius are not in their …/templates/list/<listname>/en/list:member:regular:footer.txt file. Are their modifications stored somewhere else and causing the problem?
Thx
Tom Lieuallen
From: Mark Sapiro <mark(a)msapiro.net>
Date: Thursday, February 6, 2025 at 2:22 PM
To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org>
Subject: [MM3-users] Re: Pck files stuck in out queue
[This email originated from outside of OSU. Use caution with links and attachments.]
On 2/6/25 12:42, Lieuallen, Thomas Otis via Mailman-users wrote:
> Running Mailman 3.3.10
>
> I have 11x pck files stuck in my out queue. There tends to always be a .bak file as well. If I run ‘ls -l’, the files are continually updated and rotated through, just as fast as I can look.
Are old ones being delivered and new ones added or the same ones just
being renamed? I suspect the latter and I suspect the issue in that case
is probably due to the OUT runner trying to access a template file like
list:member:{regular|generic}:{header|footer}.txt and not having
permission. See the last two posts in the thread at
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…>
> I believe they’re all for one list. When I use ‘strings’ on one to get a hint of what’s inside, I see the list members at the bottom (recipients). One of them consistently has ‘!’ before their email address. Not sure if that’s a clue. Just no other reason to suspect that, though.
The files are python pickles and `strings` shows lots of stuff. The !
may be something in the pickle that's not part of the email address. The
way to examine these files is with the `mailman qfile` command.
--
Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
_______________________________________________
Mailman-users mailing list -- mailman-users(a)mailman3.org
To unsubscribe send an email to mailman-users-leave(a)mailman3.org
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/>
Archived at: https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…>
This message sent to lieualth(a)oregonstate.edu
4 months
[MM3-users] Re: mail stuck in "out" queue
by Kareem Zidane
Apologies for that!! Yes, this strace was on the out runner process (pid 17171) and yes, the out runner is running:
```
# ps aux | grep [r]unner=out
82 mailman 1:10 /usr/bin/python3 /usr/bin/runner -C /etc/mailman.cfg --runner=out:0:1
```
Other lists seem to work fine. Here's what I see in mailman.log, after sending two separate emails to the list:
```
Jun 09 17:36:28 2020 (85) ACCEPT: <CAAQM=w13wB6zM-gkjmUWmL26zFSF2DgNKsX3eFetzjtCVPKmCA(a)mail.gmail.com>
Jun 09 17:36:30 2020 (84) HyperKitty archived message <CAAQM=w13wB6zM-gkjmUWmL26zFSF2DgNKsX3eFetzjtCVPKmCA(a)mail.gmail.com> to https://lists.cs50.harvard.edu/hyperkitty/list/ap@lists.cs50.harvard.edu/me…
[09/Jun/2020:17:36:30 +0000] "GET /3.0/lists/ap(a)lists.cs50.harvard.edu HTTP/1.1" 200 373 "-" "GNU Mailman REST client v3.3.0"
[09/Jun/2020:17:36:30 +0000] "GET /3.0/lists/ap(a)lists.cs50.harvard.edu/config HTTP/1.1" 200 3099 "-" "GNU Mailman REST client v3.3.0"
[09/Jun/2020:17:36:30 +0000] "GET /3.0/users/kzidane(a)cs50.harvard.edu HTTP/1.1" 200 401 "-" "GNU Mailman REST client v3.3.0"
Jun 09 17:36:31 2020 (82) Cannot connect to SMTP server postfix on port 25
[09/Jun/2020:17:41:56 +0000] "GET /3.1/lists/teachers.lists.cs50.harvard.edu HTTP/1.1" 200 571 "-" "GNU Mailman REST client v3.3.0"
[09/Jun/2020:17:41:56 +0000] "GET /3.1/lists/teachers(a)lists.cs50.harvard.edu/held?count=0&page=1 HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.0"
[09/Jun/2020:17:41:56 +0000] "GET /3.1/lists/teachers(a)lists.cs50.harvard.edu/held?count=10&page=1 HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.0"
[09/Jun/2020:17:41:56 +0000] "GET /3.1/lists/teachers(a)lists.cs50.harvard.edu/requests HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.0"
[09/Jun/2020:17:41:56 +0000] "GET /3.1/lists/teachers(a)lists.cs50.harvard.edu/held?count=50&page=1 HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.0"
[09/Jun/2020:17:41:58 +0000] "GET /3.1/domains HTTP/1.1" 200 537 "-" "GNU Mailman REST client v3.3.0"
[09/Jun/2020:17:41:58 +0000] "GET /3.1/domains/lists.cs50.harvard.edu HTTP/1.1" 200 223 "-" "GNU Mailman REST client v3.3.0"
[09/Jun/2020:17:41:58 +0000] "GET /3.1/domains/lists.cs50.yale.edu HTTP/1.1" 200 207 "-" "GNU Mailman REST client v3.3.0"
[09/Jun/2020:17:41:58 +0000] "POST /3.0/lists/find HTTP/1.1" 200 478 "-" "GNU Mailman REST client v3.3.0"
Jun 09 17:42:05 2020 (85) ACCEPT: <CAC-4VT7LRb7REc39i=a8wRc50hOuB_5mSEN37ozatqp9RGNfVA(a)mail.gmail.com>
[09/Jun/2020:17:42:06 +0000] "GET /3.0/lists/ap(a)lists.cs50.harvard.edu HTTP/1.1" 200 373 "-" "GNU Mailman REST client v3.3.0"
[09/Jun/2020:17:42:06 +0000] "GET /3.0/lists/ap(a)lists.cs50.harvard.edu/config HTTP/1.1" 200 3099 "-" "GNU Mailman REST client v3.3.0"
[09/Jun/2020:17:42:06 +0000] "GET /3.0/users/kareemzidane2(a)gmail.com HTTP/1.1" 200 293 "-" "GNU Mailman REST client v3.3.0"
Jun 09 17:42:06 2020 (84) HyperKitty archived message <CAC-4VT7LRb7REc39i=a8wRc50hOuB_5mSEN37ozatqp9RGNfVA(a)mail.gmail.com> to https://lists.cs50.harvard.edu/hyperkitty/list/ap@lists.cs50.harvard.edu/me…
```
Doesn't seem there are any errors? I grep'd for errors in mailman.log and this is what I got:
```
FileNotFoundError: [Errno 2] No such file or directory: '/opt/mailman/var/lists/ap.lists.cs50.harvard.edu/digest.mmdf'
FileNotFoundError: [Errno 2] No such file or directory: '/opt/mailman/var/lists/ap.lists.cs50.harvard.edu/digest.mmdf'
FileNotFoundError: [Errno 2] No such file or directory: '/opt/mailman/var/lists/ap.lists.cs50.harvard.edu/digest.mmdf'
FileNotFoundError: [Errno 2] No such file or directory: '/opt/mailman/var/lists/ap.lists.cs50.harvard.edu/digest.mmdf'
```
No mention of the /hyperkitty/api/mailman/urls API call in mailman.log but I could confirm with tcpdump that mailman is hitting that and I was able to add some logs to the _get_url function in mailman_hyperkitty plugin and it was being called infinitely.
/opt/mailman/var/archives/hyperkitty/spool appears to be empty.
And lastly, even though emails to this particular list do not go out, they do get archived.
Thank you so much! I appreciate all the help!
5 years
[MM3-users] Re: Importing config and archives only partially succeeded?
by Mark Sapiro
On 12/13/20 7:11 AM, Eric Broens via Mailman-users wrote:
> Hi Mark,
> 1.Regarding the repeated access of /archives/api/mailman/urls seems to be related to mailman not being able to open port 25.
> This is weird because other mails have been distributed.
> The mailman log shows:Dec 12 22:16:48 2020 (1471) ACCEPT: < message id >
> Dec 12 22:16:52 2020 (1474) Cannot connect to SMTP server localhost on port 25
That message is in response to a socket.error exception in attempted
delivery. It is logged only once until there is a successful delivery,
but the message keeps being retried.
> webserver logs:<host > - - [12/Dec/2020:22:16:50 +0100] "GET /archives/api/mailman/urls ?mlist=...&key=*** HTTP/1.1" 200 64 "-" "python-requests/2.25.0"
> <host > - - [12/Dec/2020:22:16:52 +0100] "GET /archives/api/mailman/urls?mlist=...&msgid=< message id >&key=*** HTTP/1.1" 200 105 "-" "python-requests/2.25.0"
> This last entry is repeated forever (until I stop the mailserver for a few minutes, but later on this happens again for other mails too).
Those GETs are part of normal message processing. As I said, they result
from core handlers asking HyperKitty for the URL at which the message
will be archived so they can add that URL to the Archived-At: header and
maybe to a message header or footer.
Presumably the one that keeps repeating is the one message/message-id
that is throwing the socket.error and being continuously retried.
I would stop Mailman and move that one .pck or .bak file out of
Mailman's var/queue/out/ directory and then start mailman. You can then
examine the queue entry with `mailman qfile` and maybe see what the
issue is.
> 2..Regarding the mails on the archive page, for most of the lists it is solved now. So probably one of the periodic jobs fixed that.The mailinglist which showed 0 participants 0 subscribers, does show now 0 participants 66 discussions.I have checked the member tables, and the members for this mailinglist are included there.
OK.
> 3.What I notice now too is that the hourly runjobs tasks don't seem to finish.I would have to check what they exactly do. Can I somehow activate logging for these?
> mailman 300042 300016 1 08:00 ? 00:09:18 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 302158 302149 2 09:00 ? 00:09:10 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 304513 304506 2 10:00 ? 00:09:38 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 308631 308620 3 11:00 ? 00:09:29 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 312847 312832 3 12:00 ? 00:09:15 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 317343 317332 4 13:00 ? 00:09:20 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 320079 320072 7 14:00 ? 00:09:08 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 322618 322610 13 15:00 ? 00:08:54 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 325205 325198 84 16:00 ? 00:06:56 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settings
/opt/mailman/venv/bin/django-admin runjobs --list
will show you what the jobs are. The hourly jobs are
new_lists_from_mailman, thread_starting_email and update_index. The one
running long is almost certainly update_index. I would stop running the
hourly jobs until you have successfully updated the search index for all
lists.
--
Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
4 years, 5 months
[MM3-users] Re: Pck files stuck in out queue
by Lieuallen, Thomas Otis
I ended up emailing the list. That email got stuck as well. So, I removed their template – and the message went through. So, that appears to have been the problem. But, not sure why.
Thank you
Tom Lieuallen
From: Lieuallen, Thomas Otis via Mailman-users <mailman-users(a)mailman3.org>
Date: Thursday, February 6, 2025 at 3:25 PM
To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org>
Subject: [MM3-users] Re: Pck files stuck in out queue
[This email originated from outside of OSU. Use caution with links and attachments.]
Mark,
There were no apparent permissions problems on templates. I was getting the ‘Cannot connect to SMTP server’ message in mailman.log.
I did end up applying the patch to decorate.py and messages went through. I’ve since removed the patch, as I’m still looking for an answer and might as well let it queue up again.
The only thing that is making me ponder at the moment is that the list owners setup a template for list:member:regular:footer in postorius. It appears that each list has a copy of that file. The modifications I see in postorius are not in their …/templates/list/<listname>/en/list:member:regular:footer.txt file. Are their modifications stored somewhere else and causing the problem?
Thx
Tom Lieuallen
From: Mark Sapiro <mark(a)msapiro.net>
Date: Thursday, February 6, 2025 at 2:22 PM
To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org>
Subject: [MM3-users] Re: Pck files stuck in out queue
[This email originated from outside of OSU. Use caution with links and attachments.]
On 2/6/25 12:42, Lieuallen, Thomas Otis via Mailman-users wrote:
> Running Mailman 3.3.10
>
> I have 11x pck files stuck in my out queue. There tends to always be a .bak file as well. If I run ‘ls -l’, the files are continually updated and rotated through, just as fast as I can look.
Are old ones being delivered and new ones added or the same ones just
being renamed? I suspect the latter and I suspect the issue in that case
is probably due to the OUT runner trying to access a template file like
list:member:{regular|generic}:{header|footer}.txt and not having
permission. See the last two posts in the thread at
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…><https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…>
> I believe they’re all for one list. When I use ‘strings’ on one to get a hint of what’s inside, I see the list members at the bottom (recipients). One of them consistently has ‘!’ before their email address. Not sure if that’s a clue. Just no other reason to suspect that, though.
The files are python pickles and `strings` shows lots of stuff. The !
may be something in the pickle that's not part of the email address. The
way to examine these files is with the `mailman qfile` command.
--
Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
_______________________________________________
Mailman-users mailing list -- mailman-users(a)mailman3.org
To unsubscribe send an email to mailman-users-leave(a)mailman3.org
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…><https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/>
Archived at: https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…><https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…>
This message sent to lieualth(a)oregonstate.edu
_______________________________________________
Mailman-users mailing list -- mailman-users(a)mailman3.org
To unsubscribe send an email to mailman-users-leave(a)mailman3.org
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/>
Archived at: https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…>
This message sent to lieualth(a)oregonstate.edu
4 months
[MM3-users] Re: Importing config and archives only partially succeeded?
by Eric Broens
Hi Mark,
1.Regarding the repeated access of /archives/api/mailman/urls seems to be related to mailman not being able to open port 25.
This is weird because other mails have been distributed.
The mailman log shows:Dec 12 22:16:48 2020 (1471) ACCEPT: < message id >
Dec 12 22:16:52 2020 (1474) Cannot connect to SMTP server localhost on port 25
webserver logs:<host > - - [12/Dec/2020:22:16:50 +0100] "GET /archives/api/mailman/urls ?mlist=...&key=*** HTTP/1.1" 200 64 "-" "python-requests/2.25.0"
<host > - - [12/Dec/2020:22:16:52 +0100] "GET /archives/api/mailman/urls?mlist=...&msgid=< message id >&key=*** HTTP/1.1" 200 105 "-" "python-requests/2.25.0"
This last entry is repeated forever (until I stop the mailserver for a few minutes, but later on this happens again for other mails too).
2..Regarding the mails on the archive page, for most of the lists it is solved now. So probably one of the periodic jobs fixed that.The mailinglist which showed 0 participants 0 subscribers, does show now 0 participants 66 discussions.I have checked the member tables, and the members for this mailinglist are included there.
3.What I notice now too is that the hourly runjobs tasks don't seem to finish.I would have to check what they exactly do. Can I somehow activate logging for these?
mailman 300042 300016 1 08:00 ? 00:09:18 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 302158 302149 2 09:00 ? 00:09:10 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 304513 304506 2 10:00 ? 00:09:38 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 308631 308620 3 11:00 ? 00:09:29 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 312847 312832 3 12:00 ? 00:09:15 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 317343 317332 4 13:00 ? 00:09:20 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 320079 320072 7 14:00 ? 00:09:08 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 322618 322610 13 15:00 ? 00:08:54 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 325205 325198 84 16:00 ? 00:06:56 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settings
Best Regards,Eric On Sunday, December 13, 2020, 06:29:19 AM GMT+1, Mark Sapiro <mark(a)msapiro.net> wrote:
On 12/12/20 7:40 PM, Eric Broens via Mailman-users wrote:
> There are no messages in var/archives/hyperkitty/spool/. At this time of the night (4:40 AM local time), there is no incoming mail.
I'm not sure what is causing the repeated access of
/archives/api/mailman/urls... This call comes from Mailman core in order
to request the URL at which a message will be archived. It is called
from mailman/src/mailman/handlers/rfc_2369.py when adding the
Archived-At: header and from mailman/src/mailman/handlers/decorate.py in
order to get the hyperkitty_url replacement value.
I don't understand why it would be called repeatedly for the same
message. Are there any clues in mailman.log.
> I just noticed when clicking on "All Threads" or "Threads by month", the emails are displayed. The statistic however shows that there were no mails in the past month, while there actually are.When clicking "Recent", "Most Active", etc. the page shows "No discussions this month (yet)."
What if you look at "threads by month" and select the current month?
> Another observation. For one list, which is one of the more active ones, the bar diagram is not empty, while showing 0 participants and 0 discussions (see attached screenshot).This one however shows the mailthreads when opening the list.
I think the basic issue is when you see no messages, HyperKitty, for
whatever reason thinks there are no current messages. I'm not sure, but
if there are recent posts, are they all in threads started more than 30
days ago?
As far as all the participants/discussions counts being zero, I think
one of the periodic jobs will fix that (possibly the daily
recent_threads_cache job)
--
Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
_______________________________________________
Mailman-users mailing list -- mailman-users(a)mailman3.org
To unsubscribe send an email to mailman-users-leave(a)mailman3.org
https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
4 years, 5 months