There are no other files named decmai.bwr in the archive.
TOPS-10 DECmail/MS V11
24 Jul 86
COPYRIGHT (c) DIGITAL EQUIPMENT CORPORATION 1986. ALL RIGHTS RESERVED.
THIS SOFTWARE IS FURNISHED UNDER A LICENSE AND MAY BE USED AND COPIED
ONLY IN ACCORDANCE WITH THE TERMS OF SUCH LICENSE AND WITH THE
INCLUSION OF THE ABOVE COPYRIGHT NOTICE. THIS SOFTWARE OR ANY OTHER
COPIES THEREOF MAY NOT BE PROVIDED OR OTHERWISE MADE AVAILABLE TO ANY
OTHER PERSON. NO TITLE TO AND OWNERSHIP OF THE SOFTWARE IS HEREBY
THE INFORMATION IN THIS SOFTWARE IS SUBJECT TO CHANGE WITHOUT NOTICE
AND SHOULD NOT BE CONSTRUED AS A COMMITMENT BY DIGITAL EQUIPMENT
DIGITAL ASSUMES NO RESPONSIBILITY FOR THE USE OR RELIABILITY OF ITS
SOFTWARE ON EQUIPMENT WHICH IS NOT SUPPLIED BY DIGITAL.
TOPS-10 DECmail/MS V11 BEWARE File -- 24 Jul 86 Page 1
1.0 KNOWN PROBLEMS
At this time, we are aware of a few known problems which we have
not yet solved prior to shipping the DECmail/MS product.
Depending on your use of the product, these problems may or may
not impact your use of MS/MX. Unless otherwise noted, SPRs need
not be sent in on these problems as we have a thorough
understanding of these problems and will be addressing them in
updates of DECmail/MS which will be distributed on Autopatch
o Sending mail to an alias more complex than a simple
network address does not work.
o Using the ESCAPE key to complete user names in MS does
not always work properly if the username contains a
o Sending mail to a username containing a space does not
work from a VAXmail node.
o MS does not handle more than 511 messages. Although MX
is quite happy to put more than that many in one mail
o If MS cannot tell MX about mail to be sent, it will warn
the user and suggest that he does a SAVE DRAFT. This is
not an option for a NOVICE user.
o At this time the edit feature of MS only works with
DTECO and TECO. The problem is that there has been no
standard that other editors have recognized. We are
looking into solutions for this which may include edits
to some editors.
o Because MS uses GLXLIB any reference to a file-spec in
the form [ppn]file.ext will probably fail giving an
incorrect error message. However, file.ext[ppn] should
always work fine.
o If you are using DECNET, MX should be started up toward
the end of your system initialization. This is so the
DECNET node names will have a chance to be defined.
(This is usually done with either NCP commands or with
the unsupported program NODNAM.)
TOPS-10 DECmail/MS V11 BEWARE File -- 24 Jul 86 Page 2
2.0 OBTAINING A CRASH DUMPS OF MS/MX
If you experience problems with MS or MX crashing, crash dumps
can be obtained, which, when sent to us, will assist in
determining the problem.
o When MS reports a stopcode it returns the user to
monitor level. At this point the crash may be SAVEd.
o Please read the installation doc file for information
about obtaining dumps of MX.
TOPS-10 DECmail/MS V11 BEWARE File -- 24 Jul 86 Page 3
3.0 INTERACTION WITH OTHER MAIL SYSTEMS
MS/MX will provide message services between TOPS-10, TOPS-20, and
VMS via DECnet links. Communication between TOPS-10/20 systems
are accomplished using SMTP (Simple Mail Transfer Protocol
(Arpanet specification RFC822)). Communication to VMS systems
use the MAIL-11 protocol.
MS/MX version 11 completely replaces any current version of MS
and NETMAI (an old unsupported DECNET mailer). MS-10 will only
send mail via MX. If you will have any sites running NETMAI you
should know that these sites may have problems receiving mail
from MX until they upgrade to MX themselves. If you see any of
these problems let us know.
4.0 NOTES AND DIFFERENCES
o If you do not plan on running a DECnet monitor then be
sure to read DECMAIL.DOC for the installation
o MS/MX V11 were written for TOPS10 version 7.03 with
GALAXY 5.1 including ACTDAE. Currently both are
required. ACTDAE is essential.
o Previous versions of MS relied on a file which included
all mail users and the disk structure for their mail
file. This was inconvenient because the system
administrator had to maintain both the user database and
this file, SYS:USERS.TXT. MS/MX V11 relies on the
accounting system for information concerning addresses.
Therefore SYS:USERS.TXT no longer needs to exist or be
o Previous versions of MS wrote local mail directly. With
version 11 MX is the only product to deliver mail. When
MX delivers mail to a local user it sets its own search
list to the default search list of that user. So, by
default a user's MAIL.TXT file will be on the first
structure in the user's default search list with disk
space available for the user.
TOPS-10 DECmail/MS V11 BEWARE File -- 24 Jul 86 Page 4
o MS/MX V11 has been set up for a system message facility.
SYSTEM-MAIL may be sent to and stored in a central
location. Note however, that there is no means to
insure that each user gets notified of new SYSTEM-MAIL.
Therefore, this is not meant to replace SYS:NOTICE.TXT.
o The DNHOST.TXT created for MS/MX will probably differ
from any created for other programs (i.e. NFT, NRT).
Therefore, you should not copy another DNHOST.TXT into
the UPS: area. For more information concerning
DNHOST.TXT see DECMAI.DOC.
5.0 UNSUPPORTED COMMANDS
MS contains a few commands which are unsupported and invisible to
the user. These commands have been included only for command
file compatibility with older versions of MS. Use of these
commands is not advised as the results can be indeterminate.
The commands are: ANSWER, BBOARD, ECHO, EMACS, PREVIOUS,
REDISTRIBUTE, SSEND, SUMMARIZE, ZSEND