Trailing-Edge - PDP-10 Archives - T10_DECMAIL_MS_V11_FT1_860414 - 10,7/mail/doc/ms.bwr
There are 5 other files named ms.bwr in the archive. Click here to see a list.

                        TOPS-10 DECmail/MS V11

                              BEWARE File

                               02 Apr 86
   TOPS-10 DECmail/MS V11 BEWARE File -- 02 Apr 86            Page 1


   At this time, we are aware of a few known problems which  may  or
   may  not  impact  your use of MS/MX, depending on your use of the
   product.  These problems are being addressed.

         o  MX creates a log file in the UPS:  directory.  This  log
            file is known to be slightly inaccurate and too verbose.
            (File size is quoted in "Pages" when  it  should  be  in
            "blocks", etc.)

         o  POSTMASTER messages sent to the user from MX may be  too
            terse for a naive user.

         o  MX has not been tested on systems which have no  network

         o  MS/MX V11 has been set up for a system message facility.
            However, there are currently no hooks in the monitor for
            this.  In other words SYSTEM-MAIL can be sent and stored
            in  a  central  location.   However,  the is no means to
            insure that  each  user  gets  notified  of  new  system
            messages.   If this kind of feature is necessary you may
            continue to use SYS:NOTICE.TXT.

         o  MX currently requires  the  file  UPS:LCHOST.TXT.   This
            file should contain the name of node (machine) it is on.

         o  MS does not handle more than 511 messages.  Although  MX
            is  quite  happy  to put more than that many in one mail
            file.  This should be fixed soon.


   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  info  about
            obtaining dumps of MX.

   TOPS-10 DECmail/MS V11 BEWARE File -- 02 Apr 86            Page 2


   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  spec.   RFC822)).  Communication to VMS systems use the
   MAIL-11 protocol.

   3.1  NETMAI

   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 recieving mail
   from MX until they upgrade to MX themselves.  If you see  any  of
   these problems let us know.


         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   inconvient   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 users MAIL.TXT  file  will  be  on  the  first
            structure  in  the  users  default search list with disk
            space available for the user.