The following text was lifted straight out of the BinkleyTerm 
Version 2.30 User's Guide, Written by Alan D. Applegate in 1989.

Every attempt has been made to preserve the function and format
of the original OKFILE as described here.

                         ----------------------          

The first file, OKFILE, is a machine-read listing of files,
complete with drive and path, that you will allow to be sent to
remote systems via file request.  The file is designated with the
'Okfile' statement in the configuration file.  Wildcards are
allowed, and nearly always used.  When an incoming request is
received, the request is checked against the OKFILE to see if you
permit the file to be sent.  
          
The OKFILE also allows you to implement "magic filenames" which
are words used to represent a file.  If someone requests
"BINKLEY" from you, for example, you could set-up your OKFILE in
such a way as to send BEXE_150.ARC in return.  This frees the
person making the request from having to know the exact filename
of the file he wants.  This is generally used by systems which
are software distribution points, hubs, and so on.
          
Password protection may also be implemented with the OKFILE,
making a password required in order to receive a particular file
or group of files.
          
A sample OKFILE:
          
   b:\aprog.ARC
   c:\file\stuff\*.*
   c:\file\programs\wlc*.txt
   c:\file\private\*.* !mypass
   @BINKLEY c:\file\dist\bexe_150.arc 
   @MYEDIT !outpass c:\file\private\editmax.arc
          
The first line gives an exact filename.  The second and third    
lines show the use of wildcards.  The fourth line shows password
protection, with an exclamation point (!) followed by the
password.  The fifth line shows a magic filename, an 'at' symbol
(@) followed by the magic filename, followed by an exact drive,
path and filename designation.  The sixth line shows a magic
filename with password protection.
         
Note that in all cases, a password (if any) is always the second
argument in an OKFILE entry.

          
The next special file is the AVAIL file, and is designated by the
'Avail' statement in the configuration file.  When someone
requests the magic filename "FILES" BinkleyTerm will send this
file.  It is a list of the files you have available for request,
in human readable form.  This is a flat ASCII text file, and
should feature the name of the file, and usually its size in
bytes and a short description of the file.  There are utilities
available that can construct this file automatically based on
your BBS system's internal listings.  Of course, it could also be
manually created.
