Re: [Mailman-Developers] mailman 3.0 roadmap, feature-parity with mailman 2.x and documentation

The OS was CentOS 6.5 in my case.
Is there a recommended server environment to run Mailman 3?
Brian

On 04/29/2015 01:26 PM, Brian Carpenter wrote:
Is there a recommended server environment to run Mailman 3?
It should install and run on any *nix server that supports both Python 2.7 and Python 3.0, an MTA capable of LMTP delivery to Mailman (currently configurations for Postfix and Exim are provided) and a web server compatible with Django.
We haven't tested all the possible combinations, and we've admittedly been a moving target, but things should get better and if you try and have issues, report them to this list or the appropriate (Mailman, Postorius or HyperKitty) bug tracker on Launchpad, and we will both try to help you through them and fix them.
Note, during the PyCon sprints, I did test installing and running Mailman 3 along side a running Mailman 2.1.20+ on my Ubuntu 14.10 laptop. I did have to sort out some dependencies, but it worked with the one caveat that if you have both a Mailman 2.1 list and a Mailman 3 list with the exact same posting address, in our recommended setup at least, Postfix will deliver a post only to the MM 3 list.
We understand we have a way to go, and it will be 3.1 before we get a clean, tested migration path and little or no loss of feature/function (the MM 3 core is based on an older 2.1 version), but we need people to start using MM 3 now, if only in limited environments, or we're never going to find the problem areas.
<plea> This is a major project and we are fewer than a dozen main contributers to its development, and we are all volunteers who do this for our own personal reasons, but not for money (most of us have day jobs; I'm fortunate enough to be retired). We need your involvement to make this successful. We welcome your help. </plea>
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

Thanks Mark. I will have my developer update Mailman 3 on my CentOS 6 server when I come back from vacation. I will then do some thorough testing and post my findings to this list.
Brian Carpenter EMWD.com

On 04/29/2015 08:45 PM, Brian Carpenter wrote:
That's wrong. I was conflating Mailman and Python Releases. Mailman 3.0 nominally requires Python 2.7 and Python 3.4. It may run with earlier Python 3.x releases, but no guarantees and probably not as old as 3.0 or even 3.1 in any case.
Thank you.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

On Apr 29, 2015, at 08:53 PM, Mark Sapiro wrote:
Nobody should be using Python 3 earlier than 3.2 for *anything* :), but the core probably will not work on Pythons earlier than 3.4. I haven't tested it, but I suspect we're using some newer standard library modules.
As we go forward, I hope we'll get some CI in place. Even after Python 3.5 is released I'd like to support 3.4 as a minimum version.
Cheers, -Barry

In addition to what Mark said: I know we've tested it on Fedora (20 and 22, I think?) and I have a script for docker install that uses Ubuntu 14.04 that may work for other apt-based systems.
Incidentally, if anyone's interested in doing packaging for the Mailman 3.0 Suite pieces for some common distributions, I think that would be really awesome.
Terri

On 04/29/2015 01:26 PM, Brian Carpenter wrote:
Is there a recommended server environment to run Mailman 3?
It should install and run on any *nix server that supports both Python 2.7 and Python 3.0, an MTA capable of LMTP delivery to Mailman (currently configurations for Postfix and Exim are provided) and a web server compatible with Django.
We haven't tested all the possible combinations, and we've admittedly been a moving target, but things should get better and if you try and have issues, report them to this list or the appropriate (Mailman, Postorius or HyperKitty) bug tracker on Launchpad, and we will both try to help you through them and fix them.
Note, during the PyCon sprints, I did test installing and running Mailman 3 along side a running Mailman 2.1.20+ on my Ubuntu 14.10 laptop. I did have to sort out some dependencies, but it worked with the one caveat that if you have both a Mailman 2.1 list and a Mailman 3 list with the exact same posting address, in our recommended setup at least, Postfix will deliver a post only to the MM 3 list.
We understand we have a way to go, and it will be 3.1 before we get a clean, tested migration path and little or no loss of feature/function (the MM 3 core is based on an older 2.1 version), but we need people to start using MM 3 now, if only in limited environments, or we're never going to find the problem areas.
<plea> This is a major project and we are fewer than a dozen main contributers to its development, and we are all volunteers who do this for our own personal reasons, but not for money (most of us have day jobs; I'm fortunate enough to be retired). We need your involvement to make this successful. We welcome your help. </plea>
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

Thanks Mark. I will have my developer update Mailman 3 on my CentOS 6 server when I come back from vacation. I will then do some thorough testing and post my findings to this list.
Brian Carpenter EMWD.com

On 04/29/2015 08:45 PM, Brian Carpenter wrote:
That's wrong. I was conflating Mailman and Python Releases. Mailman 3.0 nominally requires Python 2.7 and Python 3.4. It may run with earlier Python 3.x releases, but no guarantees and probably not as old as 3.0 or even 3.1 in any case.
Thank you.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

On Apr 29, 2015, at 08:53 PM, Mark Sapiro wrote:
Nobody should be using Python 3 earlier than 3.2 for *anything* :), but the core probably will not work on Pythons earlier than 3.4. I haven't tested it, but I suspect we're using some newer standard library modules.
As we go forward, I hope we'll get some CI in place. Even after Python 3.5 is released I'd like to support 3.4 as a minimum version.
Cheers, -Barry

In addition to what Mark said: I know we've tested it on Fedora (20 and 22, I think?) and I have a script for docker install that uses Ubuntu 14.04 that may work for other apt-based systems.
Incidentally, if anyone's interested in doing packaging for the Mailman 3.0 Suite pieces for some common distributions, I think that would be really awesome.
Terri
participants (4)
-
Barry Warsaw
-
Brian Carpenter
-
Mark Sapiro
-
Terri Oda