🚀 go-pugleaf

In article <1992Aug7.141732.23923@meaddata.com> michelle@meaddata.com (Michelle  
Buck) writes:
> I've a simple question I need answered...I seem to remember that
> there is some way to get submissions from various archive directories
> (such as from the sonata.cc.purdue.edu directory) via email, but I
> can't recollect the proper procedure.

In a sentence: send mail to archive-server@cc.purdue.edu
whose body contains a list of commands.

The long form, which is based on part of the new version of
the help file I've been playing with follows:  

                   PURDUE UNIVERSITY COMPUTING CENTER
                          NeXT ARCHIVE SERVER
                           LIST OF COMMANDS

The following is a list of commands and their descriptions supported by
Purdue University Computing Center for the NeXT archive server.  They
are listed here in alphabetical order.  


help          Sends a general help file for file submissions and
              requests.

submission    Putting the key word 'submission' in your subject line
              (and only in your subject line!) will tell the archive
              server to send the enclosed document to the archive
              moderator for inclusion into the archives.  NeXT
              attachments are welcome.  Please include a description of
              your submission and the minimum release required to run
              your software.

path <mail-path>   "Path" is used to override the mail path that the
                   archive server chooses from the header of your mail
                   message.  You should use this whenever you know that
                   the return address of your message will not be useful
                   to the archive server.  The archive server only knows
                   about internet domain.  This means that the archive
                   server understands name@site.edu, but NOT
                   name@site.bitnet or name@site.UUCP.  There are two
                   sites on campus which can forward to UUCP addresses
                   and one which can forward to bitnet addresses.  The
                   two UUCP sites are "purdue" and "pur-ee".  The bitnet
                   site is "vm.cc.purdue.edu" (known on the BITNET side
                   of the world as PURCCVM).

    To route mail to a UUCP site, I'd suggest first omitting the "path"
    directive and letting the archive-server attempt to guess.  However,
    if your mail is not returned (or is returned with errors) you might try 

    wellknownsite!yoursite!yourname@uunet.uu.net

    or

    wellknownsite!yoursite!yourname@ee.ecn.purdue.edu

    or

    wellknownsite!yoursite!yourname@cs.purdue.edu
    
    If you have any doubts about your mail address, you should ask
    your system administrator for a correct domain style address.
    Two examples uses of "path" are


       path mrd@sun.soe.clarkson.edu
       path wellknownsite!yoursite!yourname@uunet.uu.net

  index [archive...]

    "Index" mails to you a listing of the files in the specified
    archives.  If an archive is not specified, then the index of the
    available archives will be sent.

  send <archive> <file..>

    "Send" mails to you the files in the specified archive.  All of
    the files that you request will be sent to you archived together
    (see "archiver"), possibly packed (see "pack"), possibly encoded
    (see "encoder") and split up into messages that are small enough
    to be mailed (see "size").  If you specify an archive and do not
    specify any files, then all of the files in that archive will be
    sent.  You may have as many "sends" in the body of your mail
    message as you wish.

  encodedsend <archive> <file...>

    "Encodedsend" is identical to the command "send" except that the
    files are guaranteed to be encoded (see "encoder").  This is
    useful if you know that the return message will go through EBCDIC
    based computers.

  archiver <archiving-method>

    You may specify the method of archiving (merging a group of files
    into one large file) the files with "archiver".  By default, files
    that are mailable are simply stuck together with the text "cut
    here" between files and; non-mailable files are archived via unix
    tar.  The available archiving methods are:

      arc (the PC program)
      none (the files are simply stuck together)
      shar (Unix sh script)
      simple (the files are separated by "cut here" - default)
      tar (Unix Tar - default for non mailable files) 
      zoo (Unix, VMS, PC's)
      dclshar (VMS, creates a file you can unpack with @FILE.COM)
      nextmail (NeXT mail format)

  pack <packing-method>

    You may specify that the files be packed (compressed) before
    delivery.  This has the advantage that the mail files will be
    smaller.  By default the files are not packed. The available
    packing methods are:

     compress    (the Unix command compress)
     none
     # This site does not support compact.
     compact     (the Unix command compact - slower than compress)

  encoder <encoding-method>

    Non-mailable files must be converted to something mailable.  By
    default this is done with "uuencode".  You may also specify that
    the files must be encoded with the command "encodedsend."  The
    available encoding methods are:

      uuencode (default)
      btoa

      # This site does not have rscs as an encoder.
      rscs

  size <max-file in bytes>

    The archive server splits files up so that they are smaller than
    this limit.  This is done because many sites have a maximum mail
    size limit.  A value of 0 means that there is no limit.  The
    archive server has a default size limit of 300000 bytes.  You may
    change this if you know that you have different limits.  Most (but
    not all) uucp sites have a limit of 100000 bytes.  Internet and
    Bitnet sites should set this to 300000 bytes.

  length <number>

    Many mailers will truncate long lines.  To overcome this the
    archive server encodes files that contains lines that are longer
    than 130 characters (see "encoder").  If you know that your mail
    files will not be truncated then you can set this value to
    something larger.

  limit <number>

    The archive-server limits the amount of data that will be returned
    by any one request.  This limit is very large.  By using this command
    you may lower this limit.  This is typically done to prevent errors
    by the user.

  search <string> <archive> <file...>
 
    You may search through the archive for a string.  A string is
    considered to be any sequence of alphanumeric characters; case
    does not matter.  If you only provide an archive name then all of
    the files in the archive will be searched.  You will be returned
    all lines that contain the string.

  find  <string...>
    
    You may search for file names that contain the given string.  Case
    is significant in the string.  You will be returned all file names
    that match the given string.

                               EXAMPLE

Here is an example message that you could send to the archive-server.
It gives an example of all the supported commands.

------
help
path mrd@sun.soe.clarkson.edu
index latex-style res.sty
encodedsend latex-style res.sty res-sample.tex
send isetl
archiver tar
pack compress
encoder rscs
size 200000
length 80
search resume texhax texhax.89.001 texhax.89.002
find resume
-----

                               APPENDIX

1) Files are considered mailable if they do not have any lines longer
than 130 characters and do not have any characters other than tabs,
carriage returns, newlines, vertical tabs, formfeeds and characters
between space through tilde (using ascii ordering).

2) If you have problems or questions, you should send mail to
archive-management@cc.purdue.edu

3) If you have an archiving, packing, encoding program that runs under
BSD Unix that I do not have and you would like me to support then
please send it to me.  It is very easy to incorporate it into this
package.

4) The archive server was written by Michael DeCorte.  It consists
of groups of Bourne shell and awk scripts designed to work under
BSD Unix based computers. There are no restrictions on its
redistribution provided the copyright notice is left intact.  The
original sources for the archive-server can be obtained via anonymous
ftp to sun.soe.clarkson.edu or by sending messages in the format
given above to archive-server@sun.soe.clarkson.edu (of course you
won't get any of the modifications this site has added for NeXT
support).  Any further inquiries can be sent to
archive-management@cc.purdue.edu.

5) Unix is a registered trademark of AT&T.

archive-management@cc.purdue.edu
Submissions to:  archive-server@cc.purdue.edu with the
subject line 'submission'