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.