Hewlett-Packard Software Product Description ___________________________________________________________________ Product Name: HP MAILbus 400 Message Transfer Agent SPD 54.67.06 for OpenVMS Alpha, Version 3.2 PRODUCT DESCRIPTION MAILbus 400[TM] Message Transfer Agent (MTA) for OpenVMS[TM] Alpha is a layered software product that resides on an OpenVMS Alpha system. MAILbus 400 MTA provides electronic messaging services in an open net- work environment. These services are used by messaging applications, such as user agents and gateways. MAILbus 400 MTA provides the elec- tronic messaging services of an X.400 MTA, designed to conform to the 1992 CCITT series of recommendations and the 1988 joint CCITT and ISO Message Handling System Standards and their subsequent revisions. A messaging network based on MAILbus 400 MTAs can function as all, or part of, a Private Management Domain or Administration Management Do- main. MAILbus 400 MTA uses DECnet[TM]-Plus for OpenVMS Alpha for OSI[R] pro- tocol support, and OpenVMS Enterprise Directory for HP[TM] X.500 Di- rectory Services. Note that only with OpenVMS Enterprise Directory V5.3 and V5.4 can all the new features of V3.2 be realized. MAILbus 400 MTA operates over the OSI protocols, as supported by DECnet- Plus for OpenVMS Alpha. MAILbus 400 MTA can also operate over TCP/IP networks, using the RFC 1006 protocol, as supported by DECnet-Plus. The RFC 1006 protocol emulates the OSI Transport Service Protocol Class 0 over a TCP/IP network service. MAILbus 400 MTA can communicate with: o Another MAILbus 400 MTA March 2005 AE-QEFWG-TE HP MAILbus 400 Message Transfer Agent SPD 54.67.06 for OpenVMS Alpha, Version 3.2 o Another vendor's X.400 MTA MAILbus 400 MTA provides management services conforming to the HP En- terprise Management Architecture (EMA), integrated with DECnet-Plus. This provides local and remote management of MAILbus 400 MTA opera- tion. MAILbus 400 MTA supports an interface for messaging applications such as user agents and gateways. Access to this is provided by MAILbus 400 Application Program Interface for OpenVMS Alpha. MAILbus 400 MTA provides the following services to collect informa- tion about messages: o Accounting services, to record particular items of information about messages. o Archiving services, to retain complete copies of messages. o Message history logging services, to record information about mes- sages for tracing purposes. MAILbus 400 MTA provides an Interpersonal Messaging Service (IPMS) body- part conversion service, based on recipient capabilities registered in the directory. The set of body-part converters provided with MAIL- bus 400 MTA, provides a selected set of conversions between the fol- lowing body-part types: o IA5 o Teletex o ISO/6937 o General text (for ISO IR repertoires covering ISOLatin1, ISO/6937, and Teletex) o DEC[TM] Multinational Character Set o Message Router Text o WPS-PLUS[TM] o DECdx[TM] 2 HP MAILbus 400 Message Transfer Agent SPD 54.67.06 for OpenVMS Alpha, Version 3.2 o Upgrades body-parts from BP15 to FTBP MAILbus 400 MTA supports conversion between Externally Defined Body- parts and File Transfer Body-parts. In addition to providing conver- sion services, MAILbus 400 MTA supports transfer and receipt of any X.400 IPMS body-part types, and non-IPMS content types. New Features and Capabilities in V3.2 o MTA V3.2 provides a revised filter mechanism for restricting the delivering and relaying of mails to user agents/gateways or peer MTAs. The filter behavior is governed by the "Originator Restric- tion" attribute and provides the ability for a User to define an "Authorized Originators" and "Denied Originators" list of Origi- nators Partial or Complete Or address at the recipient Or address level. o The retry interval for an agent has been made a configurable pa- rameter o Comparison of routing instruction attributes, agents and domains has been made case-insensitive. o NCL output buffer size has been increased to 64K. This allows user to view large number of entries in the NCL output. o STA functionality can be enabled/disabled by means of an environ- ment variable MTA$STA. MAILbus 400 MTA is typically used in conjunction with other HP sup- plied messaging products, such as user agents and gateways. The fol- lowing are examples of messaging products that can be used in conjunc- tion with MAILbus 400 MTA to provide a complete messaging solution: o Office Server-This is an office system solution providing a wide range of services and supporting a number of different messaging clients. o MAILbus 400 SMTP Gateway for HP Tru64 UNIX[R]-This is a messaging gateway providing connectivity between SMTP and X.400 environments. 3 HP MAILbus 400 Message Transfer Agent SPD 54.67.06 for OpenVMS Alpha, Version 3.2 o HP/EDI[TM] for OpenVMS-This provides a wide range of services to enable Electronic Data Interchange (EDI) between business appli- cations. CONFORMANCE TO STANDARDS MAILbus 400 MTA for OpenVMS Alpha is designed to conform to the 1992 CCITT X.400 series of recommendations and the 1988 joint CCITT and ISO Message Handling System (MHS) standards, and the following revision documents: o Revision of the CCITT 1988 X.400 Series of Recommendations - The MHS Implementor's Guide Version 10 of February 1993 o Revisions of individual parts of International Standard ISO/IEC 10021 - Part 10021-1: Corrigenda 1, 2, 3, 4, 5, 6, and Amendment 2 - Part 10021-2: Corrigenda 1, 2, 3, 4, 5, 6, 7, and Amendments 1, 2 - Part 10021-4: Corrigenda 1, 2, 3, 4, 5, 6, 7, 8, and Amendment 1 - Part 10021-5: Corrigenda 1, 2, 3, 4, 5, 6, 7 - Part 10021-6: Corrigenda 1, 2, 3, 4, 5, 6, 7 - Part 10021-7: Corrigenda 1, 2, 3, 4, 5, and Amendment 1 MAILbus 400 MTA is designed to conform to the International Standard- ized Profile ISO/IEC ISP 10611 Common Messaging (AMH1n), and to the International Standardized Profile ISO/IEC ISP 12062 Interpersonal Mes- saging (AMH2n) and the following profiles: o The Stable Implementation Agreements for Open Systems Interconnec- tion Protocols, Version 7, Edition 1, December 1993, set up by the Open System Environment (OSE) Implementor's Workshop (OIW). o United States Government OSI Profiles (US GOSIP) V1.0, V2.0. o United Kingdom Government OSI Profile (UK GOSIP) V4.1. 4 HP MAILbus 400 Message Transfer Agent SPD 54.67.06 for OpenVMS Alpha, Version 3.2 o CEN/CENELEC profiles ENV 41201, 41202, 41214 HARDWARE REQUIREMENTS Processors Supported Any AlphaServer processor supported by DECnet-Plus for OpenVMS Alpha, provided the system has a minimum of 256 Mbytes of physical memory. See the DECnet-Plus for OpenVMS Alpha Software Product Description (50.45) for further information on supported hardware configurations. DISK SPACE REQUIREMENTS (Block Cluster Size = 1): Disk space required for 45K blocks installation: Disk space required for 40K blocks use (permanent): These counts refer to the disk space required on the system disk. The sizes are approximate. Actual sizes may vary depending on the user's system environment, configuration, and software options. CLUSTER ENVIRONMENT This layered product may be installed on each node in any valid and licensed VMScluster[TM] configuration. Each node of a VMScluster can run one instance of MAILbus 400 MTA. Each MTA is independent and does not share workspace and operates as it would on an individual system. VMScluster configurations are fully described in the VMScluster Soft- ware Product Description (29.78.xx) and include CI[TM], Ethernet, and Mixed Interconnect configurations. 5 HP MAILbus 400 Message Transfer Agent SPD 54.67.06 for OpenVMS Alpha, Version 3.2 SOFTWARE REQUIREMENTS One of the following software configurations: o OpenVMS V7.3-2, DECnet-Plus for OpenVMS V7.3-2, including the DEC- net Application Interface component. OpenVMS Enterprise Directory V5.3 OPTIONAL SOFTWARE o HP Office Server V6.0 or later provides an office solution with a wide range of services and supporting a number of different mes- saging clients o MAILbus 400 SMTP Gateway for DIGITAL UNIX V2.3 or later provides connectivity between SMTP and X.400 messaging environments o DEC/EDI for OpenVMS V2.1 or later is required for Electronic Data Interchange services OpenVMS Tailoring: The following OpenVMS classes are required for full functionality of this layered product: o OpenVMS Alpha Required Saveset o Network Support o Programming Support GROWTH CONSIDERATIONS The minimum hardware/software requirements for any future version of this product may be different from the requirements for the current version. 6 HP MAILbus 400 Message Transfer Agent SPD 54.67.06 for OpenVMS Alpha, Version 3.2 DISTRIBUTION MEDIA MAILbus 400 MTA is available as part of the HP Software Product Li- brary for OpenVMS Alpha Layered Products, part number QA-03XAA-H8. ORDERING INFORMATION Software Licenses: QL-3L3A*-** Software Documentation: QA-3L3AA-GZ.3.2 Software Product Services: QT-3L3A*-** * Denotes variant fields. For additional information on available li- censes, services, and media, refer to the appropriate price book. SOFTWARE LICENSING This software is furnished under the licensing provisions of HP's Stan- dard Terms and Conditions. For more information about HP's licensing terms and policies, contact your local HP office. License Management Facility Support This layered product supports the OpenVMS License Management Facil- ity. License units for this product are allocated on an Unlimited System Use and Concurrent Use basis. Each Concurrent Use license allows a specified number of messages to be processed by the MAILbus 400 MTA in a 24 hour period. If the num- ber of messages processed by the MAILbus 400 MTA in a 24 hour period exceeds the number of messages for which the MAILbus 400 MTA is li- censed, a warning message is output to inform users that they are in breach of their licensing agreement. The MAILbus 400 MTA will continue to process messages even if the licensed number of messages is exceeded. The MAILbus 400 MTA Unlimited System Use license imposes no restric- tions on the number of messages that the MAILbus 400 MTA can process in a 24 hour period. 7 HP MAILbus 400 Message Transfer Agent SPD 54.67.06 for OpenVMS Alpha, Version 3.2 All licenses for the MAILbus 400 MTA allow the installation and use of the MAILbus 400 MTA base component on any OpenVMS Alpha system op- erating an application that requires access to the MAILbus 400 MTA. For more information on the License Management Facility, refer to the OpenVMS Operating System Software Product Description. SOFTWARE PRODUCT SERVICES MAILbus 400 MTA for OpenVMS Alpha can participate in large distributed messaging networks, which may involve multiple vendors' systems in mul- tiple locations. HP offers a number of consulting services to assist customers in the planning, installation, management, and integration of these messaging networks. A variety of service options are available from HP. For more infor- mation, contact your local HP office. Warranty Limitations Absolute fidelity between an original document and the resulting doc- ument after MAILbus 400 MTA for OpenVMS Alpha has performed a body- part conversion on a message is not guaranteed. The differences be- tween the X.400 IPMS body-part definitions are such that conversions can result in a change in the formatting or content of a message body- part. SOFTWARE WARRANTY This software is provided by HP, with a warranty in accordance with the HP OpenVMS operating system warranty that it is installed upon. Confidential computer software. Valid license from HP required for pos- session, use or copying. Consistent with FAR 12.211 and 12.212, Com- mercial Computer Software, Computer Software Documentation, and Tech- nical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. 8 HP MAILbus 400 Message Transfer Agent SPD 54.67.06 for OpenVMS Alpha, Version 3.2 The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional war- ranty. HP shall not be liable for technical or editorial errors or omis- sions contained herein. OSI is a registered trademark of CA Management, Inc. ©2005 Copyright 2005 Hewlett-Packard Development Company, L.P. 9