Trailing-Edge
-
PDP-10 Archives
-
T10_T20_MS_V10_SRCS_830128
-
msinst.rno
There are no other files named msinst.rno in the archive.
.title DECmail/MS Installation Guide
.autoparagraph
.flags hyphenate
.flags break
.left margin 0
.right margin 72
.blank 4
.center;DECmail/MS Installation Guide
.blank 2
.require "msver.rno"
.blank 2
.header level 1 Sum=mary
This docu=ment de=scribes how to install DECmail/MS on either
a TOPS-10 or a TOPS-20 system. Where references to other soft=ware
modules are required, we refer the reader to the ap=pro=priate
doc=u=men=tation for the module in question. We assume that the
reader is familiar with oper=ating system commands and at least one
editor, and can compile, link, and save pro=grams based on
instructions in a batch control file.
The in=stal=lation instructions are divided into two sections.
The first sec=tion de=scribes in=stal=lation of DECmail/MS on a
TOPS-10 system. The second part de=scribes in=stal=lation of
DECmail/MS on a TOPS-20 system. Each sec=tion ends with an
In=stal=lation Certification Pro=ce=dure (ICP). The ICP is a simple,
manual pro=ce=dure you can perform to assure yourself that you've
cor=rectly installed all the required pieces of the soft=ware and that
the pro=duct is functioning properly.
Please read this en=tire docu=ment through before beginning
your in=stal=lation.
.note CAUTION
Before in=stal=ling DECmail/MS, be sure you've read the Beware file
for DECmail/MS com=pletely. It con=tains cautionary notices and
monitor patches required before in=stal=ling DECmail/MS.
.end note
.header level 1 Distribution tape
There are three forms of dis=tri=bu=tion tape for DECmail/MS:
.list
.list element;DECmail/MS for TOPS-10 systems
.list element;DECmail/MS for TOPS-20 systems, local mail only
.list element;DECmail/MS for TOPS-20 systems, with net=work mail
.end list
Each tape con=tains three savesets. The first saveset
con=tains doc=u=men=tation (such as this file); the second saveset
con=tains the executable images you install on your system; and the
third saveset con=tains REL files that are used to build the
soft=ware. You need not keep the REL files on=line, or do anything
with them at in=stal=lation time. They are sup=plied in order to
pro=vide a base on which patches may be installed, should any patches
be necessary.
One of the files in the first saveset is called MS.DIR. This
is a checksummed di=rec=tory of the tape. Before proceeding with the
in=stal=lation, take a checksummed di=rec=tory of your tape, and
compare the checksums you get with the checksums in MS.DIR. Except
for MS.DIR itself, the checksums should match. If they do not, you
may have a damaged tape; con=tact Digital for a replacement.
.header level 1 Installation of DECmail/MS on TOPS-10 systems
.header level 2 Installation instructions
There are five basic steps to the in=stal=lation of DECmail/MS on
TOPS-10 systems. They are:
.list 1,"o"
.list element;Step 1 - Compile and link LGNMS to LOGIN###(7.01 and 7.01A only)
.list element;Step 2 - Enter MS in PRVTAB###(7.01 and 7.01A only)
.list element;Step 3 - Define the MS monitor com=mand###(7.01 and 7.01A only)
.list element;Step 4 - Install files
.list element;Step 5 - Create STD:USERS.TXT
.end list
.header level 3 Step 1 - Compile and link LGNMS to LOGIN
.break
LGNMS is a module which, when linked with LOGIN (the CUSP
that logs timesharing users in to the system), notifies users when
they log in that they have new mail. The way you link it to LOGIN
depends on the ver=sion of LOGIN you have.
.header level 4 Rebuilding LOGIN
Before compiling and linking LGNMS, you must recompile LOGIN
so that it calls LGNMS. You will find instructions for recompiling
LOGIN in the BUILD.CTL file dis=tri=buted with the monitor. Look for
the tag LOGIN::, which precedes the sec=tion of the control file that
rebuilds LOGIN.
The way to recompile LOGIN with the LGNMS hook depends on
which ver=sion of LOGIN you have.
.header level 5 LOGIN version 61(751)
.break
LOGIN ver=sion 61(751) has the LGNMS hook, but en=closed in
a REPEAT 0. Look for the PUSHJ P,RNMAIL_#_# in LOGIN.MAC, and remove
the REPEAT 0 con=ditional around it. Now recompile LOGIN.
.literal
Example:
.COMPILE/COMPILE LOGIN.MAC
.COMPILE/COMPILE FACTOR.MAC
.end literal
.header level 5 LOGIN version 62(1005)
.break
LOGIN ver=sion 62(1005) has a con=ditional as=sembly switch
called FTMAIL in=stead of the REPEAT 0. Just set FTMAIL to -1 and
recompile LOGIN.MAC.
.literal
Example:
.COMPILE/COMPILE LOGIN.MAC
.COMPILE/COMPILE FACTOR.MAC
.end literal
.header level 4 Compile LGNMS
One of the output files produced when you recompile LOGIN is
the LOGIN uni=versal file, LGNUNV.UNV. Using this file (just make
sure it's in the di=rec=tory you're working from), compile LGNMS.MAC
from the tape, producing LGNMS.REL.
.literal
Example:
.COMPILE/COMPILE LGNMS.MAC
.end literal
.header level 4 Link LGNMS with LOGIN
.break
Once you've compiled LOGIN and LGNMS suc=cess=fully, link them
to=gether. Refer to the batch control file (BUILD.CTL) shipped with
your monitor; there is a tag called LOGIN:: that precedes the LOGIN
build pro=ce=dure. Follow the pro=ce=dure documented there for
linking LOGIN, except that you must add the module name LGNMS to the
LINK com=mand line. Install the LOGIN.EXE thus created on SYS:.
.literal
Example:
.R LINK
*LOGIN/SSAVE=LOGIN,LGNMS/GO
.COPY STD:=LOGIN.EXE
.end literal
.header level 3 Step 2 - Enter MS in PRVTAB
.break
Under TOPS-10, ver=sion 10 of DECmail/MS delivers mail by
appending each mes=sage directly to the end of each recipient's
MAIL.TXT file. In order to have the privileges to do this (since the
recipient's MAIL.TXT resides in a dif=ferent PPN than the sender's),
MS must run with the JACCT bit. To accomplish this, MS must be
entered in the monitor table PRVTAB.
PRVTAB is a table which is de=fined in COMCON.MAC. Edit
COMCON.MAC and find the label PRVTAB. The beginning of this table
looks like this:
.literal
;TABLE OF PRIVILEGED CUSPS
;USED TO TURN ON JACCT WHEN R OR RUN COMMAND OR RUN UUO
PRVTAB:
LGONAM::SIXBIT /LOGOUT/ ;NAME FOR "LOGOUT" (TURN OFF JLOG TOO)
SIXBIT /LOGIN/
QUENAM: SIXBIT /QUEUE/
SIXBIT /SPRINT/
.end literal
Add the fol=lowing line anywhere in the table:
.literal
SIXBIT /MS/
.end literal
Ordering of the entries in the table is not sig=ni=fi=cant, so this
line may appear anywhere in PRVTAB.
.header level 3 Step 3 - Define the MS monitor command
.break
To define the MS monitor com=mand, edit the file COMMON.MAC
and look for the de=fi=ni=tion of the NAMES macro. The beginning of
this de=fi=ni=tion looks like this:
.literal
DEFINE NAMES<
C <>,CBLANK,NOCORE!NOJOBN!NOLOGIN!NOINCK!NOCRLF
C START,START,NOPER!TTYRNU!INCORE!NOACT!NORUN!NOLOGIN!NOJOBN
C .HALT,STOPF,NOCORE!NOJOBN!NOLOGIN!NOINCK!CMWRQ
.end literal
The fol=lowing line must be added to the de=fi=ni=tion of the
NAMES macro:
.literal
C MS,RUNAME,RUNFLG
.end literal
Ordering of the entries in this macro is not sig=ni=fi=cant, so this
line may be added wherever you like. Just be sure it's not inserted
inside a con=ditional which is turned off in your monitor.
Now that you've edited COMCON.MAC and COMMON.MAC, follow the
instructions in the TOPS-10 Monitor In=stal=lation Guide, and build
and install your new monitor. Briefly, this involves recompiling
COMMON.MAC, recompiling your con=fig=uration-de=pen=dent files using
the new ver=sion of COMMON.MAC, recompiling COMCON.MAC, and then
replacing the copy of COMCON in TOP_?10.REL with the one you just
assembled (using MAKLIB), and linking and saving the monitor in the
usual way.
.test page 12
.header level 3 Step 4 - Installation of files
.break
The fol=lowing files should be copied as indicated:
.literal
File on distribution medium Where to copy it
--------------------------- -------------------
MS.EXE SYS:
MS.HLP HLP:
MS.INI STD:
MS.DOC DOC:
.end literal
.header level 3 Step 5 - Create STD:USERS.TXT
.break
With DECmail/MS, people are referred to by name. Since
TOPS-10 refers to people by number (PPN), a method for associating
names and numbers is required. This is the file STD:USERS.TXT. It is
a simple text file, which you can create with any editor, which
defines the correspondence between usernames and PPNs
(Project-Programmer Numbers).
.break
A USERNAME is a continuous string of cha=rac=ters; only the
fol=lowing cha=rac=ters are valid in user=names: letters, digits,
hyphens, and dots.
STD:USERS.TXT is a text file which contains one line per user.
Each line contains a file structure name, a colon, a PPN, a comma, and
then the username. PPNs and user=names should be unique (that is,
don't assign two names to the same PPN, or two PPNs to the same name).
.note
USERS.TXT can con=tain at most 1400 entries, which means that a TOPS-10
system can sup=port at most 1400 DECmail/MS subscribers.
.end note
Here is a sample USERS.TXT:
.literal
DSKB:[10,4432],Farke
DSKB:[33,5513],Gar
DSKE:[127,4454],Fred-from-purchasing
DSKE:[107,2],Operator.at.node.107
DSKX:[12,667],BigEd
.end literal
UFDs must exist corresponding to each entry in STD:USERS.TXT.
If you attempt to send to a user who does not have a UFD corresponding
to the area de=fined for him in STD:USERS.TXT, then DECmail/MS will
produce the fol=lowing error mes=sage:
.literal
?Can't send message because: Non-existant UFD
.end literal
.break
.test page 12
.note
In order to insure that a UFD always exists into which mail can be
received, it is a good practice to create an empty file in each UFD
named in USERS.TXT (because LOGOUT normally deletes empty UFDs).
Protect this file <777> to pre=vent accidental deletion. You may wish
to call this file MAIL.NUL or MAIL.000, or some=thing like that, to
indicate its purpose.
.end note
Users who are not registered in STD:USERS.TXT cannot use
DECmail/MS; they can neither send nor receive mail. Running MS for
them will produce the fatal message "?You are not registered in
SYS:USERS.TXT".
.header level 2 Installation Certification Procedure (ICP)
Before run=ning the ICP you must be sure that you're run=ning
with the modified monitor you built, con=taining the MS com=mand.
This means that after having built and installed the monitor, you must
reload your system.
Make sure that the user list, STD:USERS.TXT, con=tains an
entry for PPN [1,2] called "Operator". Make sure that this entry
refers to a file struc=ture that is always on=line, and on which a
[1,2] UFD exists and has unused disk space.
Next make sure that you, the person doing the pro=ce=dure, has
an entry in STD:USERS.TXT that also refers to a struc=ture that is
on=line and on which you have a UFD. This UFD must be for a PPN that
is NOT in project 1; that is, do not run the ICP from any PPN of the
form [1,*].
Log in to your (non-project-1) PPN. In response to the
monitor prompt (.), type the MS com=mand. MS should start up and
in=form you that you have no mes=sage file.
If you get the fol=lowing error mes=sage from the monitor in
response to the MS com=mand:
.literal
.MS
?MS?
.end literal
then the MS com=mand has not been cor=rectly installed. Check to make
sure that you cor=rectly edited COMCON.MAC, and built and loaded a new
monitor con=taining the MS com=mand.
If MS complains that it can=not find STD:USERS.TXT, check to
see that this file is properly installed.
If MS complains that "?You are not registered in
STD:USERS.TXT", check USERS.TXT to see if the PPN under which you're
logged in is listed.
If MS complains about the format of USERS.TXT, check to see
that you've followed the instructions for creating this file.
Once you've suc=cess=fully started MS up, try sending mail to
the operator. The typescript should look some=thing like this:
.literal
MS>send
To: Operator
cc:
Subject:
Message (ESC to enter Send Level, ctrl-Z to send, ctrl-K to redisplay,
ctrl-B to insert file, ctrl-E to enter editor):
This is a test message.
^Z
Sending to Operator - OK
MS>
.end literal
If, in=stead of typing "OK" after "Sending to Operator", MS
complains about a pro=tec=tion violation, then it is run=ning with=out
the JACCT bit. Check to make sure that you've installed the MS
com=mand in the monitor properly, and that MS appears in the monitor
table PRVTAB.
Once you've suc=cess=fully sent mail to the operator, have the
operator run MS and send you mail back. Now log out and log back in
again. LOGIN should give you the fol=lowing reminder:
.literal
[LGNYHM You have 1 new message; to receive it, type 'MS READ']
.end literal
If you do not get this mes=sage, check to insure that you've
cor=rectly installed the module LGNMS in LOGIN and that the modified
LOGIN is the one you're run=ning to log in.
If the above steps succeed with no problems, you've cor=rectly
installed MS and can announce it to your user community.
.subtitle Installation of DECmail/MS on TOPS-20 systems
.page
.header level 1 Installation of DECmail/MS on TOPS-20 systems
.header level 2 Summary
There are two kinds of DECmail/MS in=stal=lation on
TOPS-20. The simplest in=stal=lation is that for local mail only;
this means mail to other users on the same host. This in=stal=lation
is required. In addition, if you have other DECSYSTEM-20s in a DECNET
net=work and wish to be able to ex=change mes=sages with users on
other hosts, you must install the net=work mail soft=ware.
.header level 2 Local Mail Only
.header level 3 Installation instructions
.break
For local mail (mail to users on the same host) only, you
need to install the fol=lowing files as indicated:
.literal
File on distribution medium Where to install it
--------------------------- -------------------
MS.EXE SYS:
MS.HLP HLP:
MAILEX.EXE SYS:
MS.INIT SYSTEM:
.end literal
You also need to edit SYSTEM:SYSJOB.RUN so that it runs
MAILEX. Place the fol=lowing line in SYSTEM:SYSJOB.RUN:
.literal
RUN SYS:MAILEX
.end literal
If you wish to use MS im=me=di=ately, rather than waiting
until the next system reload, you also must start MAILEX under SYSJOB,
using the _^ESPEAK com=mand (refer to the DECSYSTEM-20 Operator's Guide
for in=for=mation on the _^ESPEAK com=mand).
.literal
Example:
@ENABLE
$^ESPEAK (TO SYSJOB)
[Please type SYSJOB commands - end with ^Z]
RUN SYS:MAILEX
^Z
$
.end literal
.header level 3 Installation Certification Procedure (ICP)
Once you've installed MS, log in and try to send mail to some
other user. Your typescript should look some=thing like this:
.literal
@MS
%No current mail file
MS>send
To: Other-user
cc:
Subject: Test message
Message (ESC to enter Send Level, ctrl-Z to send, ctrl-K to redisplay,
ctrl-B to insert file, ctrl-E to enter editor):
This is a test message.
^Z
Processing mail...
Local mail delivered OK.
MS>
.end literal
If you get the fol=lowing error mes=sage:
.literal
?Could not send to local mailer
.end literal
then neither MAILER nor MAILEX is run=ning. Check the in=stal=lation
instructions for local mail above and be sure that you've installed
either MAILER or MAILEX and that one of them is run=ning.
If you get the fol=lowing mes=sage:
.literal
?MAILER is not running. Messages not sent.
.end literal
then MAILER or MAILEX has crashed. Check to insure that whichever one
you are run=ning is run=ning under OPERATOR, so that it has the
privileges it needs.
Once you've sent mail to some other user, have them log in and
read the mail. Then have them send mail back to you. If this works,
you've suc=cess=fully installed DECmail/MS for local mail on your node
and can announce it to your user community.
.page
.header level 2 DECNET Mail installation
.header level 3 Installation instructions
.break
For a net=work mail in=stal=lation, you first do the
in=stal=lation described above for local mail. In addition to MS,
how=ever, there are some ancillary modules, known as net=work mail (or
netmail) daemons, which do the work of moving mes=sages around the
net=work for you. This sec=tion de=scribes the in=stal=lation of the
netmail daemons, and for DECNET mail, the net=work data=base that the
DECNET mail daemons require.
.header level 4 DECNET mail
.break
.header level 5 Install net=work mail daemons
.break
Install the fol=lowing files as indicated:
.literal
File on distribution medium Where to install it
--------------------------- -------------------
DMAILR.EXE SYS:
NMAIL.EXE SYS:
.end literal
.header level 5 Edit SYSTEM:SYSJOB.RUN to run the daemons
.break
Add the fol=lowing lines to SYSTEM:SYSJOB.RUN:
.literal
RUN SYS:DMAILR
RUN SYS:NMAIL
.end literal
.header level 5 Start net=work mail daemons
.break
If you wish to begin using net=work mail im=me=di=ately
(rather than waiting for the next system reload), you must start these
two tasks by hand (SYSJOB will start them auto=ma=tic=ally on every
system reload). Use the _^ESPEAK com=mand to do this. Refer to the
TOPS-20 Operator's Guide for a description of the _^ESPEAK com=mand.
.literal
Example:
@ENABLE
$^ESPEAK (TO SYSJOB)
[Please type SYSJOB commands - end with ^Z]
RUN SYS:DMAILR
RUN SYS:NMAIL
^Z
$
.end literal
.header level 5 Create SYSTEM:DECNET-HOSTS.TXT
.break
This file con=tains com=mand lines which define the DECNET
en=vi=ronment. It is read by both DMAILR and MS, so it must be
pro=tected such that all users can read it with=out privileges.
It is a text file and can be created with any editor. Each line
defines a host, or a synonym or alternate path to a host. Comments
(started by exclamation point or semicolon) and blank lines, for
readability, are allowed.
.header level 6 Defining A Directly Accessible Host
.break
A host is directly ac=ces=sible if it is in the same Phase III
net=work as your host, or in a Phase II net=work if it is directly
adjacent. To define such a node, just enter its name on a sep=a=rate
line. No punc=tua=tion is required; in par=tic=ular, do NOT terminate
the name with double-colon.
.header level 6 Defining off-network hosts (route-through hosts)
.break
.note
This sec=tion is applicable only to those net=works which run the
"pass-through", or "poor-man's-router" task, as a gate=way between
DECNETs. If you have a simple net=work with=out gate=ways, you may
skip this sec=tion.
.end note
Hosts which are not adjacent to your host, in a Phase II
net=work, or are not on the Phase III net=work in which your host
participates, must be reached using the pass-through protocol
im=ple=mented by the "pass-through", or "poor-man's-router" task
(dis=tri=buted with DECNET, not with DECmail/MS). To define such a
host you must know the routing path used to reach it. The entry for
such a host is:
.literal
<host-name>,<1st-gateway>::<2nd-gateway>:: ... <host-name>::
.end literal
If your gate=way con=fig=uration pro=vides mul=tiple paths to off-net=work
(Phase III) or non=ad=jacent (Phase II) hosts, you may define all the
paths in the file. The mail system will try to use them in the
order in which they appear in the file. If the first path does not
work, the second path is tried, and so forth, until the mail is
delivered or all paths have been tried. For example, consider a
Phase II net=work as follows:
.literal
[HOSTA]--------[HOSTB]---------[HOSTC]-------[HOSTD]
| |
| |
[HOSTE]---------[HOSTF]
.end literal
As you can see, HOSTA has two possible paths to HOSTF and HOSTE. So
in SYSTEM:DECNET-HOSTS.TXT for HOSTA, the fol=lowing entries should
be made:
.literal
HOSTA
HOSTB
HOSTC,HOSTB::HOSTC::
HOSTD,HOSTB::HOSTC::HOSTD::
HOSTE,HOSTB::HOSTE::
HOSTE,HOSTB::HOSTC::HOSTF::HOSTE:: ! alternate path
HOSTF,HOSTB::HOSTE::HOSTF::
HOSTF,HOSTB::HOSTC::HOSTF:: ! alternate path
.end literal
Note that the local host must be de=fined as well. Also, be careful
not to forget the trailing double-colon.
.page
.header level 6 Defining Host Synonyms
.break
Fre=quently you will find it useful to define mnemonic or
humorous synonyms for hosts in your net=work, especially if the
net=work ad=min=is=tra=tors have chosen to assign dry or unpopular names
to the hosts. To define a host synonym, enter the synonym name, an
equals sign (_=), and the real name. Be careful! The real name must
already have been de=fined earlier in the the file. For example:
.literal
HOSTA ! Unimaginative name
ORANGE-PAINTED-PDP10=HOSTA ! More easily remembered name
.end literal
.header level 3 Installation certification procedure (ICP)
In order to perform this pro=ce=dure, you should have
installed MS and the net=work mail soft=ware on two DECSYSTEM-20s
con=nected via DECNET. Before trying to verify your in=stal=lation,
be sure that the DECNET link between the two systems is up and
working.
Log into an account on one system and send mail to an invalid
user=name on the other system; for example, "No-such-user". Next
give the "net-mail" com=mand to force the mail unspooler (DMAILR) to
try to deliver your mail. You should get an error mes=sage from the
other node complaining about the invalid node name.
For example, if you're on NODEA and the other node is NODEB,
your typescript would look some=thing like this:
.literal
@MS
%No current mail file
MS>send
To: No-such-user at NODEB
cc:
Subject: Test message
Message (ESC to enter Send Level, ctrl-Z to send, ctrl-K to redisplay,
ctrl-B to insert file, ctrl-E to enter editor):
This is a test message.
^Z
Netmail queued for transmission.
MS>net-mail
Sending to NODEB, connect OK,
?NMAIL error: Invalid username in "To:" list: NO-SUCH-USER
MS>
.end literal
If you do not get the "connect OK" mes=sage, but in=stead get
some DECNET error mes=sage, check to make sure that the connection to
NODEB is working. If the DECNET error mes=sage is "des=ti=nation
pro=cess does not exist", check to insure that NMAIL is installed and
run=ning on the other node.
Once you've suc=cess=fully executed this part of the net=work
verification, try sending mail to a real user on the other node. Your
typescript should look some=thing like this:
.literal
@MS
%No current mail file
MS>send
To: Smith at NODEB
cc:
Subject: Test message
Message (ESC to enter Send Level, ctrl-Z to send, ctrl-K to redisplay,
ctrl-B to insert file, ctrl-E to enter editor):
This is a test message.
^Z
Netmail queued for transmission.
MS>net-mail
Sending to NODEB, connect OK, sent OK, deleted.
MS>
.end literal
Next check to see if the mail unspooler is run=ning OK.
Proceed as in the previous example, except do NOT give the "net-mail"
com=mand. Wait for the unspooler to deliver the mail. This should
take no longer than 30 minutes. You can check to see if the mail has
been delivered yet by get=ting a di=rec=tory lis=ting of your
logged-in PS: di=rec=tory. If the mail has not yet been sent, you
will see a file whose file=spec is of the form:
.literal
[--DECNET-MAIL--].NODEB.1
.end literal
When this file disappears, the mail has been delivered. Have
the user on the other system to whom you sent the mail log in and run
MS to check to see that he's actually received the mail cor=rectly.
If you encounter problems with this test, check the file
SYSTEM:DMAILR.LOG. This file con=tains a com=plete log of the
unspooler's activity and should point you to the problem.
Once you've suc=cess=fully run these tests, you can be sure
that you've cor=rectly installed DECmail/MS and can now announce it to
your user community.
.header level 2 ARPANET mail installation
.break
DECmail/MS can send and receive mail over the ARPANET as well.
For in=for=mation on in=stal=ling the ARPANET soft=ware, refer to the
TOPS-20AN In=stal=lation Guide. There is nothing special that need be
done for DECmail/MS; if you install the ARPANET soft=ware cor=rectly,
as described in its doc=u=men=tation, DECmail/MS will work with no
further actions required on your part.
.header level 2 XMAILR (Stanford/MIT Internet Mailer)
.break
DECmail/MS sup=ports XMAILR, the Stanford/MIT inter=net=work
mailer. XMAILR is a mail de=livery daemon which can deliver mail to
hosts on a variety of net=works, including DECNET, ARPANET, Chaosnet,
and Dialnet. XMAILR is neither sup=ported nor dis=tri=buted by
Digital Equipment Cor=por=ation, and so we can=not claim that
DECmail/MS will always work with XMAILR. We do make an effort to keep
DECmail/MS up-to-date with respect to XMAILR, how=ever. For more
in=for=mation on XMAILR, con=tact Mark Crispin at Stanford University
(Admin.MRC @ SU-SCORE.ARPANET). As of the writing of this document,
DECmail/MS worked cor=rectly with XMAILR, but did not recognize
pseudo-|mail=box-|names de=fined by the XMAILBOX pro=gram. This
ca=pa=bility will probably be added to future releases of DECmail/MS.
DECmail/MS decides to use XMAILR on a system if and only if:
.list 1,"o"
.list element;The file SYSTEM:HOSTS2.BIN exists and is readable.
.list element;The file SYSTEM:XMAILR.FLAGS exists and is writeable.
.end list
If these two con=di=tions are not met, DECmail/MS attempts to
use sup=ported methods of delivering the mail.
.blank
[End of MSINST.MEM]