Message Exchange Release Notes          March, 2005          This file contains the release notes for Message          Exchange V5.4. It describes any features,          restrictions, changes, or additions made to MX in this          release, and includes information that is not provided          elsewhere in the MX manual set.          Revision/Update Information:  This is a revised manual.          Operating System and Version: VMS V5.5 or later                                        OpenVMS Alpha V6.2 or                                        later                                        OpenVMS Industry Standard                                        64 V8.2 or later          Software Version:             Message Exchange V5.4          MadGoat Software          Santa Cruz, California           ________________________          13 March 2005          The information in this document is subject to change          without notice and should not be construed as a          commitment by MadGoat Software. MadGoat Software          assumes no responsibility for any errors that may          appear in this document.          No part of this publication may be reproduced,          transmitted, transcribed, stored in a retrieval          system, or translated into any language or computer          language, in any form or by any means electronic,          mechanical, magnetic, optical, chemical, or otherwise          without the prior written permission of MadGoat          Software.          Use of this software and documentation is subject          to the terms and conditions set forth in the License          Agreement.          The Licensed Materials are provided with RESTRICTED          RIGHTS. Use, duplication, or disclosure by the          Government is subject to restrictions as set forth          in subparagraph (c)(1)(ii) of the Rights in Technical          Data and Computer Software clause at DFARS §252.227-          7013 or subparagraphs (c)(1) and (2) of the Commercial          Computer Software-Restricted Rights at 48 CFR §52.227-          19, as applicable.          MadGoat, Message Exchange, and MX are trademarks of          MadGoat Software.          __________          Copyright ©2005 MadGoat Software. ALL RIGHTS RESERVED.          Portions of the software were adapted from the NetBSD          Project. Refer to the Release Notes for copyright          information.           _______________________________________________________          Contents          _______________________________________________________          CHAPTER 1  INSTALLATION NOTES                       1-1                _________________________________________________                1.1   MX MUST BE SHUT DOWN                    1-1                _________________________________________________                1.2   NETLIB                                  1-1          _______________________________________________________          CHAPTER 2  UPGRADE INFORMATION                      2-1                _________________________________________________                2.1   JNET SUPPORT DISCONTINUED               2-1                _________________________________________________                2.2   UPGRADE RESTRICTION                     2-1                _________________________________________________                2.3   CONTRIBUTED FILES NO LONGER                      DISTRIBUTED                             2-1                _________________________________________________                2.4   DOCUMENTATION IN BOOKREADER FORMAT                      DISCONTINUED                            2-1                _________________________________________________                2.5   VAX SYSTEM SUPPORT TO BE                      DISCONTINUED                            2-2                                                              iii           Contents          _______________________________________________________          CHAPTER 3  NEW FEATURES AND CHANGES IN MX V5.4      3-1                _________________________________________________                3.1   SUPPORT FOR OPENVMS INDUSTRY                      STANDARD 64 SYSTEMS                     3-1                _________________________________________________                3.2   MESSAGE QUEUE PERFORMANCE AND                      RELIABILITY ENHANCEMENTS                3-1                _________________________________________________                3.3   SMTP SERVER: CLIENT CHECK                      ENHANCEMENT                             3-1                _________________________________________________                3.4   SMTP SERVER: AUTHENTICATION LOGGING     3-2                _________________________________________________                3.5   SMTP SERVER: REQUIRING                      AUTHENTICATION                          3-2                _________________________________________________                3.6   SMTP SERVER: JUNK MAIL RULE ID                      HEADER                                  3-3                _________________________________________________                3.7   SMTP SERVER: ALTERNATE SERVER                      PROCESSES                               3-3                _________________________________________________                3.8   MX V5.3 ECO 12 UPDATES                  3-3                _________________________________________________                3.9   OTHER FIXES AND ENHANCEMENTS            3-4          iv                                                          Contents          _______________________________________________________          CHAPTER 4  KNOWN BUGS AND RESTRICTIONS              4-1                _________________________________________________                4.1   X.25-SMTP BUG                           4-1                _________________________________________________                4.2   MXALIAS AND THE MX% "@" PATCH FOR                      VMS MAIL                                4-1                _________________________________________________                4.3   POSSIBLE FORWARDING PROBLEMS            4-1                _________________________________________________                4.4   REMOTE FORWARDING PROBLEMS              4-2                _________________________________________________                4.5   BYPASS NEEDED FOR UUCP DELIVERY         4-2          _______________________________________________________          CHAPTER 5  PROBLEM REPORTS                          5-1          _______________________________________________________          APPENDIX A  OTHER COPYRIGHT NOTICES                 A-1                                                                v           _______________________________________________________   1      Installation Notes          This chapter contains items of interest pertaining to          the installation of MX.          __________________________________________________________________   1.1    MX Must Be Shut Down          If you are upgrading to MX V5.4 from a previous          version, all MX processes on the system or cluster          must be shut down using the MCP SHUTDOWN command.          Also, you should define the MX_SHUTDOWN logical (MX          V4.0+) or deassign the MX_MAILSHR system logical to          prevent users from sending mail via MX during the          installation.          __________________________________________________________________   1.2    NETLIB          MadGoat Software's NETLIB V2.4 is included with MX          V5.4. Note that this version of NETLIB supports only          Alpha and IA64 systems; VAX users must install NETLIB          V2.3D (the last version of NETLIB to support VAX          systems) prior to installing MX. Release notes for          NETLIB are provided in SYS$HELP:NETLIB024.RELEASE_          NOTES when NETLIB support is installed with MX.          Please note that the NETLIB package provided with          MX includes run-time support only. If you use NETLIB          for software development, you should obtain the full          NETLIB kit from MadGoat and install it separately.          If you already have NETLIB V2.3D or later installed          on your system, you do not have to install the NETLIB          run-time kit that comes with MX.                                                              1-1           _______________________________________________________   2      Upgrade Information          This chapter contains information of interest to sites          upgrading from previous versions of MX.          __________________________________________________________________   2.1    Jnet Support Discontinued          The last version of MX to support Jnet as a message          transport was V5.1A. Do not upgrade to MX V5.4 if you          still need support for Jnet.          __________________________________________________________________   2.2    Upgrade Restriction          MX V5.4 only supports upgrading MX installations of          version V4.0 and later. If you are currently running a          version of MX prior to V4.0, you must either install          MX V5.4 in a new location, or upgrade to MX V4.x or          V5.0 prior to installing MX V5.4 as an upgrade.          __________________________________________________________________   2.3    Contributed Files No Longer Distributed          User-contributed files are no longer distributed with          the MX kit. They are still available on the Internet          from MadGoat's web site. If you have installed the          user-contributed files from a previous version of MX,          those files are not removed during the upgrade to MX          V5.4.          __________________________________________________________________   2.4    Documentation in Bookreader Format Discontinued          The MX V5.4 documentation is no longer distributed in          Bookreader format. PostScript, ASCII text, and HTML          formats are still provided.                                                              2-1           Upgrade Information          __________________________________________________________________   2.5    VAX System Support to be Discontinued          MX V5.4 supports VAX, Alpha, and IA64 systems. Future          versions of MX will no longer include support for VAX          systems. In addition, future versions are likely to          drop support for versions of OpenVMS Alpha older than          V7.3-2.          2-2           _______________________________________________________   3      New Features and Changes in MX V5.4          )          This chapter notes the changes that were made in MX          V5.4.          __________________________________________________________________   3.1    Support for OpenVMS Industry Standard 64 Systems          This version of MX support OpenVMS Industry Standard          64 systems, as well as Alpha and VAX systems.          __________________________________________________________________   3.2    Message Queue Performance and Reliability Enhancements          The MX message queuing subsystem, FLQ, has been          modified to eliminate the linked-list structure          that was used in previous versions of MX. This          simplification improves performance by reducing the          number of reads/writes to the queue control file          and the number of locks that must be acquired for          each queue update. The changes should also improve          reliability of the queue and reduce the likelihood of          queue control file corruptions.          __________________________________________________________________   3.3    SMTP Server: Client Check Enhancement          The SMTP server access-check callout interface has          been extended to add a check for the domain name          presented by the client in the HELO or EHLO command at          the start of an SMTP session. This check can be used          to reject sessions from clients that do not present          a valid domain name on this command, or to cause all          messages sent by such clients to be rejected as junk          mail.                                                              3-1           New Features and Changes in MX V5.4          A kit that implements this additional callout          is provided in the Examples subset, at MX_          ROOT:[EXAMPLES]ACCESS_CHECK.ZIP. The README file          provided with that kit describes how to install and          configure it to either refuse or flag messages from          hosts that falsify their identities.          __________________________________________________________________   3.4    SMTP Server: Authentication Logging          When using VMS SYSUAF authentication for the SMTP          server, the server now generates an ID that is          included in the Received: header of the incoming          message and is also logged to the SMTP server's log          file, when authentication succeeds. By cross-matching          the ID with the log files, you can trace a message          to the VMS username used to authenticate the SMTP          transaction.          __________________________________________________________________   3.5    SMTP Server: Requiring Authentication          The SMTP server has been changed to check a new          logical name, MX_SMTP_SERVER_AUTHENTICATION_REQUIRED.          If that logical name translates to the string OUTSIDE,          the server will require all "outside" clients to          authenticate; if it translates to any other value, the          server will require all clients (even "inside" ones)          to authenticate. When authentication is required, the          SMTP MAIL command will be refused with an error until          the client has successfully authenticated.          You could use this feature to establish a separate          SMTP server for servicing your own client hosts (such          as PCs running POP or IMAP clients), either running on          a separate system or on a non-default port. You should          NOT enable this feature for the SMTP server that you          configure for accepting incoming messages from the          Internet or other non-authenticating hosts.          3-2                               New Features and Changes in MX V5.4          __________________________________________________________________   3.6    SMTP Server: Junk Mail Rule ID Header          The SMTP server now adds a new header, X-Junk-Mail-          Rule-ID, to incoming messages that match a REJMAN          header rule. The contents of the header is the numeric          ID of the matching rule.          __________________________________________________________________   3.7    SMTP Server: Alternate Server Processes          The MX startup procedure has been enhanced to provide          for the startup of alternate SMTP server processes          that include customizations for the logical names that          control the server's behavior, such as the IP address,          port number, and required authentication. See the file          MX_EXE:SMTP_SERVER.COM for more information.          __________________________________________________________________   3.8    MX V5.3 ECO 12 Updates          This version of MX includes all of the fixes provided          in the ECO kits issued for MX V5.3 through ECO 12.          o  MLF subscription confirmation ACCVIO fix [ECO 1]          o  Security fix for MX_DECODE, MX_LOCAL [ECO 2]          o  Local forwarder relay fix [ECO 3]          o  SET LOCAL/DISABLE_EXQUOTA and SMTP rejection             database update fixes [ECO 4]          o  MX_SITE_IN From: header generation fix [ECO 5]          o  VMS MAIL From: header generation fix [ECO 6]          o  MX_SMTP_SERVER_ADDRESS logical name support [ECO 7]          o  MX_INVALID_DOMAIN_ADDRESSES logical name support             [ECO 8]          o  RBL lookup fixes [ECO 9]          o  SMTP server queue entry handling fix [ECO 10]          o  Authentication debug enhancements [ECO 11]                                                              3-3           New Features and Changes in MX V5.4          o  Fix for DNSMTP_SERVER BADPARAM failure [ECO 12]          __________________________________________________________________   3.9    Other Fixes and Enhancements          MX V5.4 includes the following minor fixes and          enhancements:          o  In prior versions of MX, if you ran multiple             instances of the MX FLQ Manager process, only the             active process would show up in the MCP STATUS             display and respond to the SHUTDOWN and RESET             commands. This problem has been fixed.          o  The /WAIT qualifier on the MCP SHUTDOWN command             could wait for longer than necessary when shutting             down a subset of the agents running in an entire             cluster. This problem has been fixed.          3-4           _______________________________________________________   4      Known Bugs and Restrictions          __________________________________________________________________   4.1    X.25-SMTP Bug          Messages received via X25_SMTP that contain very          long lines may be rejected by the X.25 SMTP server.          Currently, the only fix is to wrap the long line          before sending the message.          __________________________________________________________________   4.2    MXALIAS and the MX% "@" Patch for VMS Mail          If you have installed the VMS Mail patch that lets          users leave off the MX% for addresses (found in the          [.CONTRIB] directory), MXALIAS addresses must still be          prefixed by MX% to be recognized. MX_MAILSHR will try          to lookup an ALIAS if the MX address does not include          an "@" in the address received from VMS Mail. With          the VMS Mail "@" patch installed, MX aliases are not          passed to MX unless they are first prefixed by MX%.          __________________________________________________________________   4.3    Possible Forwarding Problems          If, prior to installation of MX, you were running a          different E-mail package on your system, and users          made use of the SET FORWARD command in VMS MAIL          to forward mail through that other package, those          forwarding addresses may no longer work after MX is          installed.          The system manager should review the forwarding          addresses used on the system and modify them as          needed to use the MX% prefix once MX is installed.          The command SHOW FORWARD/USER=* and SET FORWARD/USER          commands in VMS MAIL can be used to accomplish this.                                                              4-1           Known Bugs and Restrictions          __________________________________________________________________   4.4    Remote Forwarding Problems          Although MX will automatically detect forwarding          on the local system, it cannot do so for messages          delivered across DECnet. If a remote DECnet user set          his or her forwarding across DECnet back into MX, as,          for example, with the following command,                           MAIL> SET FORWARD REMOTE::MX%"""user@host"""          and if MX delivers a message to that user via DECnet,          the doubled DECnet reference will result in two sets          of RFC 822 headers will appear in the message: one set          for the original message and one set for the forwarded          message.          There is no workaround or fix for this problem.          __________________________________________________________________   4.5    BYPASS Needed for UUCP Delivery          If you intend to use MX with DECUS UUCP, and you elect          to use a separate mailer account, the mailer account          may need to have BYPASS privilege.          4-2           _______________________________________________________   5      Problem Reports          Please submit problem reports to the mx-bugs alias at          madgoat.com.                                                              5-1           _______________________________________________________   A      Other Copyright Notices          The regular expression routines were adapted from          NetBSD:          $NetBSD: COPYRIGHT,v 1.4 1995/02/27 13:28:12 cgd Exp $          Copyright 1992, 1993, 1994 Henry Spencer.  All rights reserved.          This software is not subject to any license of the American Telephone          and Telegraph Company or of the Regents of the University of California.          Permission is granted to anyone to use this software for any purpose on          any computer system, and to alter it and redistribute it, subject          to the following restrictions:          1. The author is not responsible for the consequences of use of this             software, no matter how awful, even if they arise from flaws in it.          2. The origin of this software must not be misrepresented, either by             explicit claim or by omission.  Since few users ever read sources,             credits must appear in the documentation.          3. Altered versions must be plainly marked as