At 08:30 AM 11/5/95 PST, Ray Terry wrote:
(For example, I don't want my
>> MLM handling bounce-driven unsubscription, no matter how smart it thinks
>> it is. It will often do the wrong thing, because I make a decision based
>> on the user's history.)
>We know it can be done since LISTSERV has already done a good job of it.
So >how about a 'Majordomo Pro' product? A few may not want a more fully
featured >MLM, but I suspect most of us running larger lists would. Those
not wanting >the functionality would not have to config it.
I haven't used LISTSERV, but for me the transition from LISTPROC to
Majordomo has proven a pleasure. Quite simply, Listproc was NOT able to do
a good job. It was far too likely to delete someone whose mail was bouncing
temporarily or merely waiting. So in either case I had to do the work myself.
Majordomo makes it an easy job. Even with a large total # of subscribers
(it must be over 13,000 total subscriptions across our 13 lists), it is now
a very quick process for me to go through and distinguish between transient
failures and real problems. Majordomo also usually provides me the exact
address as provided in my subscription files - and allows me to do a 'which'
on a partial address when a wierd bounce comes back. Listproc did neither.
A "trigger-happy" auto-delete routine wouldn't be so tragic, especially with
majordomo's "bounces" list (which I have yet to set up). But I'm satisfied
with the small amount of work that I have to do.