From:	AITGW::"madison@vms.ecs.rpi.edu" "Matt Madison"  3-JAN-1992 15:16:02.29
To:	mx-list@vms.ecs.rpi.edu
CC:	
Subj:	MX V3.0 revision level A now available

Received: by AITGW.DECnet (utk-mail11 v1.5) ; Fri, 3 Jan 92 15:13:02 EST
Received: from vms.ecs.rpi.edu by aitgw.ge.com (5.65/GE Gateway 1.4)
	id AA00892; Fri, 3 Jan 92 15:12:57 -0500
Errors-To: list-mgr@vms.ecs.rpi.edu
X-Listname: Message Exchange discussion list <MX-List@vms.ecs.rpi.edu>
Received: by vms.ecs.rpi.edu (MX V3.0A) id 7715; Fri, 03 Jan 1992 14:36:43 EST
Sender: <madison@vms.ecs.rpi.edu>
Date: Fri, 03 Jan 1992 14:36:39 EST
From: Matt Madison <madison@vms.ecs.rpi.edu>
Reply-To: Matt Madison <madison@vms.ecs.rpi.edu>
To: mx-list@vms.ecs.rpi.edu
Message-Id: <00954162.4E0C09E0.7715@vms.ecs.rpi.edu>
Subject: MX V3.0 revision level A now available
 
After receiving a handful of reports of minor bugs and one about a somewhat
more major bug in MX V3.0, I have produced a maintenance release, called
revision A.  Everyone who obtains the MX030 kit by anonymous FTP will be
getting the updated version.  If you have MX V3.0 currently installed and
would like to upgrade painlessly to V3.0A, you should get the files
01README.REVA_UPGRADE and MX_REVA_UPGRADE030.A_Z, which is the upgrade
kit for existing V3.0 users.
 
The MX030 kit on FILESERV will remain the older version for the time
being; request package MX_REVA_UPGRADE030 for the upgrade kit.
 
The bugs fixed in V3.0A are the ones that have been reported in the
last month:
 
          1. The /DEFAULT_ROUTER qualifier to the MCP SET SMTP
             command was not being recognized, due to a command
             table error.
 
          2. The MCP MODIFY PATH command could not be used to
             update a route specification for a path.
 
          3. Some SMTP 5xx general-failure error codes were not
             causing a message to be returned to sender, but
             instead were getting re-tried. This affected both
             SMTP-over-TCP/IP and SMTP-over-DECnet outbound
             messages.
 
          4. The DOMAIN NAMES support added in V3.0 assumed that
             the mailer specified in DOMAIN NAMES was identical
             to the mailer in the XMAILER NAMES file for the
             gateway node, causing some gateway problems.
 
          5. The MX_JNET process was not correctly handling an
             accounting file reset.
 
          6. The LINK commands in the installation kit were
             being affected by LNK$LIBRARY logical names defined
             on some systems, causing some of the MX executables
             (noticeably, MX_MAILSHRP) to be linked incorrectly.
             All LINK commands in the installation kit have had
             the /NOUSERLIBRARY qualifier added to eliminate
             this problem.
 
          7. The MCP help file incorrectly stated that the
             /REPLY_TO qualifier on the MCP DEFINE LIST command
             was not yet supported. The documentation for DEFINE
             LIST in the Management Guide is also incorrect;
             this will be fixed in a future documentation
             release.
 
Number 4 on the list is a fairly important fix if you are trying to use
the DOMAIN NAMES support in MX.  The rest of the stuff is pretty minor.
 
-Matt
--
Matthew Madison, Systems Programmer  | Internet: madison@vms.ecs.rpi.edu
Engineering Computing Services       | BITNET:   MADISON@RPIECSVX
Rensselaer Polytechnic Institute     |
Troy, New York 12180-3590 USA        |