Search results for query "Cannot connect to SMTP server"
- 63 messages
[MM3-users] Re: Mailman3 not able to deliver emails sent through list, but moderation notifications
by Ruth Ivimey-Cook
See after:
On 26/11/2022 18:18, Mark Sapiro wrote:
> I found this article stating the the SMTP error message
>> might be misleading:
>> https://blog.tfiu.de/mailman3-cannot-connect-to-smtp-server-localhost-on-po…
>>
>>
>> How to further debug this?
>> What could be wrong with my Mailman3 instance and how to fix it?
>
> The article is relevant and mentions the most likely issue which is
> lack of permission on one or more message templates.
>
> Everything in Mailman's var/ directory should be owned by Mailman's
> user:group - normally `list:list` in Debian packages.
While this is always true for mailman-core, in some configurations the
mailman-web files are also inside the ./var/ tree, and they need to be
readable (and, for some, writable) by the process acting as webserver,
which may or may not be list:list.
In my case (a bit off-piste) I have set mailman-web it up to run as
owner=www-data, for example (I forget quite why this was needed now!!).
Regards
Ruth
--
Tel: 01223 414180
Blog: http://www.ivimey.org/blog
LinkedIn: http://uk.linkedin.com/in/ruthivimeycook/
1 year, 5 months
[MM3-users] Re: Postfix-Fehler mit mailman-web
by Jens Günther
Hey there, this already helped a lot! (I also think this is logged
double, because of another configuration problem:
https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…)
Am 26.08.23 um 15:56 schrieb Stephen J. Turnbull:
> Jens Günther writes:
>
> > Already a while I get this type of error:
> >
> > 2023-08-26T08:21:59.517986+02:00 postfix/smtpd[2843414]: connect from
> > unknown[192.168.176.6]
> > 2023-08-26T08:21:59.522238+02:00 postfix/smtpd[2843414]: NOQUEUE:
> > reject: RCPT from unknown[192.168.176.6]: 450 4.7.25 Client host
> > rejected: cannot find your hostname, [192.168.176.6];
> > from=<$admin(a)mydomain.de> to=<$recipient> proto=ESMTP helo=<mailman-web>
>
> and similar except for
>
> > from=<root(a)$mailman.mydomain.de> to=<root@localhost> proto=ESMTP
> [...]
> > Where
> > - $admin(a)mydomain.de is set in MAILMAN_ADMIN_EMAIL (mm-web)
> > and as site_owner in mailman-extra.cfg (mm-core)
> > and as DEFAULT_FROM_EMAIL in settings_local.py (mm-web)
> > - $mailman.mydomain.de is set in SERVE_FROM_DOMAIN (mm-web)
>
> The first one is probably a Django error. You can probably find a
> trace of it in the Mailman's mailman-web.log. The second one could be
> any number of things but I would guess for starters it's a cron
> report. That might show up in a cron.log or syslog or messages.
With hte log I could reproduce it and it happens, when somebody tries to
reset the password:
ERROR 2023-08-26 19:41:00,863 22 django.request Internal Server Error:
/accounts/password/reset/
Traceback (most recent call last):
File
"/usr/lib/python3.10/site-packages/django/core/handlers/exception.py",
line 55, in inner
response = get_response(request)
File
"/usr/lib/python3.10/site-packages/django/core/handlers/base.py", line
197, in _get_response
response = wrapped_callback(request, *callback_args, **callback_kwargs)
File
"/usr/lib/python3.10/site-packages/django/views/generic/base.py", line
84, in view
return self.dispatch(request, *args, **kwargs)
File "/usr/lib/python3.10/site-packages/django/utils/decorators.py",
line 46, in _wrapper
return bound_method(*args, **kwargs)
File "/usr/lib/python3.10/site-packages/allauth/decorators.py", line
20, in wrap
resp = function(request, *args, **kwargs)
File
"/usr/lib/python3.10/site-packages/django/views/generic/base.py", line
119, in dispatch
return handler(request, *args, **kwargs)
File "/usr/lib/python3.10/site-packages/allauth/account/views.py",
line 105, in post
response = self.form_valid(form)
File "/usr/lib/python3.10/site-packages/allauth/account/views.py",
line 700, in form_valid
form.save(self.request)
File "/usr/lib/python3.10/site-packages/allauth/account/forms.py",
line 580, in save
self._send_password_reset_mail(request, email, self.users, **kwargs)
File "/usr/lib/python3.10/site-packages/allauth/account/forms.py",
line 620, in _send_password_reset_mail
get_adapter(request).send_mail(
File "/usr/lib/python3.10/site-packages/allauth/account/adapter.py",
line 140, in send_mail
msg.send()
File "/usr/lib/python3.10/site-packages/django/core/mail/message.py",
line 298, in send
return self.get_connection(fail_silently).send_messages([self])
File
"/usr/lib/python3.10/site-packages/django/core/mail/backends/smtp.py",
line 131, in send_messages
sent = self._send(message)
File
"/usr/lib/python3.10/site-packages/django/core/mail/backends/smtp.py",
line 149, in _send
self.connection.sendmail(
File "/usr/lib/python3.10/smtplib.py", line 901, in sendmail
raise SMTPRecipientsRefused(senderrs)
smtplib.SMTPRecipientsRefused: {'$Accountaddress': (450, b'4.7.25 Client
host rejected: cannot find your hostname, [192.168.176.6]')}
- where $Accountaddress is the mail-address I registered with
-> it seems to me, that in this process the hostname for the
web-container is missing and can't be found, right? I mean the hostname
for the core-container must be there, since mail is accepted :-D
Thanks for looking into this.
8 months, 3 weeks
[MM3-users] Uncaught runner exception
by Stephen J. Turnbull
Wolfgang Bock via Mailman-users writes:
> smtp_host: Tried with 127.0.0.1/localhost/server ip or FQDN=servername
> smtp_port: (got a "cannot connect to SMTP Server on port 25") so I let this
> item empty ...
This is your problem. By default, it should be port 25. Apparently
there is no fallback for this in case it's left empty. (I would guess
if you commented it out, it *would* fall back to port 25.
> Apr 06 00:03:26 2020 (31153) ACCEPT:
> <6a504834-123a-60f6-3a0e-494623b74523(a)mailbox.org>
> Apr 06 00:03:26 2020 (31156) Uncaught runner exception: invalid literal for
> int() with base 10: ''
This is saying int() was called with the empty string as argument.
> Apr 06 00:03:26 2020 (31156) Traceback (most recent call last):
[intermediate frames omitted]
> File "/usr/lib/python3/dist-packages/mailman/mta/base.py", line 45, in
> __init__
> config.mta.smtp_host, int(config.mta.smtp_port),
The call to int() in the line above is getting the empty value from
the config file. Changing smtp_port to '25' (or the appropriate
value) in the config file will prevent the "Uncaught runner exception".
If localhost's smptd is not listening on port 25, as the comment above
seems to indicate, you either need to
- find out the correct value if smptd is listening on a different port,
- enable that daemon if it's not running, or
- point smtp_host at a functioning outgoing mail server if localhost
is not expected to be a mail server.
In the latter two cases you also need to make sure smtp_port is
correct for the server you use. There are some other, rarer and more
complicated, possibilities, so if your answer is "none of the above",
feel free to say so. But check those first, please.
Steve
4 years, 1 month
[MM3-users] Mails for 1 specific mailinglist not being send and looping in out queue
by Eric Broens
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
3 years, 4 months
[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/
3 years, 4 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
4 years, 4 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
4 years, 4 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/
3 years, 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!
3 years, 11 months
[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
3 years, 5 months