Stephen J. Turnbull wrote: > Martin Lorenz writes: > > I am afraid, mailman3 needs far too much system resources for this > > virtual server. > > This whole story doesn't make much sense to me. You switched to a new > virtual server because Mailman 2 isn't supported but imply that > Mailman 3 is, but you can't get support from your vendor? Do you mean > that *Python* 2 is not supported but *Python* 3 is?
to clarify the history: the provider of my old v-server ceased its service. so I had to switch to a new provider. The new v-server is debian-based. the release is bullseye which does still provide python2 but lacks a few packages that are necessery to install mailman2.1 I would have to manually install dependencies via pip instead of apt. > Then, as far as I can tell on my hosts, Mailman 3 does not use a lot > more resources than Mailman 2.1 to process email, because it's > basically the same processing model. By "doing anything," do you mean > posting to lists? Migrating lists? Creating and managing lists with > Postorius? Migrating archives? Accessing archives and posting via > HyperKitty? The problem occurs whenever mail ist sent to a migrated list. All mails sent to the lists I migrated from my old 2.1 instance (23 lists in total) are swallowed and never get delivered. I have not found out where they are. There are no errors in the logs. exim accepts the mail, hands it over to mailman without error but never gets it back for delivery. A few mails turn up in the archive but must don't. > Python 2 is *unsupported* and likely to have security issues (in > particular, it probably allows SSL/TLS connections now considered > insecure). Mailman 2 is also end-of-life, and may have security > issues (although Mark continues to accept patches and even fix them > occasionally, he keeps promising to stop "soon"). You're asking for > endless hurt if you get into trouble with Mailman 2. (I don't think > it's likely except maybe a botnet will take your virtual server over > for Bitcoin mining or DDoS attacks, but if it happens it will be bad.) > Like Mark, I recommend that you at least let us try to help you to > figure out why the virtual server fails to run Mailman 3. Are you > sure the new virtual server will handle the load of Mailman 2? Maybe > it's just too small for the job of handling mailing lists. the new server is way stronger than the old one. > If you're not willing to upgrade, you're going to need to install I am more than willing to go with mailman3 if I can get it up and running. I currently try to retire all my python2 dependencies so going fo mailman2.1 was only because I quickly needed a working solution - which I did not get. Currently all users and admins of my lists know, that they have to be patient... thank you for the help you offer. The time I can invest on the subject is rather limited for the coming week. from Oct. 14 on I can dive into it :) greets martin ------------------------------------------------------ Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/
