On Sun, 3 May 1998, Rich Kulawiec wrote:

> 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.
> 
> Understanding of limitations/bugs in various packages and ability
>       to choose between packages.
> 
> Basic understanding of SMTP protocol.
> 
> Basic understanding of DNS (including MX records).
> 
> Thorough understanding of RFC 822 headers.
> 
> Understanding of the mechanisms and defenses against various
>       forms of abuse, including mailbombing, forged subscriptions,
>       etc.
> 
> Knowledge of de facto conventions (e.g. "-request").
> 
> Ability to use whois/traceroute and other network tools to find
> users, sites, admins, etc.
 
You forgot to mention a complete understanding of digital signal
transmission and assembly language programming.  Most of the skills
you have listed up to this point are more the purview of a site
manager, postmaster or sysadmin rather than a listowner.  Someone in
the loop should have all of the skills you mentioned.  I contend that
a good LISTOWNER need not have all of these skills.  If all of these
skills were required before you could become a listowner, only
techno-wizards would be listowners.  With proper support, you don't
need to be a rocket scientist to be a good listowner. 

Up to this point in the skills discussion, we have not mentioned
splitting responsibilities into typical divisions.  For example, I run
a site.  I understand the operation and limitations of my server
software.  My postmasters and sysadmins have a complete understanding
of SMTP and all of the other protocols and software needed to connect
my server to the net. De-facto list setup standards, such as a
"-request" address, are under the jurisdiction of the server admin. 
While I do use traceroute/whois and such to tack down spam and other
net abuse sent to my personal mail and to my server, I almost never
use these tools as a list admin. 

>       Awareness of privacy/copyright/etc. issues which have varying
>       impact on mailing list subscribers.


These are issues which the listowner needs to handle.


- murr -

Reply via email to