TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:Re: Definition of List Server From:Sandy Harris <sharris -at- DKL -dot- COM> Date:Fri, 13 Aug 1999 15:27:49 -0400
Debbie Robbins wrote:
>
> Bev,
> Here's a shot:
>
> A functional unit, a dedicated computer, that provides shared services to
> workstations over a network.
Methinks that shot missed. Your definition is close for "server", but not
for "list server".
My shot:
A piece of software (or, in some contexts, the machine on which it runs)
which manages one or more mailing lists. All messages arriving for a given
list are automatically sent to all the list's subscribers.
Generally, various list-management functions are also handled by the list
server. For example, it sends a "welcome" message to all new subscribers
and handles commands such as "subscribe", "unsubscribe", "lists" (get a
list of available lists), "who" (get a list of subscribers), and
"help" (get a list of list server commands), all without human
intervention.
Typically, these requests go to a different address. For a list named
wombat -at- somewhere -dot- com, they might go to wombat-request -at- somewhere -dot- com,
and/or to an address with the list server software name in it such as
majordomo -at- somewhere -dot- com or listserv -at- somewhere -dot- com -dot- /The/ classic
"clueless newbie" error is to send an "unsubscribe" message to the
list itself.
