Subject: | |
From: | |
Reply To: | Forum on LISTSERV release 1.7 |
Date: | Mon, 29 Jul 1991 19:31:34 CDT |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
On Mon, 29 Jul 1991 18:28:29 EDT Lisa M. Covi said:
>I have a filelist that would be best owned and/or updated by a user
>with an Internet address. I am also interested in finding out if/why
>Internet users can own lists and update files in a filelist.
>
We have several owners and file contributors who use "internet" addresses.
They are on all sorts of systems. The LISTSERV pm still would have to set up
the FILELIST structure and probably some generic filename patterns so all the
user would have to do is send mail to LISTSERV with the first line being the
PUT.
Here is the condensed version of notes I've used in the past. About the only
problem we've had is in trying to delete a file and the user's mail system
insists on inserting a blank record after the PUT. Instead of deleting the
file it is replaced with a single blank line. Haven't found a way around that
yet but it is a rare problem found only on a few of the remote owner systems.
Marty
How to Store a File in a FILELIST via e-mail
The following gives techniques to be used to store text files with
records of 80 characters or less via e-mail.
1. You have to be authorized to store files of the given names in
the filelist. Contact [log in to unmask] to have this done.
Authorization includes setting up a file "template" with a part of
the filename being agreed upon (so LISTSERV can recognize it).
We also need to know the "From:" address on the mail from the
maintainer. Usually a special "password" is also assigned.
2. Send the mail to [log in to unmask]
with the first line of the BODY/TEXT of the mail (ie. the line
after the blank line which follows the headers) with:
PUT filename filetype filelist "TITLE=...description of file......" PW=password
Either the filename or filetype (or parts of them) must match the template
defined in the filelist! The filename and filetype may be up to 8
characters long and consist of letters (A-Z), digits (0-9) and
if you want, special characters: "+-_:@#$". Note that you may NOT
use a period (".") in the name and some systems may have problems
handling even the special characters allowed.
The filelist is the collection of files to be used (eg. ROOTS-L,
POWER-L, etc.). This is determined in step 1.
You can have about 30 characters of comments in the TITLE= field (which
must be enclosed in double quotes as shown). This shows up on the output
of the "INDEX filelist" command.
The password is the one agreed to in step 1.
Please note that only ONE blank line is allowed. It is the blank
line (or CR/LF) that normally follows the mail headers.
The file should start on the line immediately following the PUT.
ALL lines following the PUT until the end of the mail will be
considered part of the file (ie. a signature if you added one...).
3. Follow the PUT command immediately with the text to be stored. You will
get acknowledgement from LISTSERV that the file has been stored. To
verify that the command worked you may use the
INDEX filelist and/or
GET filename filetype commands (send them to [log in to unmask]).
For example, mail to add FEATHER INTRO to filelist FOWLFILE might
look like this:
Date: Mon, 3 Sep 90 15:03:03 CDT
From: Donald Duck <[log in to unmask]>
To: [log in to unmask]
Subject: Featherbedding (Note: Ignored)
PUT FEATHER INTRO FOWLFILE "TITLE=Intro to Feather Beds" pw=noloons
Feathering the Nest: An Introduction
The most important thing about a nest is where it is located.
You want to avoid predators like skunks, mink, and racoons not
to mention Elmer Fudd...
...etc...
4. To replace a file simply submit the PUT command with the new file
following in exactly the same way.
5. To DELETE a file from the filelist completely, send the PUT command
as the ONLY line of text (ie. be sure the mail ends immediately
after the line with the PUT command on it).
If you have any questions please let me know. Thank you!
Marty Hoag [log in to unmask] [log in to unmask]
>Thanks
>Lisa Covi
>BITNET Support
|
|
|