> > Use and understand the listowner commands for the server software
> > used by the list such as:
This is good. Now I can explain the requirements from the point of view
of a user on an ISP that provides competent software for its users.
> Add:
> Judgement to decide when to use server software and when not to; or,
> in a related vein, which operations to automate and which to
> do manually.
On this particular ISP, there is no choice.
> Understanding of limitations/bugs in various packages and ability
> to choose between packages.
Not needed (see above).
> Basic understanding of SMTP protocol.
> Basic understanding of DNS (including MX records).
> Thorough understanding of RFC 822 headers.
Not needed; the software handles bounces, and unsubscribes undeliverable
addresses automatically.
> Understanding of the mechanisms and defenses against various
> forms of abuse, including mailbombing, forged subscriptions,
> etc.
Subscription requests require confirmation. Default configuration is that
posting is allowed only from subscribers.
> Knowledge of de facto conventions (e.g. "-request").
Taken care of by the ISP when they set up a mailing list for you.
> Ability to use whois/traceroute and other network tools to find
> users, sites, admins, etc.
Definately required for open lists, not needed that often for closed lists.
> Awareness of privacy/copyright/etc. issues which have varying
> impact on mailing list subscribers.
Very important. I'd say this is more important than RFCs and protocols.
I'd like to distinguish between two types of listowners:
1) The person with root privileges on his/her machine must be very competent,
including all the items on Rich's list, to manage the software that they
are responsible for.
2) The person with a shell account at a competent ISP that allows its users
to run mailing lists on the ISP's machines. In this case, the burden of
competency shifts to people providing the functionality. I.e., the
ISP's programmers must be competent; the user needs only be responsible.
-Joe
