Although e-mail is convenient for sending messages to someone else, sending a message to more than one user at the same time requires saving a copy of the message and sending it to the additional parties. Alternatively, you must create a distribution list of users who will receive the message and designate this list at the time the message is sent. If a list is used regularly and each user on the list keeps an individual version, each user is required to maintain that list. This means anyone wanting to join such a group is at the mercy of every user already on the list.
Duplication of effort coupled with the lack of control makes this a tenuous solution. Much better is a single, central list that requires a user to be added or deleted only once. All mail sent to such a list is forwarded to everyone on the list. This type of list is common on the Internet and is discussed later in this chapter. If we extend the features of such a list, we can allow each user to control the ability to receive mail, receive copies of the mail they post, and search previous messages for specific information. This is what Listservs do. Rather than burden someone with a full-time job of maintaining a list, Listservs allow those who want to subscribe to a list take care of themselves.
Listservs are one of the most accessible Internet resources available to those who don't have full Internet access; you need only an e-mail gateway. Many Internet-related books ignore or diminish the role of Listservs. Because of the Listserv system's role in the Internet's history and its continued growth and popularity, it is silly to overlook such a flexible, powerful, and useful Internet facility.
The Listserv system provides a mechanism for self-sufficiency, but this doesn't mean you are on your own. Each site running Listserv software has at least one person designated as the Postmaster. The Postmaster is responsible for the upkeep of the Listserv software (although this is usually done automatically using the Listserv system) and serves as a contact point to help resolve technical and list-oriented problems. If you need to contact the site Postmaster, send e-mail to POSTMAST@siteaddress (notice that POSTMASTER is truncated to POSTMAST to conform to an eight-letter user ID restriction).
The person you are most likely to contact is the list owner. The list owner is one or more individuals responsible for maintaining the list, helping users who have difficulties, and settling disputes. It's not unusual for someone to post a request publicly for the list owner to contact them. The preferred method of contact is to review the list and use the information there to send mail directly to the list owners.
NOTE Before diving deeper into this subject, a few notes should be made regarding conventions. References in this chapter to lists refer to VM operating system Listserv-based lists, unless otherwise stated. Every effort has been made to use real information and real messages as examples. The origin of the messages has been altered to protect privacy, and some users' e-mail addresses have been altered for the same reason.
Listserv-based lists provide users with the ability to govern themselves. You can subscribe and unsubscribe to the lists of your choice, control your subscription options, search through the archives of previous messages, and so on. Most lists are open to the public, although some are moderated and require the list owner to approve of messages before they are distributed.
Using the Listserv system requires little knowledge beyond that used to operate your e-mail system. Special methods required to tap into an Internet gateway (usually through an online service) are exceptions to the system requirements. Interacting with Listserv is as simple as sending someone e-mail. The commands are simple. The Listserv system even has the ability to peer itself—that is, you can split the list across several, even distant, sites to spread the load imposed by a heavily trafficked list.
NOTE Many texts that provide cursory information about Listserv tell you to leave blank the subject line of an e-mail header. If you have used different e-mail software—even on the same computer—you have probably discovered that many e-mail software packages do not allow a blank subject line. In actuality, the Listserv software ignores the subject line when processing commands.
The Listserv system originally started as a standard e-mail distribution list common to many users of the Internet today—all messages sent to a list were automatically redistributed to everyone listed as a subscriber. This was software written by EDUCOM and installed at BITNIC. As the desire and needs of the subscribers grew and additional features were needed to accommodate the volume of e-mail, Listserv became the Revised Listserv.
Dr. Eric Thomas developed this new list processor at the Ecole Centrale de Paris in France. This new generation of list processing provided for a broader understanding of users' needs and self-sufficiency. The new software included the ability to automatically subscribe and unsubscribe, get online help, communicate between multiple sites to improve efficiency, and specify different types of subscription settings to provide flexibility. As the Listserv system grows, Dr. Thomas has worked to ensure that each version is backward compatible with the previous version, allowing the system to continue to progress without requiring everyone to relearn how to use it.
Versions of the Listserv software are now underway for other operating systems. A Listserv-like system for UNIX is now available and running at many sites but is not as robust as Dr. Thomas' Listserv system. The subscription process has been automated, and a rudimentary help facility is available, but the various sites are not interconnected and self-organizing; that is, they are stand-alone sites. This means you have to examine each site for the lists it has to offer; you cannot retrieve a global list of lists.
As you become familiar with the Listserv environment, you notice one interesting characteristic about the names of the lists: they have a maximum of eight letters. This is no coincidence. As noted earlier in this chapter, the Listserv software was written for the VM/CMS operating system. VM (and many other IBM operating systems) allows no more than eight letters in a user ID.
A Listserv list is created as a user ID (usually by the technical support or systems staff) under VM. A control file is then created (again, usually by the support staff) that designates the list owners (those who can control the list and act on behalf of users when problems occur) and various options selected for the list (including default options). The control file is sent to the Listserv user ID. This step identifies the list to Listserv and can be used to activate the list.
A user ID with the name LISTSERV is the "brain" for each of the sites that supports the Listserv system. All commands related to list subscriptions and options should be sent to this user ID: all commands should be sent to LISTSERV@where_ever and all messages for others to read should be sent to listname@where_ever.
Because all messages sent to a list are redistributed to all active subscribers, stray commands are often sent to everyone. Also, it is not unusual for someone to post this message to a list: "Would someone please add me to this list?" A follow-up message from a subscriber is almost always posted, explaining the subscription process. The original requester does not see the message (because he or she is not yet a subscriber) so these efforts are in vain.
No system is perfect; even Listserv has flaws. Some users feel these flaws are severe enough to prevent them from using the lists. Although the flaws are annoying, you'll find that the shortcomings are not insurmountable. Listserv software continues to develop and improve. Subscribers can now specify topics of interest and receive only messages addressing those interests. Another feature has been added that allows a subscriber to receive one large block of messages in a digest format instead of many individual messages. This is convenient for those gaining access to the Internet through a paid service provider where charges may be based on the number of messages received and are almost always based on connect time. The digest form allows you to log on, download your e-mail in one file, and disconnect to read the mail offline at your leisure.
One inconvenience is the e-mail orientation of Listserv; everything arrives through your mailbox. If you are using a paid provider service that monitors or charges for e-mail use, this may be inconvenient. This drawback is offset by a positive attribute: because you are probably familiar with your e-mail software, you won't have to learn a new command structure for handling list traffic.
Another inconvenience of Listserv is that it cannot automatically address mail to the list owners. Other software packages allow you to direct mail to the owner or maintainer of a list or forum without knowing their name or e-mail address. To send mail to the Listserv list owner directly, you must know the address. For information on this process, read "Reviewing the List," later in this chapter. Do not do as some inconsiderate users do and post a request to the list asking the list owners to contact them.
Finally, no easy mechanism exists for determining where you have subscriptions. The only organized method of knowing about your subscriptions is to keep a list, perhaps a list of mail aliases, or an online address book that contains a list. You don't have to know which lists you have to remove your subscription from because you can unsubscribe from all lists. See "Unsubscribing from All Lists," later in this chapter, for information about this procedure.
Despite some of these inconveniences, the Listserv system has several redeeming features. The self-organizing structure allows you to quickly and easily find information about available lists and topics. Many other discussion lists tend to appear and disappear like mushrooms and have no formal mechanism that allows users to locate them.
The Listserv system also permits a high degree of independence. Other discussion lists require owner intervention just to add or remove users from a subscription list. Allowing users to control their own fate provides more free time (in theory) for list owners to improve their lists.
Finally, using the Listserv system doesn't require full Internet access. You can access these lists if the online system you use has an e-mail gateway to the Internet. Because most paid providers have (or will have soon) e-mail gateways, Listserv makes it easy to tap into the information exchanged.
The Listserv software system is structured to make Internet users self-sufficient. It's generally expected that you will provide for yourself. This includes subscribing and unsubscribing (except for moderated lists), searching the archives for previously discussed topics, and determining whether or not the list is "alive."
At times, you must rely on the list owner to intervene on your behalf, but doing so publicly is not the preferred method. All the commands you need to avoid inflicting yourself on fellow subscribers and eliminate embarrassment can be found in this chapter. Anyone who learns how to subscribe to a list is expected to know how to unsubscribe as well.
TIP Because messages sent to a list are redistributed to all active subscribers, never send Listserv commands to the list; always send them to the Listserv user ID.
After subscribing to a list, it is a wise practice to lurk. Lurking is the practice of watching but not posting; you're an electronic Peeping Tom. Doing so allows you time to acclimate yourself with the posters and participants, gauge the volume (number of messages) of the list, and determine whether this is where you want to spend your time. Newbie users are exposed when they subscribe to the Star Trek Listserv (STREK-L@PCCVM.BITNET) and post a message such as "I like the pointy-eared guy. What's his name?" or subscribe to the chess Listserv (CHESS-L@GREARN.BITNET) and post "I just learned to play last year. Please send me your favorite opening."
Before posting, consider your audience. Eventually, you'll find others with whom you have something in common. You'll be tempted to exchange messages, which are extensions of list conversations. It's polite to take these message threads offline; not everyone is interested in hearing the various tidbits of information you and your cohorts exchange. They're irrelevant to the list's purpose.
The world is not going to end because you do not provide for yourself. But you reduce or eliminate the aggravation caused to fellow users by familiarizing yourself with the commands and the actions they perform. Generally, the Internet community is open minded and tolerant of diversity. Jumping in without consideration for current policies and practices, however, is similar to doing a cannonball off the diving board, splashing your hosts, and realizing you never learned to swim.
The Listserv system's self-organizing ability provides an advantage over other e-mail-based discussion lists. Finding lists of interest is simple; messages like "Does anyone know of a Listserv about such-and-such topic?" are unnecessary and annoying.
There are three primary methods for finding lists: online references, directories, and texts (including Gopher and Veronica); subscribing to NEW-LIST and receiving an announcement; and using the built-in LIST command.
The online references and dictionaries are regularly updated materials. They are provided by individuals who collect information about either general topics representing a cross-section of the Internet's offerings or resources of interest to specific special-interest groups.
NEW-LIST is for users who create new lists (both Listserv and non-Listserv) to notify others. This list is also used by persons posting inquiries while looking for specific lists, Listservs, and news. The address of NEW-LIST is vm1.nodak.edu (for those who don't trust Listserv to forward your subscription request). See "Subscribing and Unsubscribing," later in this chapter, for information about subscribing to Listservs.
The LIST command is the Listserv equivalent to a library's card catalog; it allows users to exploit Listserv's self-organizing capability. The scope (or range) of the LIST command depends on the options you specify. If you are interested in becoming a charter member of a Listserv, you may find yourself checking for new lists more often than is practical. Using the LIST command daily or weekly is probably too often. If early exposure to a new list is important, you should probably subscribe to NEW-LIST.
If the LIST command is used without options, it provides a list of lists for the site receiving the command. Here's the abbreviated output from sending the LIST command to listserv@indycms.iupui.edu:
> LIST
AATG American Association of Teachers of German
ACCESS-L Microsoft Access Database Discussion List
APOSEC52 Alpha Phi Omega Region 6 (Sections 48/52/54)
ARNBOARD ARNOVA Board of Directors
BIBSOFT Discussion of software for citations and bibliographies
BKGAMMON Backgammon strategy
BRTHPRNT List for Birthparents of Adoptees
C-L Discussion of C Programming
CENTINFO Center Availability Information
COMPACT IUPUI Campus Compact
CSCI207 Learning List for CSCI207
DISTLABS Teaching Science Labs Via Distance
EXCEL-L Microsoft Excel Developers List
FACOUNCL IUPUI Faculty Council Mail List
FITNESS Fitness and the IUPUI campus
FREE-L Fathers' Rights and Equality Exchange
The LIST GLOBAL command is self-descriptive. It returns a list of all known public lists. If you do not send the command to a backbone site, it is forwarded to a backbone for you. A backbone site is a primary or large site. Because Listserv forwards LIST GLOBAL requests on your behalf, it is not necessary to know the addresses of your backbone sites.
TIP If you are using an online service that charges for either large numbers of messages or large messages, check to see whether it has an online library that contains files, such as the LISTSERV LISTS file. Another possibility is to try using a Gopher (see Chapter 25, "Using and Finding Gophers") or Veronica (see Chapter 26, "Searching Gopherspace with Veronica"), both of which frequently provide access to the global list.
Before sending the LIST GLOBAL command, you should be prepared for the results. At the time of this writing, more than 4,000 lists existed. This means a rather lengthy list of lists when you to try to determine what's changed since the last time you submitted the command.
NOTE The emphasis on Bitnet addresses in the LIST GLOBAL result does not mean you have to become a full-time Bitnet-to-Internet translator. Listserv is usually smart enough to forward commands to the correct site.
Following is a portion of the output received from the LIST GLOBAL command (do you really want to read through 100 pages now?). The Network-wide ID column gives the name of the list, the Full address column is the Bitnet address, and the List title column gives the description of the list designated by the list owner.
List of all Listserv lists known to Listserv@YALEVM on 28 Feb 1994 22:55
Network-wide ID Full address List title
-
AUSTEN-L AUSTEN-L@MCGILL1 Jane Austen discussion list
AUSTLIT AUSTLIT@NDSUVM1 Austrian Literature
AUTISM AUTISM@SJUVM SJU Autism and Developmental
Disabilities List
AUTOCAD AUTOCAD@JHUVM AUTOCAD Discussion List
AUTOCAT AUTOCAT@UBVM AUTOCAT: Library cataloging and
authorities +
AUTORACE AUTORACE@VTVM1 AUTORACE - A Discussion of Auto
Racing
AUTOS-L AUTOS-L@TRITU The List For Classic And Sports Cars
AVHIMA-L AVHIMA-L@UIUCVMD American Veterinary Health
Information Manag+
AVIATION AVIATION@BRUFPB General Aviation List
AWARDS-B AWARDS-B@OSUVM1 Commerce Business Daily - Awards
AWARE-L AWARE-L@UKANVM Discussion of the dual platform
authoring pr+
AWR-L AWR-L@TTUVM1 A WRITER'S REPERTOIRE
AXE-LIST AXE-LIST@MCGILL1 Quebec Literature Studies
Faced with the prospect of browsing more than 4,000 lines of text to find interesting lists, most users resort to reading the text file into an editor or word processor and using a search command. Listserv has a mechanism to reduce the list automatically. An extension of the LIST GLOBAL command enables you to specify text to be found in the name or description of the list. The form of the command extension is LIST GLOBAL/text where text is text string for which you want to look in the list name or description.
The next output example shows a list of information supplied by Listserv when the LIST GLOBAL/GAME command is submitted. The /text extension is not a cure-all. Some lists may have cryptic names resulting from the eight-letter restriction, or may not be described in the way you expect. However, it often reduces the search time.
Excerpt from the Listserv lists known to Listserv@YALEVM on 31 Jan 1994 01:07
Search string: GAME
Network-wide ID Full address List title
-
CONSIM-L CONSIM-L@UALTAVM Conflict simulation Games
DIPL-L DIPL-L@MITVMA Discussion Group for the Game of
Diplomacy
D20A-L D20A-L@MITVMA 10 Player Diplomacy Game List (Sam
Huntsman +
GAMES-L GAMES-L@BROWNVM (Peered) Computer Games List
GAMES-L@GREARN (Peered) Computer Games List
GAMES-L@KRSNUCC1 (Peered) Computer Games List
GAMES-L@UTARLVM1 (Peered) Computer Games List
GMAST-L GMAST-L@UTCVM Gamemasters Interest Group
MYTHUS-L MYTHUS-L@BROWNVM Mythus Fantasy Roleplaying Game List
SHADOWRN SHADOWRN@HEARN Discussion of the Fantasy game
ShadowRun
STARGAME STARGAME@PCCVM STARTREK Role Playing game list
The following sections describe the all-important activities of subscribing and unsubscribing to Listserv.
The SUBSCRIBE command requires little documentation, aside from the need to identify yourself to Listserv. SUBSCRIBE can be abbreviated SUB, producing the following command syntax:
SUB listname firstname lastname
Remember to insert the correct name of the list for listname, and your first and last names in place of firstname and lastname. Listserv is designed to allow you to send this command to any Listserv user ID; your request is forwarded to the proper host site (you are notified should forwarding occur). Here is a copy of the notice received from a subscription request to the FOLKLORE list:
Your subscription to the FOLKLORE list (Folklore Discussion List) has been accepted.
Please save this message for future reference, especially if you are not familiar with Listserv. This might look like a waste of disk space now, but in 6 months you will be glad you saved this information when you realize that you cannot remember what are the lists you are subscribed to, or what is the command to leave the list to avoid filling up your mailbox while you are on vacation. In fact, you should create a new mail folder for subscription confirmation messages like this one, and for the "welcome messages" from the list owners that you will occasionally receive after subscribing to a new list.
To send a message to all the people currently subscribed to the list, just send mail to FOLKLORE@TAMVM1.TAMU.EDU. This is called "sending mail to the list", because you send mail to a single address and Listserv makes copies for all the people who have subscribed. This address (FOLKLORE@TAMVM1.TAMU.EDU) is also called the "list address". You must never try to send any command to that address, because it is distributed to all the people who have subscribed. All commands must be sent to the "Listserv address", Listserv@TAMVM1.BITNET (or Listserv@TAMVM1.TAMU.EDU). It is very important to understand the difference between the two, but fortunately it is not complicated. The Listserv address is like a FAX number, and the list address is like a normal phone line. If you make your FAX call someone's regular phone number by mistake, it is an unpleasant experience for him but you will probably be excused the first time. If you do it regularly, however, he will probably get upset and send you a nasty complaint. It is the same with mailing lists, with the difference that you are calling hundreds or thousands of people at the same time, so a lot more people get annoyed if you use the wrong number.
You may leave the list at any time by sending a "SIGNOFF FOLKLORE" command to Listserv@TAMVM1.BITNET (or Listserv@TAMVM1.TAMU.EDU). You can also tell Listserv how you want it to confirm the receipt of messages you send to the list. If you do not trust the system, send a "SET FOLKLORE REPRO" command and Listserv will send you a copy of your own messages so that you can see that the message was distributed and did not get damaged on the way. After a while, you may find that this is getting annoying, especially if your mail program does not tell you that the message is from you when it informs you that new mail has arrived from FOLKLORE. If you send a "SET FOLKLORE ACK NOREPRO" command, Listserv will mail you a short acknowledgment instead, which will look different in your mailbox directory. With most mail programs, you will know immediately that this is an acknowledgment you can read later. Finally, you can turn off acknowledgments completely with "SET FOLKLORE NOACK NOREPRO".
Contributions sent to this list are automatically archived. You can get a list of the available archive files by sending an "INDEX FOLKLORE" command to Listserv@TAMVM1.BITNET (or Listserv@TAMVM1.TAMU.EDU). You can then order these files with a "GET FOLKLORE LOGxxxx" command, or using Listserv's database search facilities. Send an "INFO DATABASE" command for more information on the latter.
Please note that it is presently possible for anybody to determine that you are signed up to the list through the use of the "REVIEW" command, which returns the e-mail address and name of all the subscribers. If you do not want your name to be visible, just issue a "SET FOLKLORE CONCEAL" command.
More information on Listserv commands can be found in the Listserv reference card, which you can retrieve by sending an "INFO REFCARD" command to Listserv@TAMVM1.BITNET (or Listserv@TAMVM1.TAMU.EDU).
This message is a template—it is nearly the same for every subscription confirmation, except for the list name and addressing information. If you read this listing carefully, you will see much of the information users need to avoid posting queries like "How do I sign off this list?" or "How do I receive copies of the mail I send?"—the message even fills in the addresses specific to this list.
NOTE If you misspell your name or want to change it, the SUB command allows you to do so. If you submit the SUB command to a list that understands you to be a subscriber, it makes the name change for you.
Some lists require confirmation after an initial subscription request. The following example shows a portion of the message returned by Listserv when a subscription request is submitted to a list requiring confirmation. You may wonder why confirmation is be needed. Consider what would happen if you leave your user ID logged on and unattended. Someone can easily send a subscription request to a list with a high volume of mail, perhaps even on the order of several hundred messages per day. Requiring confirmation can help avoid this problem.
Your command:
SUBSCRIBE ACCESS-L firstname lastname
has been received. You must now reply to this message (as explained below) to complete your subscription. The purpose of this confirmation procedure is to check that the address Listserv is about to add to the list for you is working properly. This is a typical procedure for high-volume lists and all new subscribers are subjected to it - no offense meant. We have tried to make this confirmation as simple and painless as possible, and apologize for the inconvenience.
Historically, most Internet users come from academic institutions (hence the reference in many Internet circles to the "September" cycle of new users). This means a fairly high rate of turnover because of student users who are away several months of the year. Even in the world of the Internet today, where businesses are connecting at dizzying rates, turnover exists. Listserv permits the list owner to require renewal of your subscription, usually once a year, to alleviate the burden of weeding out expired user IDs or the user IDs of persons who may still be subscribed but have no interest in the list. This list is also used by persons looking for specific groups who post inquiries.
The UNSUBSCRIBE command (which can be abbreviated UNSUB) or the SIGNOFF command removes you from the specified list. The command syntax is as follows:
UNSUB listname
This is the output from a successful UNSUB request:
You have been removed from the FOLKLORE list.
If you try to remove yourself from a list that doesn't consider you to be a subscriber, you receive two messages. The following example shows the first message that resulted from an unsuccessful attempt to unsubscribe from WIN3-L:
> UNSUB WIN3-L
You do not appear to have subscribed to list WIN3-L. You are being mailed some additional information, with a few hints on getting your subscription cancelled. Please read this mail message before trying anything else.
The next output extract provides the first few lines from the follow-up message. If you cannot resolve the problem using the information provided in this response, you should attempt to contact one of the list owners. Instructions for determining the list owners' e-mail addresses are found in "Reviewing the List," later in this chapter.
No entry for your me@here address could be found in the WIN3-L list at
UICVM. Here are a number of possible reasons why you might still be getting mail from the list.
TIP If you cannot reach any of the list owners for assistance and you are subscribed to a high-volume list, consider using the SET listname NOMAIL command (details provided later in this chapter). This command stems the tide of e-mail until you can unsubscribe. Using this command is preferred to a public message, which will only irritate your fellow subscribers.
If it becomes necessary for you to unsubscribe from all the lists to which you are subscribed, Listserv has just the tool: an extension of the UNSUB or SIGNOFF command. This extension tells Listserv to distribute the request to all known Listserv sites and attempt to remove you from any of the lists under their control. No special information is provided for this command. The syntax is as follows:
SIGNOFF * ( NETWIDE
Processing your request takes place in two steps. The following example shows the output from the first step, which indicates that UNSUB requests will be passed along to other servers. If you know your user ID will be deleted or out of service, it is only courteous to remove yourself from lists in advance. Many users do not realize that their inaction causes extra work for others when the mail begins bouncing. Many support personnel ignore this command when removing a user ID from their system and address individual messages to each of the lists found in the mailbox to ask for removal.
> UNSUB * ( NETWIDE
Your request will be forwarded to 259 servers.
Although Listserv doesn't enable you to determine which lists you are subscribed to in a global fashion, you can determine the subscription parameters for a particular list. You also can list information about a particular list. Some lists allow you to retrieve information about the list only if you are listed as a subscriber. This option is turned on or off by the list owners.
The QUERY command returns the subscription values for a particular list. In addition to providing information about your subscription, the QUERY command can quickly tell you whether you are subscribed to a list. If you believe you are a subscriber and receive information from the Listserv system to the contrary, use the REVIEW command (explained in the next section) to determine whether Listserv has you subscribed with a different e-mail address.
> QUERY ACCESS-L
Distribution options for firstname lastname <me@here>,
list ACCESS-L: Ack= Yes, Mail= Yes, Files= Yes,
Repro= No, Header= Short(BSMTP), Renewal= Yes, Conceal= No
You should use the REVIEW command to obtain specific information about the list—default subscription values for new subscribers, a list of the users and their e-mail addresses, and a list of users who have not concealed their subscription. Here is some of the information returned when reviewing the WORDS-L list:
* English Language Discussion Group
*
* Review= Public
* Subscription= Open,Confirm
* Send= Public
* Daily-Threshold= 300
* Notify= Yes
* Reply-to= List,Respect
* Files= No
* Default-options= Repro
* Confidential= No
* Validate= Store Only
* Renewal= 6-Monthly,Delay(14)
* X-Tags= Comment
* Stats= Normal
* Ack= No
* Notebook= No
* Digest= Yes,Same,Daily
* Owner= maynor@ra.msstate.edu (Natalie Maynor)
* Owner= alileste@idbsu.idbsu.edu (Dan Lester)
* Owner= lncjb@cc.newcastle.edu.au (Carolyn Baird)
* Owner= fna104@uriacc.uri.edu (Jim Bradley)
* Owner= hide:,quiet:
* Owner= maynor@cs.msstate.edu (Bernard Chien Perro)
* Owner= hide:,quiet:
* Owner= harold@uga
* Errors-to= maynor@ra.msstate.edu
* Errors-to= alileste@idbsu.idbsu.edu
* Errors-to= lncjb@cc.newcastle.edu.au
* Errors-to= fna104@uriacc.uri.edu
* Editor= maynor@ra.msstate.edu
* Editor= alileste@idbsu.idbsu.edu
* Editor= lncjb@cc.newcastle.edu.au
* Editor= fna104@uriacc.uri.edu
* Mail-Via= DIST2
Other discussion list methods can be implemented using e-mail, but you are usually limited to the options of receiving mail or not receiving mail: If you are a subscriber, you receive mail; when you are removed from the list, you do not receive mail. The Listserv software, however, has several options you can set.
Several of these options are described in the subscription message you receive (see the output listing, earlier in this chapter, for a successful subscription request) in a format customized for that particular list. The following sections list options you'll find helpful, as well as information about why and when you may want to use them. This is not an exhaustive list, but the commonly used options are described. You can retrieve additional Listserv commands using the information in "Using the INFO Command for More Information," later in this chapter.
The MAIL/NOMAIL option instructs Listserv about your desire to receive or halt posted messages. Using this command enables you to control the e-mail flow but still retain your subscription. The syntax of the command indicating a desire to stop receiving messages is as follows:
SET listname NOMAIL
The counter command that restores your ability to receive mail is this:
SET listname MAIL
You'll find this handy in several situations. If you return from vacation, or your system was brought down for an extended period of time, you can find yourself digging out from underneath an avalanche of messages when you return. Imagine how much mail you can have waiting for you if a high-volume list sends several hundred messages daily and you're gone for a week. If you feel you have missed something, you can retrieve relevant archives (if that option is established for the list) at your convenience. Look at the sections later in this chapter that explain the archive structure and how to list, search, and retrieve list archives.
TIP Another reason to keep a list subscription and not receive messages is for the purpose of research. Many older lists have extensive archives that are nice to search. If you are interested in material previously posted (perhaps on a computer-related forum for solutions to a particular problem) but don't care to receive e-mail, the NOMAIL option is exactly what you need.
Many unknowing or inexperienced users post messages to a list asking, "Why don't I receive copies of my own messages? Are my messages being posted? Please let me know." The Listserv system has an option called REPRO, which indicates your desire to receive copies of the messages you post to the list.
A good rule of thumb is to expect lists to default to Repro=No. If you want to receive copies of your own messages (a sign the list is at least functional when traffic is light), use this syntax:
SET listname REPRO
Turn the option off with this syntax:
SET listname NOREPRO
You may find it necessary to conceal your subscription to a particular list; perhaps the list focuses on issues of a personal nature and you'd rather others—for example, your employer—not know you are a subscriber. The CONCEAL command prevents others from seeing your name and e-mail address when they retrieve list information with the REVIEW command. You should know, however, that this command does not prevent others from seeing your presence if you post messages to the list. You can only hope a list that is this important allows only subscribed users to search the archives. This means that someone wanting to check up on you has to join the list and take the chance of exposing themselves.
The syntax of the command to conceal yourself is as follows:
SET listname CONCEAL
Here is the reverse command:
SET listname NOCONCEAL
SHORT
Because Listserv is efficient enough to send copies of messages once to each site (whenever possible), it lists each of the recipients at that site in the To header field. If the number of users at your site is more than a handful, this list can get cumbersome. The list of recipients also compromises your privacy because your name and user ID are on each message received by your associates. The list of To recipients can be abbreviated to a nondescript Multiple users by using the following command syntax:
SET listname SHORT
The full list of headers can be turned on using the following command syntax:
SET listname FULL
Although many other Internet-related discussion groups and Usenet newsgroups keep archives available with anonymous FTP, Listserv makes archives available directly. Most lists archive all messages automatically. They also have the ability to store files for retrieval, as well as storing groups of files known as packages. A package permits making one retrieval request instead of requesting many files individually.
The Listserv system possesses a powerful searching mechanism. Without it, you are required to retrieve entire archive files and search them manually. The following sections are not a comprehensive tutorial to the searching mechanisms; after reading them, however, you will be able to perform simple searches and have enough information to survive as you learn.
The INDEX command provides a list of files available at the site hosting the Listserv. Following is a summarized output from an INDEX request submitted to listserv@uicvm.uic.edu, host of WIN3-L. The most important columns are the filename, file type, and file description. Remember that Listserv is structured for the VM operating system. VM organizes files by filename and file type (there's also a filemode, but that is not relevant here).
* Master Listserv filelist
* rec last-change
*filename filetype GET PUT -fm lrecl nrecs date time File description
* - - -
Listserv FILELIST ALL CTL V 107 105 95/01/31 22:19:33 Lists all available
Listserv files
NOTEBOOK FILELIST NAD N/A V 95 N/A 95/01/26 11:23:51 List of available
notebooks
INFO FILELIST ALL LMC V 102 100 94/09/16 22:02:58 List of information
files about Listserv
TOOLS FILELIST ALL LMC V 97 223 94/09/16 22:03:04 Software tools for
use with Listserv
CONTROL FILELIST ALL LMC V 96 139 95/01/25 13:49:14 Control datafiles
used by Listserv
The master list has been obtained, but it contains only high-level material and doesn't include information about the intended target: WIN3-L. Submitting a new INDEX request in the form INDEX WIN3-L produces output similar to the following. This is a list of files associated with WIN3-L.
* WIN3-L FILELIST for Listserv@UICVM.
* WIN3-L files
* rec last - change
*filename filetype GET PUT -fm lrecl nrecs date time File description
* - - -
WINDOWS FAQ ALL OWN . . 0 ........ ........
* NOTEBOOK archives for the list
* (Monthly notebook)
* rec last - change
*filename filetype GET PUT -fm lrecl nrecs date time File description
* - - -
*
* NOTEBOOK archives for the list
* (Weekly notebook)
* rec last - change
*filename filetype GET PUT -fm lrecl nrecs date time File description
* - - -
WIN3-L LOG9201A PRV OWN V 80 2920 95/01/07 23:04:35 Started on Sun,
1 Jan 1995 10:15:44 EST
WIN3-L LOG9201B PRV OWN V 80 4359 95/01/14 22:58:49 Started on Fri,
8 Jan 1995 08:32:00 CET
WIN3-L LOG9201C PRV OWN V 80 3674 95/01/21 22:43:27 Started on Sun,
15 Jan 1995 00:29:10 -0600
WIN3-L LOG9201D PRV OWN V 80 2656 95/01/28 09:02:49 Started on Sat, 21 Jan 1995 23:17:00 PST
WIN3-L LOG9201E PRV OWN V 80 1335 95/01/29 09:54:12 Started on Sun,
29 Jan 1995 10:11:25 EST
WIN3-L LOG9401D PRV OWN V 82 11507 94/01/28 23:48:41 Started on Sat,
22 Jan 1994 00:50:00 EDT
WIN3-L LOG9401E PRV OWN V 80 5651 94/01/31 23:31:36 Started on Fri,
28 Jan 1994 21:43:00 EST
WIN3-L LOG9402A PRV OWN V 79 240 94/02/01 02:04:32 Started on Mon,
31 Jan 1994 22:21:57 -0800
The files with a file type prefix of LOG are archives. The files have a timestamp: LOGyynn tells the year (yy) and number (nn) of the archive. The ninth line of the listing indicates that notebooks are reset monthly (now we know that each number indicates the month the archive log was created). Some lists have enough activity to warrant weekly logs. The final letter at the end of the filename (for example, A, B, or C) indicates smaller archives within the month. Whenever a log archive becomes large, the letter is incremented to keep the same datestamp but provide a unique file type.
The filename and file type become important when you want to retrieve a file. The proper command syntax to indicate which file you want sent to you is as follows:
GET filename filetype
If you retrieve too much material during a 24-hour period, you are notified by Listserv and told how much time must expire before you can retrieve more files. If a specific file is desired, you shouldn't have any problems, but if you are retrieving log archives and searching them, you may want to investigate the Listserv searching mechanism.
A demonstration of the LIST command has provided you with a list of files associated with the WIN3-L list. As a quick review, each message posted to the list is archived in a log file if the list owner has specified this option. Sites working with little or no spare disk space may not permit list archives.
The INDEX command is local; that is, it is relevant only for the site you send it to. If you send the command INDEX listname to a Listserv user ID, it returns a list of files associated with the list. This list includes the archived files (if this feature has been designated by the list owner). If you want to retrieve a file, use the GET command. The command structure is GET filename filetype (to conform to the VM operating system's structure of a filename and file type). After the request is processed, the desired file is returned to you.
The Listserv system supports a powerful searching mechanism. The minute details of this function are beyond the scope of this book. The INFO command provides you with the information you need to retrieve the necessary documents. The Listserv system lets you search for more than just specific words. Archived messages can be searched based on the date they were written, words they contain, words they don't contain, who posted the message, similarities of words, and combinations of all of these.
Here is a simple search request:
//
Database Search DD=MyJob
//MyJob DD *
Search Easter Egg in Win3-L
Index
/*
If this is submitted as an e-mail message and sent to listserv@uicvm.uic.edu by an active subscriber, an index of messages that contain the words easter and egg is returned. (Easter eggs are the hidden screens software designers sometimes add to programs as an artistic touch.) If you use this sample command file as an example and build on it using the online references, it's possible to find just about anything you are looking for. The searching mechanism is one of the most understated features of the Listserv system and is probably more powerful than those available in commercial systems that permit user searches against unstructured text.
The INFO command is the method for requesting help. You can send this command to any of the Listserv user IDs, and a file will be sent to you in response to your request. Use the INFO ? command to retrieve a current list of relevant help topics. Most topics listed are available to all users. Some are available only to those who own or maintain lists, others only to Postmasters, and still others only to those who help coordinate the Listserv software system.