Date: Mon, 1 Jun 2020 17:17:22 -0500 From: Tim Daneliuk <tundra@tundraware.com> To: FreeBSD Mailing List <freebsd-questions@freebsd.org> Subject: Re: Migrating To Python 3.x Message-ID: <bfbe75c7-d53b-7a42-a4b9-36ad1585a39f@tundraware.com> In-Reply-To: <cdbae924-82d3-6d37-db4e-c9ed2ef9b1ab@kicp.uchicago.edu> References: <02676140-06dd-a947-b7b4-0f6ccbeaf773@tundraware.com> <cdbae924-82d3-6d37-db4e-c9ed2ef9b1ab@kicp.uchicago.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On 6/1/20 5:10 PM, Valeri Galtsev wrote: > > > On 6/1/20 5:03 PM, Tim Daneliuk wrote: >> I have a number of servers with rather complex mail/dns/web server >> configurations that are stable and have been running happily for many years >> needing nothing more than monthly patching. >> >> But Python 2.x is EOL at the end of this year. Can anyone suggest a >> strategy for moving from 2.x to 3.x? >> >> Also concerned about what to do with mailman since mailman3 never has made >> it to the ports tree as best as I can determine. >> > > I got some advises on mailman replacement recently, didn't have chance to work through migration yet, but my plan will be based on one of the following choices: > > 1. sympa (most likely) > > 2. majordomo (less likely) > > What else did you manage in your mail server setup depend on the sneaky snake (python)? > > Valeri > >> >> TIA, >> > I moved away from majordomo years ago because it was such a security problem. -- ---------------------------------------------------------------------------- Tim Daneliuk tundra@tundraware.com PGP Key: http://www.tundraware.com/PGP/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bfbe75c7-d53b-7a42-a4b9-36ad1585a39f>