Echoes Maillisten-Handling

 

 

CONTENTS


# introduction to echoserv
#
quick note to those that just want off
#
addresses of note
#
using the server
#
server databases
#
commands - an intro
#
quit command
#
subscription commands
#
subscription commands - realtime
#
subscription commands - digest
#
un-subscription commands
#
file list commands
#
file retrieval commands
#
misc. commands


# introduction to echoserv

this is the help file (such as it is) for "echoserv". what is that? echoserv is the automated mail server for the pink floyd mailing list "echoes".

if you what you need cannot be satisfied by the capabilities of the server, or you are otherwise having trouble getting it to do your bidding, please contact the administrivia address (below).

# quick note to those that just want off

if you want to get off the list, you should be able to use echoserv, as follows:

mail to: echoserv@meddle.org, in the body of the message put: "delete echoes" or "quit"

expect a confirmation from echoserv as it deletes your address from the list. if your address has somehow changed, echoserv will not be able to find you -- in such cases please contact the administrivia address (below).

please be advised that unsubscribing will stop new mail from being sent your way, but does nothing about de-queueing any mail which might have been delayed and is still in transit. (sorry.)

# addresses of note

submissions: echoes@meddle.org
administrivia:  echoes-request@meddle.org
automated mail server: echoserv@meddle.org

# using the server

now, as for using the mail server, it is nearly as easy as 1,2,3...

1. commands go in the body of a message only (the subject is ignored.)
2. *only* commands go in the body of a message.
if you (or your mailer) must include a sig, please be sure to use the "quit" command (see below.)
3. for all commands where your address is to be included, *please* make
sure that the address is both complete and accurate. e.g. if you want to get off the list, then mail to
echoserv@meddle.org, in the body of the message put "delete echoes" or "quit".

# server databases

echoserv is capable of maintaining and allowing access to multiple databases. in the file commands (see below) echoserv must be provided with the name of the desired database from which to extract the desired file. 

echoserv is presently maintaining many databases (enough that i will just list the most important ones -- check it out using the "index" command, described elsewhere in this write up.) first among these is the "echoes" database. this consists of the faq, digest back issues for the current volume, etc. back issues for other than the current volume are now in separate databases, "echoes-vol1" for volume 1, etc. information on tour dates, reviews, stats, and the like will be found in the "echoes-tour" database. information on standard releases is stored in the "rolo" database. rolo is an acronym for "recordings of legitimate origin" and it    encompasses both the standard stuff you can buy at your local music store as well as the legal/licensed promo and "radio only" released types of material material. for stuff which doesn't quite fit that description, read on....
the next database is "roio".
an acronym that you will often see used on echoes (and elsewhere -- its    use is spreading) in place of the (read on) b-word. the "roio" database contains large amounts of information on what we    call "recordings of [illigitmate, indiscriminate, etc.] origin" in the cd format.
and then there is the "roio-lp" database.
it is for roio's in lp format.

still wondering what the b-word is? hint: consider the type of footwear good for hiking....  call them  collectors' editions, or whatever, but not b**ts. electronic mail is not secure, and easily lends itself to eavesdropping. so, since i'd rather not have any undue attention brought to this little venture, don't use the b-word. 

there are 2 databases dedicated to useful shareware and public domain software. these are "pc-code" and "sun4-code" which have (oddly enough :-) code in them for pc's (msdos) and sun (sparc unix) machines. the code files here are uuencoded, so you'll need uudecode as a minimum. the final database is daily traffic from "eclipse" the precursor to "echoes."

# commands - an intro

echoserv will parse each line of received mail and mail a reply for valid commands as they are handled. in the event that echoserv cannot parse commands from a received post, it will so notify the sender. commands to echoserv come in several categories:
                quit command
                subscription commands
                un-subscription commands
                file commands
                misc. commands
each of these are described below with unix style templates: first
the commands will be named and summarized. the second element is a synopsis of the command useage template. care must be taken in the use of the template: some of the information (e.g. the command name) must be entered precisely and some things require that a real value (e.g. an address or filename) be provided and that a bit of intelligence be applied. finally there is a mass of pertinent information lumped as a description.
reading of the descriptive section is highly recommended, as it
may contain useful information and hints about the consequences of dealing with echoserv in a specific way.

 

# quit command
name quit - stop command parsing
end - stop command parsing
b!uK - stop command parsing
synopsis quit
end
b!uK
description

echoserv is the automated mail server for the pink floyd mailing list "echoes". NB: the word automated -- it will do a *very* limited set of things as described herein. as it cannot cope with the signatures often appended to mail, this command can be used to cause echoserv to ignore everything which follows. this can also be useful if both server commands and general text must appear in the same post: just put all the commands first, end them with a 'quit' command, and then go ahead and add whatever else is to be included. but be warned that nobody will look at it if it is sent only to echoserv, only if you have cc'd somebody in addition.

examples commands are used exactly as in the synopsis above.
 
# subscription commands
name add - add sender to the echoes digest list
add-digest - add sender to the echoes digest list
add-realtime - add sender to the echoes realtime list
synopsis add echoes
add-digest echoes
add-realtime echoes
description these are the basic commands used to request echoserv to begin a subscription to echoes. nb: the default subscription form is now digest. more complex forms of these commands are discussed below. the echoes list is available to subscribers in both realtime and digest forms.  this means that subscribers get to choose whether they want to receive submissions immediately as they appear or to receive a tidy little bundle once a day. some consideration should be given to this choice. those considering a realtime subscription should be aware that peak traffic can easily amount to 50 or more posts a day. see the section titled 'subscription commands - realtime' those considering a subscription to the digest should be aware that they will get one package per day and that sometimes this package can be quite bulky -- NB: some mailers have defaults set which cause them to choke on posts bigger than 100K and the digest has been known to exceed that. see the section titled 'subscription commands - digest' subscription to one format does not preclude subscription to the other format.
examples commands are used exactly as in the synopsis above.
 
# subscription commands - realtime
name add-realtime - add sender to the echoes realtime list
s
ubscribe-realtime - begin sender's subscription to realtime echoes
synopsis

add-realtime echoes
s
ubscribe-realtime echoes

description these are the basic commands used to request echoserv to begin a subscription to the realtime feed from echoes. some consideration should be given to this choice. those considering a realtime subscription should be aware that peak traffic can easily amount to 50 or more posts a day. the command will use the address of the sender as the subscription address. if the sender's return address is inappropriate and you'd like another one used as the subscription address, then you must contact the administrivia address: echoes-request@meddle.org

examples

commands are used exactly as in the synopsis above.
# subscription commands - digest
name add - begin sender's subscription to realtime echoes
subscribe - begin sender's subscription to realtime echoes
add-digest - begin sender's subscription to the echoes digest
subscribe-digest - begin sender's subscription to the echoes digest
synopsis add echoes
subscribe echoes
add-digest echoes
subscribe-digest echoes
description these are the basic commands used to request echoserv to begin a subscription to the echoes digest. some consideration should be given to this choice. those considering a subscription to the digest should be aware that they will get one package per day and that sometimes this package can be quite bulky -- NB: some mailers have defaults set which cause them to choke on posts bigger than 100K and the digest has been known to exceed that. the command will use the address of the sender as the subscription address. if the sender's return address is inappropriate (e.g. you are at work and you just found out about echoes) and you would like another one used as the subscription address (e.g. your private machine or connection because your boss would kill you if you signed up using one of the machines in his department), then you must contact the administrivia address: echoes-request@meddle.org

examples

commands are used exactly as in the synopsis above.
# un-subscription commands
name delete - cancel all of sender's subscriptions to echoes
unsubscribe - cancel all of sender's subscriptions to echoes
synopsis delete echoes
unsubscribe echoes
description these are the commands used to request that echoserv cancel all of a user's subscriptions to the echoes digest. the command will use the address of the sender as the subscription address to process. to change from realtime to digest, or vice versa, one must first delete oneself from the list and then add oneself back in the desired mode. NB: it is possible to be on both realtime and digest forms of echoes: failure to delete oneself is the easiest way to do this. please also note that these commands should not be sent to the list, they should be sent to echoserv. if you have any problems, then you must contact the administrivia address:  echoes-request@meddle.org

examples

commands are used exactly as in the synopsis above.
# file listing commands
name filelist - mail a list of available files to the requestor
dir - mail a list of available files to the requestor
ls - mail a list of available files to the requestor
synopsis filelist DATABASE
dir DATABASE
ls DATABASE
description these are the commands used to request that echoserv return a list of available files for the listed DATABASE. current databases include, but are not limited to: echoes    eclipse roio  roio-lp see the "index" command to see how to get a complete and current list.

examples

the response from echoserv will be a list of files with size (see note below) and date info. if you send the command filelist roio the response will look like:
Available file list for 'roio'
4184 Feb  9 20:12 00readme
10895 Feb  9 20:12 0index
10892 Feb  9 20:12 0timeindex
5224 Feb 15  1993 8th_rd_from_the_moon.cd
20292 Apr 22 22:22 testfile (.Z)

please note that if the filename is followed by (.Z) as seen just above, then the file size is the compressed size and what will actually be sent to you is _larger_ by some amount. a good guess is that it will expand to about twice the listed size.

# file retrieval commands
name mail - mail a file back to the requestor
send - mail a file back to the requestor
get - mail a file back to the requestor
synopsis mail DESIRED_FILE DATABASE
send DESIRED_FILE DATABASE
get DESIRED_FILE DATABASE
description these are the commands used to request that echoserv return one of the files. for each file desired, the user should use a separate command. filenames must be as returned by the filelist command - no wildcards or pathing allowed. returned files are sent in straight ascii: no compression, no encryption, no nothing. returned files are sent one file per message.

examples

getting the current issue of the echoes digest, the faq, and the "8th road" roio (ref section above) and the "testfile" in the roio database (op. cit.) would be done with the commands:
mail current.issue echoes
mail echoes.faq.1 echoes
mail echoes.faq.2 echoes
mail echoes.faq.3 echoes
mail echoes.faq.4 echoes
mail echoes.faq.5 echoes
mail echoes.faq.6 echoes
mail echoes.faq.7 echoes
mail echoes.faq.8 echoes
mail echoes.faq.9 echoes
mail echoes.faq.10 echoes
mail 8th_rd_from_the_moon.cd roio
mail testfile roio

sending the above set of commands in a single message to echoserv will result in 13 separate replies: one for each file requested. nb: do not postpend the .Z to the filename, even though the information returned by the "filelist" command contains an indication that the file is stored in compressed form.

# misc. commands
INDEX index - confirm existance of echoes
longindex - return introductory information file
synopsis index
longindex
description

index will cause one to get some mail back that lists the different databases supported by echoserv. to get some mail back with the names of the databases and whatever brief explanation for each exists,  just use the 'longindex' command.

examples

commands are used exactly as in the synopsis above.
PING ping - register a "keep me on" request with the server
synopsis ping
description this command is used to get one's address removed from the "purge list" that will be used as the basis for a periodic purging of the subscriber list. at intervals, the purge list is fed to the server and all addresses which remain on the purge list at that time are deleted from the list of echoes subscribers. sending a "ping" command to the server should prevent your address from being deleted as part of a purge.

examples

commands are used exactly as in the synopsis above.
HELP help - return this help file to the sender
synopsis help
description this command is used to get one's very own copy of this thing. if what is needed cannot be satisfied by the capabilities of the server, or echoserv is otherwise giving trouble about doing one's bidding, please contact the administrivia address. NB: when echoserv cannot get a valid command from what it was sent, it will interpret same as a cry for help and will return a copy of this file.

examples

commands are used exactly as in the synopsis above.