El 2/4/23 a las 11:12, Odhiambo Washington escribió:

On Sun, Apr 2, 2023 at 11:35 AM Guillermo Hernandez (Oldno7) via Mailman-users<mailman-users@mailman3.org> wrote:

...

It seems that FreeBSD is handling IPv6 in a way that other OSs dont. It surprise me, because FreeBSD was the first OS where IPv6 was deployed, but it is what it is.

Thaks to everybody for your patience, specially Odhiambo and Mark.

@Guillermo Hernandez (Oldno7)<guillermo@querysoft.es>

Thanks for the update. However, I don't think I would entirely blame FreeBSD for this. As Mark pointed out, something did not upgrade completely. 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) This could be some quirk within your FreeBSD ports and you may need to ensure everything related to your Python version is updated. It could be... but since a year ago I configured a poudriere repository and Im updating from packages, not from ports. But this do not discards your guess Why am I saying this? I am running MM3 in a virtualenv on FreeBSD (13.1-p6) and I did upgrade to the bleeding-edge MM3 by running all components from git, and I don't have this problem you had. Not the same version exactly though. But similar enough Could you possibly fully update your Python libraries by following the entry dated 20220626 in /usr/ports/UPDATING? Could you run all the steps, do away with the workaround, and see if that fixes the issue?

I switched to python 3.9 in early 2022 (or it could be 2021?), that updating point is not applicable here. All my python apps are 3.9. And therefore it would not explain why a server which was working perfectly before this mailman3 upgrade, was falling in this strange IPv6 problem after.

PS: I don't even think many people are running MM3 on FreeBSD, leave alone from the ports.

Well... leaving FreeBSD for apparently greener paths in my servers is not something I'm planning to do. They are running some FreeBSD version since 1993... and then, they are working.  I'm not running MM3 from the ports, I installed every bit of it from python tools.

I have come to learn that even in Linux, using the distro's packages is usually problematic. Again, I don't install from any distro package Running MM3 from virtualenv is quite safe and to be honest, you can migrate your setup from where it is now to a virtualenv and you will not lose anything.

And I cannot deny it... but I'm already under one layer of virtualization... the mailman servers run in a jail environment. I don't want to add more layers if I can avoid it.

Thank you very much for your pointings.

Regards

--

Mailman's content filtering has removed the following MIME parts from this message.

Content-Type: image/png Name: firma-GHP-emails.png

Replaced multipart/alternative part with first alternative.

El 2/4/23 a las 12:57, Guillermo Hernandez (Oldno7) via Mailman-users escribió:

...

Running MM3 from virtualenv is quite safe and to be honest, you can migrate your setup from where it is now to a virtualenv and you will not lose anything.

And I cannot deny it... but I'm already under one layer of virtualization... the mailman servers run in a jail environment. I don't want to add more layers if I can avoid it.

Re-reading my own mail makes me think that the jail environment could be the guilty. I'm gonna test it controlling that IPv6 config pass trough the jail (even there is no IPv6 config -localhost is ::1-, it could be that the jailed server could not be allowed to use it). I'll tell you the results.

--

Mailman's content filtering has removed the following MIME parts from this message.

Content-Type: image/png Name: firma-GHP-emails.png

Replaced multipart/alternative part with first alternative.

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

(I left the relevant part of the previous thread at bottom to give context)

(Knowing that this could be of less interest to the majority os suscribers in this list, I write it down for someone that could be searching for a solution out there)

I you have mailman3 in a FreeBSD jailed server, and your lmtp runner stops working after mailman3.3.8 upgrade the most probably cause is the IPv6 config of the jail and the "::1" IP of the localhost.

Disclaimer: I find the next to work, but as I don't use IPv6 (and know nothing about its complexities), it could be a mistaken config. But I asume that if you have the same problem, it is in a no IPv6 aware server, otherwise you would not have this situation.

In the jail config of the parent host I configured explicitily this IPv6 IP

ip6.addr = "::2";

And in the /etc/hosts definitions of the jailed host

#::1            localhost localhost.yourserver.com ::2            localhost localhost.yourserver.com

After that, restarted the jail and the lmpt runner will work again as it's expected

And the rest of the services will work too.

Thanks for your patience.

El 3/4/23 a las 8:02, Guillermo Hernandez (Oldno7) via Mailman-users escribió:

...

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.

And you are right (ther is more down of this):

Python 3.9.16 (main, Dec 15 2022, 09:41:07) [Clang 13.0.0 (git@github.com:llvm/llvm-project.git llvmorg-13.0.0-0-gd7b669b3a on freebsd13 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) Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/usr/local/lib/python3.9/socket.py", line 232, in __init__ _socket.socket.__init__(self, family, type, proto, fileno) OSError: [Errno 43] Protocol not supported

Buuuuuut, if I do the same in the "father" server:

Python 3.9.16 (main, Dec 15 2022, 09:41:07) [Clang 13.0.0 (git@github.com:llvm/llvm-project.git llvmorg-13.0.0-0-gd7b669b3a on freebsd13 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() File "<stdin>", line 1 sock.close() IndentationError: unexpected indent sock.close()

The server can open a socket without problem. As I though previously it has to be something with the jailed envviroment. Your test had probe me right (and wrong in my jail tests). It's very valuable. I know now where I can dig more.

Thanks a lot

--

Mailman's content filtering has removed the following MIME parts from this message.

Content-Type: image/png Name: firma-GHP-emails.png

Replaced multipart/alternative part with first alternative.

El 4/4/23 a las 3:31, Mark Sapiro escribió:

Guillermo Hernandez (Oldno7) wrote:

...

I thought I said it: I reboot this server everyday at 06:40 CEST time. That's why I'm sure it's not an undetected problem for weeks. The lists in this last upgraded server are with daily traffic. I'm suscribed to all.

I've looked at this a bit further. Prior to Mailman core 3.3.4 we required aiosmtpd>=1.1. In 3.3.4 we required aiosmtpd>=1.4.1 and now we require aiosmtpd>=1.4.3. The code in aiosmtpd that triggers the issue in the socket module was added in aiosmtpd==1.3.1. So it is likely that your prior Mailman core version was <3.3.4 and your aiosmtpd dependency was <1.3.1, so the Mailman upgrade would also have upgraded aiosmtpd to a version which triggered the socket issue.

I think tou are completely right about the aiosmtpd changes. But I had mailman 3.3.5 installed since end of september of '21, mailman 3.3.6 since end of october '22, and mailman 3.3.7 since the beginning of december of last year. You can search the list and find my messages about that upgrades and problems I had with them.

Just to make it clear: It happened upgrading from 3.3.7 to 3.3.8

The upgrade procedure I did all the times is

pip install --upgrade django-mailman3 mailman mailman-hyperkitty mailmanclient postorius django hyperkitty uwsgi mod-wsgi

and if I see some trouble I did it with a --force-reinstall parameter (not that I remember it happened last times that I upgraded)

(and then the collectstatic, etc.)

If I missed something, I don't know.

---

Mailman-users mailing list --mailman-users@mailman3.org To unsubscribe send an email tomailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Archived at:https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/...

This message sent toguillermo@querysoft.es

--

Mailman's content filtering has removed the following MIME parts from this message.

Content-Type: image/png Name: firma-GHP-emails.png

Replaced multipart/alternative part with first alternative.