Thanks for responding. Our setup will be much smaller, so I'm encouraged.
Dennis J. Gurgul
Helix System Management
617.724.3169
On 9 Apr 1997, Dewey M. Sasser wrote:
> >>>>> "Dennis" == Dennis Gurgul <gurgul@helix.mgh.harvard.edu> writes:
>
> Dennis> 1. Some users here have requested I install majordomo on
> Dennis> our unix system. They have offered to help with the
> Dennis> administrative burden. Does someone acting as a list
> Dennis> owner/administrator need root access, or can that work be
> Dennis> done at the user level (once everything is installed)?
>
> List owners do not need root access. All list owner operations are
> performed via mail, so they do not even need to be users on your system.
>
> Dennis> 2. I subscribed to majordomo-users about a month ago and
> Dennis> see about 30 or more messages per day. Many of the issues
> Dennis> look like basic configuration problems. Let's say
> Dennis> somebody administers a unix system with about 1,000 users,
> Dennis> and they need just the basics of a mailing list service.
> Dennis> How big of a task is the maintenance of this for someone
> Dennis> with limited unix admin experience (couple years)? Will I
> Dennis> have time for lunch? Thanks.
>
> Once MJ is set up, there is very little for the MJ-owner to do. Most
> of the burden is (as it should be) on the list administrators.
>
> Occasionally, you might have to get involved to fix a mail loop.
> Also, any bad mail to majordomo@yourdomain will go your way (such as a
> user sending a "help" command from an invalid address, or whatever.
> If the majordomo mail bounces, it will bounce to majordomo-owner. You
> can pick a victim (uh, I mean volunteer) to assist you with handling
> this type of thing (which I haven't seen on my lists since the last
> time I screwed up setting up a list).
>
> My company has on the order of 70 mailing lists (few of them public),
> and the only serious time commitment is on the one list where the
> owner has to track down all bad/changed addresses. Again, this burden
> is on the list owner, not the majordomo owner.
>
> The majordomo owner (or at least someone who can su root) will be
> necessary to add/change list topology such as adding a digest version
> of the list or adding archiving. Again, this is a setup cost. List
> options such as visibility, subscription, moderation, headers,
> footers, digests going out (except by cron) are all handled by the
> list owners.
>
> In summary, not too long ago my company made the rule that "all
> aliases with more than one person on it should be a majordomo mailing
> list", because, once majordomo is setup, there is less increment cost
> in maintaining another list than there is in maintaining the sendmail
> aliases.
>
>
> --
> Dewey M. Sasser voice: (617) 494-6000
> dewey@newvision.com PGP Key from public servers
> PGP mail preferred.
> ---
> "Deliver yesterday, code today, think tomorrow."
>
>
>
References:
|
|
