On 4/2/23 03:57, Guillermo Hernandez (Oldno7) via Mailman-users wrote:
I'm NOT blaming any of the parts involved... Sure, most probably is my fault. But the last upgrade shows that the process that fail is involved with mailman upgrade. The last server was working smoothly and it has higher traffic than the first I tried. It cannot be that I missed that something was not working for weeks (since the last upgrade of the OS)
It depends on what you did. Mailman's lmtp runner would only encounter this issue at startup, so unless you restarted Mailman or rebooted the server, lmtp runner would have continued without issue even if there was an underlying OS problem.
Also, I don't think the problem is with Mailman per se. The underlying issue is in the Python library socket module. Try the following in a Python 3 shell
$ python3
Python 3.9.16 (main, Dec 11 2022, 12:49:23)
[GCC 9.4.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> from socket import AF_INET6, SOCK_STREAM, socket as makesock
>>> sock = makesock(AF_INET6, SOCK_STREAM)
>>> sock.bind(("::1", 0))
>>> sock.close()
This is essentially what aiosmtpd does and I expect that sock = makesock(AF_INET6, SOCK_STREAM) will throw the OSError: [Errno 43] Protocol not supported exception.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan