On Sun, May 23, 1999 at 07:01:29PM -0700, SRE <eckert@climber.org> wrote:
> At 01:17 PM 5/23/99 +0300, Brock Rozen wrote:
> >Doesn't receiving a copy of the posted message indicate that it was sent out?
>
> Not always. We've had problems with some people getting it and some not.
> Also, there is a huge time lag. (Although I risk getting yelled at AGAIN
> by Jason for mentioning Listserv, Mj2 is much slower when distributing to
> 400 people. Listserv slows down on big lists also, but you get that little
> confirmation message and you don't worry about the hour or two it takes
> to get the post back.
Erm. Strikes me that this is MTA dependant. If your MTA is slow and
not designed to keep up with modern requirements for SMTP, you'll get your
response back slowly. Admittedly Mj2 is slower than Listserv, and slower
than Mj1, which Jason has acknowledged repeatedly - it hasn't had much
optimization for speed, it's still being built. But once a message has
been sent out via SMTP it's not really Mj2's responsibility to make it go
faster - that's the MTA's job.
This leads nicely into a question I've had for a while now - has anyone
got Mj2 working with Postfix? :)
> My reason for asking is that subscribers want it. If we make our
> decisions on what subscribers want, we'll probably have different
> code than if we try to decide what programmers are capable of
> doing for themselves. If we keep saying "but you can do these
> things for yourself and derive from them the same information
> that you want the server to deliver", aren't we sort of saying
> that only experts should use the software?
Jason isn't saying this is something which Mj2 shouldn't support, he's
saying he doesn't see the need, and because he doesn't see the need he's
not going to write the code for it. If you want it, write the code
yourself yourself or find someone else who will. Is it just me, or does
this seem to come up every month or two?
To go off on a bit of a tangent, I think there might be some confusion
about the difference between what subscribers want and what subscribers
need.
IMHO, I'd much rather have a nice, small(ish) core mailing list manager
which does basic tasks that subscribers *need*, and does them well. Have
it supply hooks for modules to be plugged into that do all the bells and
whistles that subscribers *want*, which are optional based on what the
server admin wants to install. Ideally, people besides Jason should be
working on those modules - aside, perhaps, from a few sample modules -
because I'd really like to see Mj2 go to beta sometime before 2001 (I have
a dream... ;), and I think Jason's time and talents are better spent
working on the core application.
Now, enough of my opinions... :) I'm going to dust off my ancient
years-old perl knowledge and actually look thru the code and see if I can
figure it out. Maybe I can remember and (re)learn enough to help out
with *something*.
Bryan
--
Bryan Fullerton http://www.samurai.com/
Core Competency
Samurai Consulting
"No, we don't do seppuku." Can you feel the Ohmu call?
Follow-Ups:
References:
|
|
