Message Exchange Release Notes August, 2011 This file contains the release notes for Message Exchange V6.1. 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: OpenVMS VAX V6.2 or later OpenVMS Alpha V6.2 or later OpenVMS Industry Standard 64 V8.2 or later Software Version: Message Exchange V6.1 Endless Software Solutions Perth, Western Australia ________________________ 03 August 2011 __________ Copyright ©2008 Matthew Madison. __________ Copyright ©2011 Endless Software Solutions. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: o Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. o Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. o Neither the name of the copyright owner nor the names of any other contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Portions of the software were adapted from other open source projects. Refer to the Release Notes for copyright and license information. _______________________________________________________ Contents _______________________________________________________ CHAPTER 1 INSTALLATION NOTES 1-1 _________________________________________________ 1.1 MX MUST BE SHUT DOWN 1-1 _______________________________________________________ CHAPTER 2 UPGRADE INFORMATION 2-1 _________________________________________________ 2.1 UPGRADE RESTRICTION 2-1 _______________________________________________________ CHAPTER 3 NEW FEATURES AND CHANGES IN MV V6.1 3-1 _________________________________________________ 3.1 VAX SYSTEM SUPPORT RE-INSTATED 3-1 _________________________________________________ 3.2 NEW ANTI-SPAM HEURISTICS 3-1 _______________________________________________________ CHAPTER 4 NEW FEATURES AND CHANGES IN MX V6.0 4-1 _________________________________________________ 4.1 OPEN SOURCE DISTRIBUTION 4-1 _________________________________________________ 4.2 VAX SYSTEM SUPPORT DISCONTINUED 4-1 iii Contents _______________________________________________________ CHAPTER 5 NEW FEATURES AND CHANGES FROM V5.4 AND EARLIER RELEASES 5-1 _________________________________________________ 5.1 SUPPORT FOR OPENVMS INDUSTRY STANDARD 64 SYSTEMS 5-1 _________________________________________________ 5.2 MESSAGE QUEUE PERFORMANCE AND RELIABILITY ENHANCEMENTS 5-1 _________________________________________________ 5.3 SMTP SERVER: CLIENT CHECK ENHANCEMENT 5-1 _________________________________________________ 5.4 SMTP SERVER: AUTHENTICATION LOGGING 5-2 _________________________________________________ 5.5 SMTP SERVER: REQUIRING AUTHENTICATION 5-2 _________________________________________________ 5.6 SMTP SERVER: JUNK MAIL RULE ID HEADER 5-3 _________________________________________________ 5.7 SMTP SERVER: ALTERNATE SERVER PROCESSES 5-3 _________________________________________________ 5.8 MX V5.3 ECO 12 UPDATES 5-3 _________________________________________________ 5.9 OTHER FIXES AND ENHANCEMENTS 5-4 iv Contents _______________________________________________________ CHAPTER 6 KNOWN BUGS AND RESTRICTIONS 6-1 _________________________________________________ 6.1 X.25-SMTP BUG 6-1 _________________________________________________ 6.2 MXALIAS AND THE MX% "@" PATCH FOR VMS MAIL 6-1 _________________________________________________ 6.3 POSSIBLE FORWARDING PROBLEMS 6-1 _________________________________________________ 6.4 REMOTE FORWARDING PROBLEMS 6-2 _________________________________________________ 6.5 BYPASS NEEDED FOR UUCP DELIVERY 6-2 _______________________________________________________ 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 V6.1 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-1 _______________________________________________________ 2 Upgrade Information This chapter contains information of interest to sites upgrading from previous versions of MX. __________________________________________________________________ 2.1 Upgrade Restriction MX V6.1 only supports upgrading MX installations of version V6.0 and later. To upgrade from pre-V6.0 releases it is recommended that the following MCP commands are used to generate a human readable script. $ MCP SHOW ALL/COMMAND/OUTPUT=ddcu:[dir]file.MCP This script can then can be edited appropriately and loaded into the new MX installation by using the @ input-indirection function. 2-1 _______________________________________________________ 3 New Features and Changes in MV V6.1 This chapter notes the changes that were made in MX V6.1. __________________________________________________________________ 3.1 VAX System Support Re-instated Support for systems running OpenVMS VAX has been resinstated in the V6.1 release of Message Exchange. MX is now available on all three OpenVMS supported architectures. __________________________________________________________________ 3.2 New Anti-SPAM Heuristics There are now two new anti-SPAM heuristic filters. These are FROM_BAD_LOCAL_USER and FROM_USER_MSGID_ HOST. See the REJMAN documentation for further information on how to use the heuristics and what they attempt to catch. 3-1 _______________________________________________________ 4 New Features and Changes in MX V6.0 This chapter notes the changes that were made in MX V6.0. __________________________________________________________________ 4.1 Open Source Distribution Starting with V6.0, MX is now distributed as open source. __________________________________________________________________ 4.2 VAX System Support Discontinued MX V6.1 supports only Alpha and IA64 systems. You may be able to build binaries for VAX from the source code, but some modifications may be required to get them to run. 4-1 _______________________________________________________ 5 New Features and Changes from V5.4 and Earlier Releases This chapter notes the changes that were introduced in MX V5.4 and prior releases. __________________________________________________________________ 5.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. __________________________________________________________________ 5.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. __________________________________________________________________ 5.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. 5-1 New Features and Changes from V5.4 and Earlier Releases 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. __________________________________________________________________ 5.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. __________________________________________________________________ 5.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. 5-2 New Features and Changes from V5.4 and Earlier Releases __________________________________________________________________ 5.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. __________________________________________________________________ 5.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. __________________________________________________________________ 5.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] 5-3 New Features and Changes from V5.4 and Earlier Releases o Fix for DNSMTP_SERVER BADPARAM failure [ECO 12] __________________________________________________________________ 5.9 Other Fixes and Enhancements MX V6.1 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. 5-4 _______________________________________________________ 6 Known Bugs and Restrictions __________________________________________________________________ 6.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. __________________________________________________________________ 6.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%. __________________________________________________________________ 6.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. 6-1 Known Bugs and Restrictions __________________________________________________________________ 6.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. __________________________________________________________________ 6.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. 6-2 _______________________________________________________ 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 such, and must not be misrepresented as being the original software. Since few users ever read sources, credits must appear in the documentation. 4. This notice may not be removed or altered. A-1 Other Copyright Notices =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= /*- * Copyright (c) 1994 * The Regents of the University of California. All rights reserved. * * Redistribution and use in source and binary forms, with or without * modification, are permitted provided that the following conditions * are met: * 1. Redistributions of source code must retain the above copyright * notice, this list of conditions and the following disclaimer. * 2. Redistributions in binary form must reproduce the above copyright * notice, this list of conditions and the following disclaimer in the * documentation and/or other materials provided with the distribution. * 3. All advertising materials mentioning features or use of this software * must display the following acknowledgement: * This product includes software developed by the University of * California, Berkeley and its contributors. * 4. Neither the name of the University nor the names of its contributors * may be used to endorse or promote products derived from this software * without specific prior written permission. * * THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE * ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF * SUCH DAMAGE. * * @(#)COPYRIGHT 8.1 (Berkeley) 3/16/94 */ A-2