MAILINS.DOC - Distributed Systems Group RSX Network mail Installation notes
Author: David J. Mitton 	5/14/81

  This is unsupported software that is in use on the Digital Engineering
Network. It is provided here for use by Digital customers as a courtesy.
This software was developed within Digital as a series of midnight projects.
This software has problems (known and unknown) that are constantly being
fixed.

These files are currently in use by the Distributed Systems Software 
Engineering group.  There is a different set of utilities used by
the RSX Group.  They are in the library MAIL.ULB. Extract the file MAIL.RLS
for further information on them.

Mail Sender	Mail Server	Mail Reader	Help files 
NETSND.FTN	MAILSRV.B2S	MAI.CMD		UNSSEND.HLP
NETSND.OBJ	MAILRSX.B2S	MAIL.INI	UNSMAIL.HLP
NETSND.CMD	MAILARC.B2S			MAI.HLP
GINUAB.MAC	MAILSRV.OBJ	Mail Notifier
GINUAB.OBJ	MAILSRV.ODL	MAILNOT.MAC
		MAILSRV.CMD	MAILNOT.OBJ
				MAILNOT.CMD
				MAINOTBLD.CMD


Configuration Options:
(other options are availible in the RSX Group MAIL.ULB)

1)	First RSX format - incoming mail is placed in individual MAIL.TXT
	files in each user's own directory.  Mail is read by processing
	the individual files with standard RSX utilities or with an indirect
	command file reader (MAI.CMD). Also known below as DS Group Format.

The MAILSRV.B2S is the DS group format. You can get the other options
by APPENDING (with the BP2 compiler) either MAILARC.B2S or MAILRSX.B2S
before compiling.

For example, to compile DS Group Format:

RUN $BASIC2
OLD MAILSRV
COMPILE
^Z

Building Mail:

Unless you want to modify Mail, you should only have to build the Notifier
task as it priviledged and goes poking in the device databases.
The task images provided will run on any machine which
has EIS.  (Due to the use of F4P, EIS is a minimum requirement for Mail.)
You should be able to skip reading the rest of this section, and go on
to "Installing Mail"

The .CMD files provided contain enough information to enable building
the programs.  Be sure and use MAILSRV.ODL and .CMD, and not a file
produced by the BP2 compiler.  Note: the command files included are for
V1.5 of BP2.  You will have to modify them for V1.6 BP2. (#$#*&&&!!!)
Also note that BP2 truncates the object file name to MAILSR.OBJ! Rename it.

The Fortran-IV-Plus code does not generate FPP instructions; thus it may
be used on any machine which has EIS (most PDP-11s have EIS).  If you do
not have floating point, check local procedures for using F4P.

Installing Mail:

Install the three tasks; NETSND, MAILSRV, MAILNOT.
Issue the command: NCP SET OBJ 27 NAM MAL$$$ USE DEF VER OFF COP 10
Copy MAI.HLP to the LB:<libuic> on M-PLUS 
	or use seperate copies on 11M.
Move the Help files to the system help directory.
Edit UNS.HLP to point to UNSMAIL and UNSSEND.
Note that MAI.HLP is set up to be used under M-Plus.
  It must be modified to be used under 11M.

Using the MAI.CMD, Mail Reader:

On M-Plus systems this is best done through the system command catchall
facility of TDX (...CA.). To enable command file catchall,
	ASN SY:=ZZ2:
Then the command
	MAIL
will work like an installed program.
On vanilla M systems, you will have to make separate copies or just
indirect to a shared copy.
	@LB:[1,54]MAIL


Creating the Routing File and the Forwarding/Filter File:

1. LB:[1,2]MAILNODE.DAT is the routing file and contains lines of the form:
   nodename poor::mans::routing::to::nodename::
   e.g.
   ARK BABEL::GALAXY::STAR::VAX4::ARK::


   If you wish, you may initially create a null file:

	PIP LB:[1,2]MAILNODE.DAT=NL:

	NOTE: This file is also used by PMR (the passthrough task)
	to connect to unknown nodes or for alternate paths.

2. LB:[1,2]MAILUSER.DAT is the Forwarding/Filter File and has lines like:
   localname->nodename::nodefurther::distantname
   localalias->localnameoraccount
   localname->(Error message)
   e.g.
   LUSER->CORRECT::NODE::LUSER
   SYSTEMMANAGER->WATSON
   SMITH->(Smith - Send to JSMITH or GSMITH or BSMITH)
   BSMITH->[231,277]
   COMMENT LINE

   (Any line which does not contain "->" is a comment.)

   An optional feature (called ABSOLUTE filter) requires that all users who
   will receive mail on this node be entered in the Filter File.  An entry
   of the form NAME->NAME is sufficient if no translation is required.  To
   activate this feature, a line BEGINNING with "->" (in column one) is
   placed at the END of the Filter file.  This line contains the message to
   be returned to the person trying to send mail.

   e.g.
   -> does not read mail on THSNOD
   The user's name, followed by the message will be returned as an error.

   THE ABSOLUTE FILTER IS USEFUL TO PREVENT THE SENDING OF MAIL TO
   INACTIVE OR INAPPROPRIATE ACCOUNTS.

Terminal notification happens by MAILNOT tracking down the terminals
with the correct UIC.  If privileged users have changed their UIC, they
will not be notified of incoming mail.