Adam D McKenna <[EMAIL PROTECTED]> writes:
> From: Chuck Milam <[EMAIL PROTECTED]>
>> First off, let me say this: Before anyone gets excited, ezmlm is NOT
>> an option. I have users and list owners that want to use Majordomo and
>> only Majordomo. They know Majordomo, they like Majordomo, they demand
>> Majordomo. Therefore, I have to make this work with Majordomo. Clear?
> The cool thing about ezmlm is that you don't need to "know" it. You
> just use it. There are no problems, no annoying bounces, etc. It just
> works.
This is simply not true. How do you subscribe to an ezmlm list? How do
you unsubscribe? How do you close an ezmlm list to non-subscriber
messages? How do you remotely get a listing of who's on the list? How do
you configure the intro message? How do you make the list moderated? I
know the answers to all of those questions, or at least solutions for
them, and they're all different than the answers for Majordomo.
Differences are things that you have to know.
You have to know ezmlm. Majordomo has ways of doing all of those things
that are different than ezmlm, and therefore people moving from Majordomo
to ezmlm would have to learn something new. When supporting users on
production servers who are expecting a specific interface, just telling
them "changing to ezmlm guys, learn something new" is not an option.
Furthermore, ezmlm and Majordomo are designed from very different
perspectives. Majordomo is a single address that runs *all* the lists at
one site, making things like global queries possible. A lot of people
have modified Majordomo implementations where global queries are even safe
and fast. This is not ezmlm's root philosophy, so even if you add support
for such things, it's not going to be as clean.
--
Russ Allbery ([EMAIL PROTECTED]) <URL:http://www.eyrie.org/~eagle/>
