Patch-ID# 100480-01
Keywords: mhs patch
Synopsis: SunNet MHS 7.0: mhs bug fixes
Date: 21/Jan/92

SunOS release: SunOS 4.1, SunOS 4.1.1

Unbundled Product: SunNet MHS

Unbundled Release: 7.0

Topic: 

BugId's fixed with this patch: 1070524, 1060020, 1060558, 1055022

Architectures for which this patch is available: sun3, sun4

Patches which may conflict with this patch: 

Obsoleted by: 

Files included with this patch: 

Problem Description: 

    Bug Id: 1070524
        Use of the 822 group construct caused mail to be dropped.
        822 groups are now translated as according to RFC 987.
        Also, bad addresses are now put in the RFC-822-Headers body 
        part.

    Bug Id: 1060020
        Synopsis: 4.1 subsidiary sendmail fails to route when 
        x400-gate is defined in NIS

    Bug Id: 1060558
        Synopsis:  Not translating 822 username "_" into 
        PersonalName form
     
    Bug Id: 1055022 
        Synopsis: Wrong activity identifier prevents connection
        with Atlas

    Also fixed is a problem where SunNet MHS RTS sent less than the
    negotiated checkpoint size.  While this is legal, it causes 
    problems with some other implementations.

NOTE:

    This patch includes Sun 3 & Sun 4 executables.
    Please uses sun3 for sunx, sun4 for sun4c machines.

    In the typical configuration, the MHS software is installed on one
    or more machines.  These machines are neither NFS servers nor
    clients as far as the MHS software is concerned.  This is called the
    standalone configuration.  This patch must be applied to each
    standalone machine.  Do steps (1) - (5).

    If the configuration is such that some machines act as NFS servers
    for the MHS software to other clients, do steps (1) and (5) on the
    servers and clients and do steps (2) - (4) on just the servers.


INSTALLATION:

To install this patch, follow the following procedure:

(1) Stop the MHS system if it is running using "mhsc -shutdown"
    (see mhsc(8)).  

(2) Read in the patch:

    (a) become root:
    
            su

    (b) Set the "archs" environment variable to those architectures
        that this machine supports.  If the machine is a standalone
        machine, use the following command:
        
            set archs = `arch` 

        This same command would be used in the case that this machine is
        a homogeneous server (where all the clients are machines of the
        same type).

        If this machine is a server for both sun3's and sun4's (a
        heterogeneous server), use the following:

            set archs = "sun3 sun4"

        Typically the architectures supported by a machine can be
        determined by finding what subsitutes for "*" in the command:

            ls /export/exec/*/sunlink/mhs

        (Note: the "set" commands above assume the csh. If you use
        sh, use a command like "archs=`arch`".)

    (c) If the patch has been distributed via tape, set the "tarfile"
        environment variable to the device name for your tape drive.
        Typically it will be

            set tarfile = /dev/nrst8

        but it is possible that "st0" would be replaced by "st0", "mt0"
        or "ar0".  Note that the "n" is needed to specify "no rewind".
        Now, execute the following to position the tape:

            mt -f $tarfile rew
            mt -f $tarfile fsf 1

    (d) If the patch has been distributed via e-mail, save the message
        in a file and set the "mailfile" environment variable to the
        full path of the file:

            set mailfile = <path-of-mail-file-saved-above>

        and then execute in some temporary directory (such as /tmp)

            uudecode $mailfile
            uncompress mhs.patch.tar.Z
            set tarfile = `pwd`/mhs.patch.tar


    (e) Now execute

            cd /export/exec
            tar xfvp $tarfile $archs

        which should yield directories /export/exec/*/sunlink/mhs.patch.
        On this machine, the software will end up in
        /usr/sunlink/mhs.patch because /export/exec/`arch` is a symbolic
        link to /usr.

(3) Optionally, save the old software.  The script to be run in step
    (4) will give you the option of saving copies of the files to be
    updated.  However, if you want to keep the whole distribution
    together and you don't have the FCS tape, copy the software to
    tape or some other safe place.  To copy to tape, put a scratch
    tape in the tape drive and execute

        cd /export/exec
        tar cfv /dev/rst8 sun*/sunlink/mhs

(4) Install the patch:

        cd /usr/sunlink/mhs.patch
        install.mhs.patch

    The install script will ask you to confirm its actions by asking a
    series of questions.  Unless you have an exceptional configuration,
    you should select the default (provided in brackets ("[]")) by
    typing RETURN.  If you have a safe copy of the whole distribution,
    you can answer "no" to the "Do you want to keep old copies of these
    files?"  question.

(5) Reconfigure and start the gateway:

        su mail
        cd
        configure
        rungateway &

The new software should be up and running.


Estimated Size of this patch: 1823 KB