
On Sat, May 4, 2024 at 6:55 PM Carl Zwanzig <cpz@tuunq.com> wrote:
On 5/4/2024 1:45 AM, Odhiambo Washington wrote:
On Fri, May 3, 2024 at 7:54 PM Carl Zwanzig <cpz@tuunq.com> wrote:
Last I checked, MM3 was just not suitable for a small set of smaller lists and to be maintained by less experienced people.
In what aspects was it not suitable? I have never encountered a document stating that.
Of course not, that's my opinion- every time I look at what it takes to install MM3, it seems like a lot of work for the results. If I need to run a few lists of tens of people, I don't want to spend multi-hours doing the setup. Kind of like using a 10 tonne lorry to move a table and chairs; it just doesn't make sense.
A lot of time? I think that's relative to the experience one has on as a Sysadmin. Can you try it by following - https://docs.mailman3.org/en/latest/install/virtualenv.html - and report the time it took you to have a functional list? You will most likely spend multiple hours on it when using the OS packaging system, which is;t recommended anyway. The virtualenv method is the recommended one.
Perhaps that's changed, has it? I am not able to answer that before I get the answer to my question above.
There you have it. MM2 has been quick and easy to install and configure and light on the resources, MM3 appears to need a lot more. (How long does it take to install and configure a complete and usable MM3 installation? What are the resources needed? At one time, I ran MM2 on a 90Mhz Pentium and it did the job; there's a 2006 list post about it.)
Again, "how long" will depend on one's familiarity with the applications being glued together. Not standard timing. How long does it take for MM2?
Did you also know that MM2 relies on Python2.7 (Recommended) which was already EoLed?
Um, I've known that for years, thing is MM2 -still-works-! This might be why there seem to be a fair number of MM2 installs out there in production.
My first MM2 install was probably 18-20 years ago.
I had my 1st MM2 install in 2005, IIRC.
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]