Hello.
I am setting up a new mailman3 server (debian 11). mailman3-full is installed on the same server as postfix (our MTA).
There is just one test mailing list now. When I send a message to it (I am a subscriber), mailman3 accepts the message through LMTP. Both the postfix log and mailman.log confirm this.
Postfix log: Aug 14 03:21:25 mail postfix/lmtp[4097036]: 44E49272437D: to=<testlist@cmi.ac.in>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.15, delays=0.02/0.03/0.01/0.09, dsn=2.0.0, status=sent (250 Ok)
mailman.log: Aug 14 03:21:26 2022 (4096856) ACCEPT: <Yvgc3WsoFlpZbypw@cmi.ac.in>
(The digest.mmdf file shows the test message I sent. Hence mailman3 has received the message from postfix.)
However, after this, the postfix log does not show any attempt by mailman3 to send the message to the list members.
The following runners have started (after the most recent mailman3 restart) Aug 14 03:19:53 2022 (4096853) archive runner started. Aug 14 03:19:53 2022 (4096863) retry runner started. Aug 14 03:19:53 2022 (4096862) rest runner started. Aug 14 03:19:54 2022 (4096855) command runner started. Aug 14 03:19:54 2022 (4096854) bounces runner started. Aug 14 03:19:55 2022 (4096860) pipeline runner started. Aug 14 03:19:55 2022 (4096866) digest runner started. Aug 14 03:19:55 2022 (4096858) nntp runner started. Aug 14 03:19:55 2022 (4096857) lmtp runner started. Aug 14 03:19:55 2022 (4096865) virgin runner started. Aug 14 03:19:56 2022 (4096856) in runner started. Aug 14 03:19:57 2022 (4096859) out runner started.
However, I get the following line each time I do a restart Aug 14 03:19:57 2022 (4096859) Cannot connect to SMTP server localhost on port 587 I tried to specify the name of the postfix server, though it runs on the same machine as mailman3, and the different ports : 25, 465 and 587; they all raise the same error.
Following <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/runners/doc...>, I tried to create an outgoing test runner, but that resulted in the following errors.
from mailman.runners.outgoing import OutgoingRunner from mailman.testing.helpers import make_testable_runner outgoing = make_testable_runner(OutgoingRunner, 'out') Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/usr/lib/python3/dist-packages/mailman/testing/helpers.py", line 92, in make_testable_runner return EmptyingRunner(name) File "/usr/lib/python3/dist-packages/mailman/testing/helpers.py", line 79, in __init__ super().__init__(*args, **kws) File "/usr/lib/python3/dist-packages/mailman/runners/outgoing.py", line 53, in __init__ super().__init__(slice, numslices) File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 63, in __init__ section = getattr(config, 'runner.' + name) File "/usr/lib/python3/dist-packages/mailman/config/config.py", line 123, in __getattr__ return getattr(self._config, name) AttributeError: 'NoneType' object has no attribute 'runner.out'
Here are the lines in mailman.cfg referring to smtp smtp_secure_mode : starttls smtp_host: localhost smtp_port: 587
If you could suggest how I could fix this issue, it would be great.
Thank you. Manoj.
On 8/13/22 15:14, mkummini@cmi.ac.in wrote:
However, I get the following line each time I do a restart Aug 14 03:19:57 2022 (4096859) Cannot connect to SMTP server localhost on port 587 I tried to specify the name of the postfix server, though it runs on the same machine as mailman3, and the different ports : 25, 465 and 587; they all raise the same error.
You only see this message once at startup because it is only issued once until there is a successful delivery.
This error can occur for reasons other than an inability to connect to the smtp server. In particular, if there are errors in decorating the message with a header and/or a footer because of permissions or other problems in retrieving a list:member:regular:header or list:member:regular:footer template, this will occur.
Have you put templates in Mailman's var/templates directory (possibly
named /var/lib/mailman/templates in the debian package). If so, can the
Mailman user (I think list in a debian package) find and read them?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 8/13/22 15:57, Mark Sapiro wrote:
Have you put templates in Mailman's var/templates directory (possibly named /var/lib/mailman/templates in the debian package). If so, can the Mailman user (I think
listin a debian package) find and read them?
I think that should be /var/lib/mailman3/templates in the debian package. Also, all that directory and all its subordinate directories and files should be user:group list:list.
If you ever ran Mailman core as root and not as user list, this can
create things that list can't read.
See these threads: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/K..., https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/5... and https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/K... and perhaps others from this search https://lists.mailman3.org/archives/search?q=Cannot+connect+to+SMTP+server
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Thank you! ownership and permissions of the template files was the problem.
Manoj.
participants (2)
-
Mark Sapiro -
mkummini＠cmi.ac.in