Search results for "Cannot connect to SMTP server"

[MM3-users] Re: Uncaught runner exception

by Wolfgang Bock

Thank you Steven for your reply! I Set smtp_server to port 25 and got a "Cannot connect ro SMTP Server on port 25", the former error message didn't show again. As I see port 25 is reseved for postfix. So I have to fiddle out how mailman3 could also use this port for sending mails out. .... Regards Wolfgang -----Ursprüngliche Nachricht----- Von: Stephen J. Turnbull <turnbull.stephen.fw(a)u.tsukuba.ac.jp> Gesendet: Montag, 6. April 2020 14:56 An: Wolfgang Bock <mailinglisten(a)wbock.de> Cc: 'mailman-users' <mailman-users(a)mailman3.org> Betreff: [MM3-users] Uncaught runner exception 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 _______________________________________________ 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/

5 years, 2 months

[MM3-users] Re: Bulk changes to delivery mode and moderation action

by Mark Sapiro

On 1/7/22 6:07 PM, David Newman wrote: > On 1/7/22 4:32 PM, Mark Sapiro wrote: > >> I suspect an issue trying to connect to the MTA to send the messages. >> This can be caused by permission errors. Check permissions on >> Mailman's var/templates/* > > Bingo. This list had regular and digest footer templates with 0644 > permissions owned by root:root, and there was an exception and traceback > for the most recent message in shunt about the permissions issue. That comes from running `mailman import21` as `root`. Always run `mailman` commands as the Mailman user. > I've changed ownership to mailman:mailman and restarted the mailman3 > service. > > As soon as I fixed this, my inbox filled with test messages... Good! >> Is there a 'Cannot connect to SMTP server ... on port ...' anywhere in >> mailman.log? > > Yes, lots. This might or might not be a different issue. It is exactly this issue which is now corrected. > As I mentioned earlier, the most recent message in shunt was from 0000 > hours today. There are many "Cannot connect" messages since then, but > none since fixing the issue above. The Cannot connect messages are from the issue of ownership of the templates and Mailman's out runner continually retrying the send. This is separate from the shunted messages. > Seems OK now. The superuser sees all posts after the unshunt action. So it appears that you ran `mailman unshunt` and the shunted messages were successfully processed, so whatever caused them to be shunted in the first place is fixed. Individual messages don't get shunted because of this template ownership issue, but it may be that digests do get shunted for this reason. -- 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

[MM3-users] Re: Bulk changes to delivery mode and moderation action

by Mark Sapiro

On 1/7/22 3:41 PM, David Newman wrote: > > There are 24 messages in the shunt queue, the most recent of which is a > digest from 0000 hours today. The test messages I sent later today are > not there. > > There are also 13 messages in the out queue. I can't read these as the > filenames appear to change on every invocation of ls. I suspect an issue trying to connect to the MTA to send the messages. This can be caused by permission errors. Check permissions on Mailman's var/templates/* >> Are there errors and tracebacks in var/logs/mailman.log? Every message in the shunt queue should have an exception and traceback logged in mailman.log. > But the Postfix log doesn't show it being distributed to me or anyone else. Is there a 'Cannot connect to SMTP server ... on port ...' anywhere in mailman.log? > Oddly, neither of the two list owner emails (me and someone else) show > this message in the archive via the admin panel. However if I log in as > the list owner directly to the archives: > > https://lists.domain.tld/archives/ > > I can see today's test posts if logged in as the list member, but do not > see the posts if logged directly into the archive as the Django superuser. That seems strange, I don't know why the superuser would not be able to see things in the archive that a list owner or member can. > The nondelivery of list mail is more serious than the archive problem, > though. Archiving is separate from delivery. messages can be archived and still fail delivery in the out runner which is what's happening here. The question is why? I suspect you have one or more 'Cannot connect to SMTP server ... on port ...' messages in mailman.log? and I suspect this is a misleading issue in this case caused by an inability to read some file in Mailman's var/templates/lists/<list_id>/en directory. I also suspect the shunted messages are from some prior condition which has possibly been fixed, but I can't be sure without exceptions and tracebacks from mailman.log (should be timestamped the same as the mod time if the shunted file). You can view them with `mailman qfile` and unshunt (reprocess) them with `mailman unshunt`. -- 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

[MM3-users] Uncaught runner exception

by Wolfgang Bock

Hello, I need your help. I got a "Uncaught runner exception: invalid literal for int() with base 10:" Referring to a discussion in Sept. 2019 with Manos Pitsidianakis "Cannot connect to SMTP server localhost on port 25" I did following: stop both postfix and mailman 3 services. Deleted all files in the /var/lib/mailman3/queue directories. Restarted both services. With following configurations: (extracts): /etc/mailman3/mailman.cfg [mta] incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver 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 ... smtp_user: smtp_pass: lmtp_host: 127.0.0.1 lmtp_port: 8024 configuration: python:mailman.config.postfix /var/log/postfix/mail.info Apr 6 00:02:22 ... postfix/postfix-script[31407]: starting the Postfix mail system Apr 6 00:02:22 ... postfix/master[31409]: daemon started -- version 3.4.8, configuration /etc/postfix Apr 6 00:03:09 ... postfix/smtpd[31462]: connect from mout-p-103.mailbox.org[80.241.56.161] Apr 6 00:03:09 ... policyd-spf[31468]: prepend Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=80.241.56.161; helo=mout-p-103.mailbox.org; envelope-from=[mail address]; receiver=<UNKNOWN> Apr 6 00:03:09 ... postfix/smtpd[31462]: D29FE138023E: client=mout-p-103.mailbox.org[80.241.56.161] Apr 6 00:03:09 ... postfix/cleanup[31471]: D29FE138023E: message-id=<6a504834-123a-60f6-3a0e-494623b74523(a)mailbox.org> Apr 6 00:03:25 ... postfix/qmgr[31411]: D29FE138023E: from=<[mail address]>, size=2811, nrcpt=1 (queue active) Apr 6 00:03:25 ... postfix/smtpd[31462]: disconnect from mout-p-103.mailbox.org[80.241.56.161] ehlo=2 starttls=1 mail=1 rcpt=1 data=1 quit=1 commands=7 Apr 6 00:03:25 ... postfix/lmtp[31481]: D29FE138023E: to=<[list address]>, relay=127.0.0.1[127.0.0.1]:8024, delay=16, delays=16/0.01/0/0.1, dsn=2.0.0, status=sent (250 Ok) Apr 6 00:03:25 ... postfix/qmgr[31411]: D29FE138023E: removed /var/log/mailman3/mailman.log Apr 06 00:02:12 2020 (31148) Master started Apr 06 00:02:13 2020 (31158) rest runner started. Apr 06 00:02:13 2020 (31150) archive runner started. Apr 06 00:02:13 2020 (31159) retry runner started. Apr 06 00:02:14 2020 (31161) virgin runner started. Apr 06 00:02:14 2020 (31154) lmtp runner started. Apr 06 00:02:14 2020 (31155) nntp runner started. Apr 06 00:02:14 2020 (31153) in runner started. Apr 06 00:02:14 2020 (31151) bounces runner started. Apr 06 00:02:15 2020 (31157) pipeline runner started. Apr 06 00:02:15 2020 (31152) command runner started. Apr 06 00:02:15 2020 (31162) digest runner started. Apr 06 00:02:16 2020 (31156) out runner started. 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: '' Apr 06 00:03:26 2020 (31156) Traceback (most recent call last): File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 173, in _one_iteration self._process_one_file(msg, msgdata) File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 266, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/lib/python3/dist-packages/mailman/runners/outgoing.py", line 93, in _dispose self._func(mlist, msg, msgdata) File "/usr/lib/python3/dist-packages/mailman/mta/deliver.py", line 77, in deliver agent = BulkDelivery(int(config.mta.max_recipients)) File "/usr/lib/python3/dist-packages/mailman/mta/bulk.py", line 50, in __init__ super().__init__() File "/usr/lib/python3/dist-packages/mailman/mta/base.py", line 45, in __init__ config.mta.smtp_host, int(config.mta.smtp_port), Any hints how to solve the problem?? Regards Wolfgang

5 years, 2 months

[MM3-users] WG: Re: Uncaught runner exception

by Wolfgang Bock

Hello Stephen, I have to apologize for misspelling your name! Sorry! Regards Wolfgang -----Ursprüngliche Nachricht----- Von: Wolfgang Bock via Mailman-users <mailman-users(a)mailman3.org> Gesendet: Montag, 6. April 2020 23:44 An: 'mailman-users' <mailman-users(a)mailman3.org> Betreff: [MM3-users] Re: Uncaught runner exception Thank you Steven for your reply! I Set smtp_server to port 25 and got a "Cannot connect ro SMTP Server on port 25", the former error message didn't show again. As I see port 25 is reseved for postfix. So I have to fiddle out how mailman3 could also use this port for sending mails out. .... Regards Wolfgang -----Ursprüngliche Nachricht----- Von: Stephen J. Turnbull <turnbull.stephen.fw(a)u.tsukuba.ac.jp> Gesendet: Montag, 6. April 2020 14:56 An: Wolfgang Bock <mailinglisten(a)wbock.de> Cc: 'mailman-users' <mailman-users(a)mailman3.org> Betreff: [MM3-users] Uncaught runner exception 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 _______________________________________________ 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/

5 years, 2 months

[MM3-users] Trying to set up mailman3 on my mail server

by Shawn Heisey

I'm having a lot of trouble with trying to set up mailman3 on my mail server. It's on an AWS instance, running Ubuntu 20.04 LTS. All software is installed from Ubuntu packages. Mailman version is 3.2.2. The problem I am trying to troubleshoot first is how this can be happening: Oct 14 11:27:26 2021 (2341) ACCEPT: <f36e1ed0-9d25-b661-9c94-4ce999f6d5fd(a)elyograg.org> Oct 14 11:27:27 2021 (2344) Cannot connect to SMTP server 127.0.0.1 on port 25 From the shell, I can "telnet localhost 25" successfully, even as the "list" user. Apparmor is disabled. The UFW firewall is enabled, which allows all traffic on the loopback interface. I disabled ipv6 at the kernel level, but had the same problem with ipv6 enabled, so I don't think ipv6 is related at all. I do not see any connections in the postfix log that correspond to the mailman connection error. From a fresh install of mailman, I created two mailing lists. Once upon a time I had those lists active on a Debian 6 machine running mailman 2.1.13 ... I copied the mailing list config from that machine over and used the "import21" facility to import the configuration into the new mailman3 install. That worked without error and I can see the lists and their members with the "mailman" command. I found instructions for integration with postfix, and added the required three config lines to the postfix config. When I try to send a message to the list, I get what I pasted above in the mailman log. I think that means the postfix integration is working, and is forwarding to mailman. I'm hoping somebody can give me some pointers, and if more information is needed for troubleshooting, let me know what is needed. I'm also having trouble with the web UI ... I thought I had found what to do with Apache, but it's having problems and I do not know what to do so it works. The UI is not super important right now, I'd like to get the lists working first. I first tried to get help on the IRC channel, but that appears to be a dead end. I did give it several hours. Thanks, Shawn

3 years, 7 months

[MM3-users] Re: mail stuck in "out" queue

by Mark Sapiro

On 12/17/24 16:58, Mark Sapiro wrote: > > You say you have removed the var/templates/list/LIST_ID/* templates, but > is there still a var/templates/list/ and a var/templates/list/LIST_ID/ > directory and are they searchable by the Mailman user? > Another indication of this issue is a log message in mailman.log saying Cannot connect to SMTP server localhost on port 25 or whatever the smtp_host: and smtp_port: settings are. This (misleading) message will appear only once at the time of the first post to the problem list or just following a restart of Mailman. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 months, 3 weeks

[MM3-users] Re: Bulk changes to delivery mode and moderation action

by David Newman

On 1/7/22 4:32 PM, Mark Sapiro wrote: > On 1/7/22 3:41 PM, David Newman wrote: >> >> There are 24 messages in the shunt queue, the most recent of which is >> a digest from 0000 hours today. The test messages I sent later today >> are not there. >> >> There are also 13 messages in the out queue. I can't read these as the >> filenames appear to change on every invocation of ls. > > > I suspect an issue trying to connect to the MTA to send the messages. > This can be caused by permission errors. Check permissions on Mailman's > var/templates/* Bingo. This list had regular and digest footer templates with 0644 permissions owned by root:root, and there was an exception and traceback for the most recent message in shunt about the permissions issue. I've changed ownership to mailman:mailman and restarted the mailman3 service. As soon as I fixed this, my inbox filled with test messages... > >>> Are there errors and tracebacks in var/logs/mailman.log? > > > Every message in the shunt queue should have an exception and traceback > logged in mailman.log. > > >> But the Postfix log doesn't show it being distributed to me or anyone >> else. > > > Is there a 'Cannot connect to SMTP server ... on port ...' anywhere in > mailman.log? Yes, lots. This might or might not be a different issue. As I mentioned earlier, the most recent message in shunt was from 0000 hours today. There are many "Cannot connect" messages since then, but none since fixing the issue above. > > >> Oddly, neither of the two list owner emails (me and someone else) show >> this message in the archive via the admin panel. However if I log in >> as the list owner directly to the archives: > > >> https://lists.domain.tld/archives/ >> >> I can see today's test posts if logged in as the list member, but do >> not see the posts if logged directly into the archive as the Django >> superuser. > > > That seems strange, I don't know why the superuser would not be able to > see things in the archive that a list owner or member can. Seems OK now. The superuser sees all posts after the unshunt action. Thanks very much for your help with this. dn > > >> The nondelivery of list mail is more serious than the archive problem, >> though. > > > Archiving is separate from delivery. messages can be archived and still > fail delivery in the out runner which is what's happening here. The > question is why? > > I suspect you have one or more 'Cannot connect to SMTP server ... on > port ...' messages in mailman.log? and I suspect this is a misleading > issue in this case caused by an inability to read some file in Mailman's > var/templates/lists/<list_id>/en directory. > > I also suspect the shunted messages are from some prior condition which > has possibly been fixed, but I can't be sure without exceptions and > tracebacks from mailman.log (should be timestamped the same as the mod > time if the shunted file). You can view them with `mailman qfile` and > unshunt (reprocess) them with `mailman unshunt`. >

3 years, 5 months

[MM3-users] Re: Emailing a list from the list server

by Mark Dadgar

On Jun 1, 2020, at 11:45 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 6/1/20 10:02 AM, Mark Dadgar wrote: >> >> I cannot email a list from an account on the list server itself (for example, programmatically by script, but also manually) using mail / mailx / mutt / etc from the command line. The emails just disappear into the ether. > > > What's in Postfix's mail.log? Jun 1 11:54:55 mail postfix/lmtp[238922]: 1F42613BEB5: to=<test3(a)pdc-racing.net>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.04, delays=0.02/0.01/0/0.02, dsn=2.0.0, status=sent (250 Ok) smtp.log: Jun 01 11:54:55 2020 (238852) Peer: ('127.0.0.1', 53402) Jun 01 11:54:55 2020 (238852) ('127.0.0.1', 53402) handling connection Jun 01 11:54:55 2020 (238852) ('127.0.0.1', 53402) Data: b'LHLO mail.pdc-racing.net' Jun 01 11:54:55 2020 (238852) ('127.0.0.1', 53402) Data: b'MAIL FROM:<mark(a)pdc-racing.net>' Jun 01 11:54:55 2020 (238852) ('127.0.0.1', 53402) sender: mark(a)pdc-racing.net Jun 01 11:54:55 2020 (238852) ('127.0.0.1', 53402) Data: b'RCPT TO:<test3(a)pdc-racing.net>' Jun 01 11:54:55 2020 (238852) ('127.0.0.1', 53402) recip: test3(a)pdc-racing.net Jun 01 11:54:55 2020 (238852) ('127.0.0.1', 53402) Data: b'DATA' Jun 01 11:54:55 2020 (238852) ('127.0.0.1', 53402) Data: b'QUIT' Jun 01 11:54:55 2020 (238852) ('127.0.0.1', 53402) connection lost Jun 01 11:54:55 2020 (238852) Connection lost during _handle_client() Test3 is a working mailman3 list. There are no posts held for moderation. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

5 years

[MM3-users] Re: signup / registration error - permissions and cert chains

by David Newman

On Dec 31, 2021, at 03:43, Victoriano Giralt <victoriano(a)uma.es> wrote: > > El viernes, 31 de diciembre de 2021 1:48:38 (CET) David Newman escribió: >> I'd like for regular (non-admin) list subscribers to be able to manage >> their subscription preferences and view list archives. > > That's a good way to go :-) > > My response is more of a (very) old sysadmin and Django user (since 2008) > hunch that a proper one based on code and documentation review, but I've been > trying to contribute several times and always (super) Mark Sapiro beats me :-) > >> If I'm reading the error correctly, this is related to an inability to >> verify the cert chain. The /etc/mailman3/settings.py file points to the >> same cert and key files used by Nginx, Postfix, and Dovecot. > > You are right in your diagnose but not in your interpretation (see my comment > below inside the traceback). It is certificate related, but not for server > TLS, but for CLIENT authentication. > > >> EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' >> EMAIL_HOST = 'localhost' >> EMAIL_PORT = 25 >> EMAIL_HOST_USER = 'dnewman(a)networktest.com' >> EMAIL_HOST_PASSWORD = 'wouldnt-you-like-to-know' >> EMAIL_USE_TLS = 'True' >> EMAIL_SSL_CERTFILE = '/etc/ssl/certs/myhost.crt' >> EMAIL_SSL_KEYFILE = '/etc/ssl/private/myhost.key' > > All these settings above are used for SENDING messages and, if I'm not > mistaken, the SSL key and cert are used for authenticating the user sending > the email. Actually, using TLS and SMTP Auth for localhost is a bit too much. > I've been configuring SMTP servers since 1990 and my mail servers just accept > mail form localhost, if they are broken into, the user and password have > already been exposed :-) > >> But this might only be for email, not Postorius/Django. > > You are right (if I also am) > >> What additional configuration is needed to allow regular users to create >> and manage their own accounts? > > I'd say that is more what is not needed (the SMTP TLS authentication) > > I'll remove the "noise". These are the tell tale lines: > >> "/opt/mailman/venv/lib/python3.9/site-packages/django/core/mail/backends/smt >> p.py", line 67, in open >> self.connection.starttls(keyfile=self.ssl_keyfile, >> certfile=self.ssl_certfile) > > The SMTP Django backend is trying to connect to the mail server to send the > Mailman account confirmation message and failing, probably because the user > Django runs as cannot open the private key (which is a very sensible thing if > that private key is the one used for the web facing TLS certificate, I can > tell you how bad in private or search for my name, wasd, apache and VMS ;-)) > > That certificate is not needed for sending email from Django, and, as I said, > not even SMTP Auth for sending via localhost. Actually, doing SMTP Auth on > port 25 is not even recommended practice. Hi Victoriano, Thanks for this. I could use some clarification on what specific changes you are suggesting. I *think* you are saying to remove the EMAIL_USE_TLS stuff and also move to another port (maybe 587), but I am not sure. Also, the reason I added the TLS in the first place was that I was getting errors without it. And I am unclear why the cert / private key pair do not work for Django when they do work OK for Postfix, Nginx, and Dovecot. Thanks for clarifying — and happy and safe 2022 to you as well! dn > > Happy, healthy, safe and well ventilated New Year to all. > > -- > Victoriano Giralt Innovation Director > Digital Transformation Vicerectorate University of Malaga > +34952131415 SPAIN > ================================================================== > Note: signature.asc is the electronic signature of present message > A: Yes. >> Q: Are you sure ? >>> A: Because it reverses the logical flow of conversation. >>>> Q: Why is top posting annoying in email ? > > > > _______________________________________________ > 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, 5 months

Search results for query "Cannot connect to SMTP server"