LISTSERVLISTSERV lists give you a way to have open discussions with dozens (or even hundreds) of people on a myriad of topics. Best of all, it is all done through e-mail!
I want to say something about the difference between list addresses and LISTSERV addresses. Let's pretend that I create a list here at the University of Alabama for the open discussion of power line-chomping squirrels. I'll even call the list "SQUIRREL".
The address for our pretend squirrel discussion list would be SQUIRREL@UA1VM.UA.EDU (or SQUIRREL@UA1VM.BITNET). Any e-mail letter sent to the SQUIRREL@UA1VM.UA.EDU address would be copied and mass-mailed to every single person subscribed to the squirrel list. That's simple enough.
But how are people going to subscribe to my squirrel list? We need a second address just to handle all of the commands for the list! That second address is the LISTSERV address (which, in this case, is LISTSERV@UA1VM.UA.EDU).
Are you starting to see the picture?
The list address is the address you send something to if you want it to be distributed to everyone else subscribed to the list. The LISTSERV address is the address you send all of your commands to.
What would happen if you sent a command (like SUBSCRIBE or GET) to the discussion list's address instead of to the LISTSERV's address? Simple -- your command would be treated like a letter and would be sent to everyone on the list (how embarrassing!).
Remember this (and you will see this on a pop quiz sometime):
Now, life would be a whole bunch easier if the only LISTSERV in the world was at the University of Alabama. But, it isn't. There are thousands of different LISTSERVs around the world, and there are literally tens of thousands of different LISTSERV lists.
How are you ever going to find out what different discussion lists are out there, and what these lists' addresses are? Well, there are a couple of ways to do this:
A few more examples:
List address: LISTSERV address:
CHAUCER@UICVM.BITNET LISTSERV@UICVM.BITNET
ROADMAP@UA1VM.UA.EDU LISTSERV@UA1VM.UA.EDU
PPD-L@HUMBER.BITNET LISTSERV@HUMBER.BITNET
VEGLIFE@VTVM1.BITNET LISTSERV@VTVM1.BITNET
Why is this important to know? Well, let's say that I tell you
that there is a LISTSERV list called VEGLIFE@VTVM1.BITNET that
you really need to subscribe to. All I have given you is the list's
address. Remember, you can only send LETTERS to the list address
You need the LISTSERV address in order to subscribe!
With this trick, you automatically know that the LISTSERV address for VEGLIFE@VTVM1.BITNET is LISTSERV@VTVM1.BITNET and you can subscribe to the list without any problem!
You may notice that some list addresses look something like this: CRUISE-L@UNLVM MAPTEST@UA1VM NAVIGATE@UBVM Those are BITNET addresses. To turn these addresses into something that you can use, you'll have to add .BITNET to the end of the addresses: CRUISE-L@UNLVM.BITNET MAPTEST@UA1VM.BITNET NAVIGATE@UBVM.BITNET and the LISTSERV addresses would be: LISTSERV@UNLVM.BITNET LISTSERV@UA1VM.UA.EDU LISTSERV@UBVM.BITNET One nice thing about this is that you can almost always tell that a list is a LISTSERV list by looking at the list's address. If the address is LIST@NODE or LIST@NODE.BITNET, you can all but bet that the list is a LISTSERV list.
Some of you may be at sites that do not allow mail to Bitnet addresses.
You can bypass this restriction by taking the address
LIST@NODE.BITNET
dropping the .BITNET, so the address becomes
LIST@NODE
changing the @ to a %, so the address becomes
LIST%NODE
and then adding @CUNYVM.CUNY.EDU to the end, so that the final
address becomes
LIST%NODE@CUNYVM.CUNY.EDU
Now let's talk about some new LISTSERV commands. You already
know the SUBSCRIBE command
SUBSCRIBE listname
and the GET command
GET filename filetype F=MAIL
I want to show you a couple of other commands that will make your
life a whole lot easier (remember, all commands must be sent to
a LISTSERV address).
If you ever need to unsubscribe from a list, the UNSUBSCRIBE command will take care of everything. There are three different UNSUBSCRIBE commands that you can use:
There are a couple more things I want to talk about, but I'll save them until tomorrow :)