The most common commands are also available in a simple, easy to use form.
Expanded descriptions are available below:
Caps and small letters in a command line are used to show the minimum letters required to execute the command. You can generally send any number of commands in a single message, as long as each is on a separate line. (Exceptions to this rule will be noted.)
If you are forced to change Internet providers and cannot unsubscribe from your old e-mail address, please send an e-mail note to the Listowners with a request to unsubscribe from the old e-mail address.
You can do this by signing off from the old logon and than resubscribing from the new logon or you can request assistance from the Listowners.
Please include your old, new address and your name in the message.
If you experience problems, reading the individual messages, try turning the MIME option off as explained below.
A digest message follows this general presentation format.
There are 3 messages totalling 4 lines in this issue.
Topics in this issue:
Subject heading 1
Subject heading 2
Subject heading 3
End of Topics (which are also called e-mail "Subject Lines")
----------------------- LISTSERV COMMAND SUMMARY ---------------------
1) Post a message to the List - To: CELIAC@LISTSERV.ICORS.ORG
** Make sure you have a subject line that reflects your topic **
** Selectively quote the previous message, do not repost it **
2) Reach a List owner - To: CELIAC-REQUEST@LISTSERV.ICORS.ORG
3) Get LISTSERV command help - To: LISTSERV@LISTSERV.ICORS.ORG
Message: GET CELIAC WELCOME
4) Unsubscribe from this List - To: LISTSERV@LISTSERV.ICORS.ORG
Message: UNSUB CELIAC
*To reply to the List, instead of poster, send to CELIAC@LISTSERV.ICORS.ORG*
----------------------------------------------------------------------
message 1
-----------------------------
message 2
-----------------------------
message 3
------------------------------
There are many reasons why your e-mail address may be causing error notices, including a full mailbox or transmission problems along the pathway. The high volume of error notices we get makes it impossible for us to research every notice. We do try to warn you of the problem, but usually you will not receive our warning for the same reason that the error notice is being generated. If the bounced message appears to be temporary, the ID is set to digest mode.
(2) If the response shows that you are not subscribed, the system detected serious errors for your ID and automatically deleted it after 4 days of these errors. To regain access, you need to request a new subscription. A database search is required to obtain any missed messages more than seven days old.
(3) If the returned response shows no apparent error or a setting of NOPOST, forward it with background information to the Listowners.
(4) If you receive a response, then the system is operating normally and things are just quiet. If you do not receive a response after several hours, the system may be down. Your choice is to wait, or you can send a message to one of the Listowners and they will attempt to give you an update.
(5) As a convenience for subscribers experiencing network problems, the previous seven daily digests are available. The digest is produced at 11:00 p.m. It will be posted to the appropriate file usually before 8:00 a.m.
To request a copy send a GET command to the LISTSERV(R) for the desired file. Replace "XXX" with the desired day of the week, abbreviated to three letters.
GET CELIAC DIG-XXX
(6) Do not send messages to CELIAC@LISTSERV.ICORS.ORG about a suspected outage, or about problems with your own subscription; this just clutters the mailboxes of all the other subscribers to the list, many of whom have to pay by the line or by the email. Instead, send your message to one of the Listowners. If you don't have the address of one of the Listowners handy, you can send a message to the Listowners
A special file (FILEDESC) has been prepared to summarize the file contents. It is available by sending this command in conjunction with the INDEX command:
GET CELIAC LOG9411
Starting with the 1996 logfiles the format is LOGyymmx, with "x" denoting the week. "x" can be "A", "B", "C", "D", or "E".
You can retrieve any archive file, up to and including the current month's archives. (The current month's archives are updated continuously as each new posting comes in.) Note that the archive files prior to 1996 are VERY large, containing 250-750 Kilobytes each, or about 100-300 pages each.
Fact sheets, newsletters, and other information files are also available for retrieval; a full listing of these can be obtained by using the INDEX command mentioned previously.
Some systems cannot handle large files. If you experience trouble receiving a file, you can break it into parts with the split=nn command, with "nn" indicating the maximum size for each part in kilobytes. (A kilobyte is 1,000 bytes, less than half a printed page.) For example, JUNO users have a limit of about 60 kilobytes per message. A JUNO user would send this command to get the November 1994 log file in parts no bigger than 60 kilobytes:
GET CELIAC LOG9411 split=50
The SEARCH line has several options: by dates, subject, or sender. Here are some examples:
If you find that you are frequently searching the archives, you will find it easier and ultimately faster to download all the celiac logfiles. That way you can use your own computer's search functions instead of the LISTSERV(R). To obtain the logfiles, see the get command above.
The database facility has many features for more complex searches. For a complete description, send in the body of the message to the the StJohns' LISTSERV(R).
It is also possible to do an interactive searches through the St. Johns interface.
INFO REFCARD
The purpose of this copyright is to protect your right to make free copies of this paper for your friends and colleagues, to prevent publishers from using it for commercial advantage, and to prevent ill-meaning people from altering the meaning of the document by changing or removing a few paragraphs.