DIGITAL Software Product Description ___________________________________________________________________ Product Name: MAILbus 400 SMTP Gateway SPD 46.91.02 for Digital UNIX, Version 2.1 PRODUCT DESCRIPTION MAILbus 400[TM] SMTP Gateway brings together the world's global mes- saging systems - the Internet[R] and X.400. MAILbus 400 SMTP Gateway provides a comprehensive solution to inter- working between the Internet and X.400 environments, based on the lat- est Internet and X.400 messaging standards. MAILbus 400 SMTP Gateway enables Internet and X.400 users to exchange a wide range of information, from simple text messages to complex doc- uments and binary information. MAILbus 400 SMTP Gateway uses the Mul- tipurpose Internet Mail Extensions (MIME) definitions to ensure the highest level of compatibility for information exchanged between the Internet and X.400. MAILbus 400 SMTP Gateway is flexible in its operation, providing cus- tomers with extensive control over address and data mapping. This means that customers can tune the MAILbus 400 SMTP Gateway's operation to match the needs of their particular messaging environment. In addition to supporting the latest Internet messaging standards, MAIL- bus 400 SMTP Gateway also includes support for `8-bit' sendmail sys- tems. MAILbus 400 SMTP Gateway provides customers with control over the interpretation and mapping of information in an `8-bit' sendmail environment. March 1996 AE-Q422C-TE MAILbus 400 SMTP Gateway operates on Digital[TM] UNIX[R]. MAILbus 400 SMTP Gateway makes use of other Digital products to connect to the In- ternet and X.400. MAILbus 400 SMTP Gateway uses the MAILbus 400 Mes- sage Transfer Agent for X.400 connectivity, and the SMTP mailer com- ponent of Digital UNIX for Internet connectivity. MAILbus 400 SMTP Gate- way uses the DEC X.500 Directory Service for address translation. CONFORMANCE TO STANDARDS Internet Standards The following Internet messaging standards are relevant to MAILbus 400 SMTP Gateway: o RFC 1327 - This specifies how to map messages between the Inter- net and X.400. MAILbus 400 SMTP Gateway implements RFC 1327, with the following exceptions: - MAILbus 400 SMTP Gateway does not implement the sections refer- ring to message body translation, which have been superseded by RFC 1494 and RFC 1495. - Section 2.2.1, which specifies mappings for unknown Internet mes- sage headers. MAILbus 400 SMTP Gateway implements an alterna- tive mapping, designed to improve interworking. o RFC 1494 - This specifies how to map single MIME body part messages between the Internet and X.400. MAILbus 400 SMTP Gateway implements RFC 1494, with the following exceptions: - MAILbus 400 Gateway does not implement support for the Generic MIME Extended Body Part specified in section 5.2. - MAILbus 400 SMTP Gateway does not implement support for the con- tent type/subtype combination of application/x400-bp defined in section 6.1. - MAILbus 400 SMTP Gateway implements some alternative body part translations to those specified in RFC 1494. 2 o RFC 1495 - This specifies how to map between MIME multipart mes- sages and X.400. MAILbus 400 SMTP Gateway implements RFC 1495, with the following exception: - The MAILbus 400 SMTP Gateway does not generate or translate the IPMS Heading Extensions for multipart messages, as defined in section 3.2.2 of RFC 1495. MAILbus 400 SMTP Gateway implements an alternative mechanism, designed to improve interworking. o RFC 1521 - MIME Part One. MAILbus 400 SMTP Gateway implements all aspects of RFC 1521 that are relevant to a messaging gateway. o RFC 1522 - MIME Part Two. MAILbus 400 SMTP Gateway implements all aspects of RFC 1522 that are relevant to a messaging gateway. o RFC 1137 - This specifies alternative translations for text char- acters known to cause interworking problems for Internet applica- tions when included in mail addresses. MAILbus 400 SMTP Gateway im- plements all of RFC 1137, but can also be configured to provide other translations, depending on the requirements of the customer. o RFC 1154 - This RFC has been superseded by RFC 1521. MAILbus 400 SMTP Gateway does not implement support for RFC 1154. o The MIXER Specification - This is not yet an RFC, but the MAILbus 400 SMTP Gateway implements the following aspects of MIXER: - MAILbus 400 SMTP Gateway translates X.400 reports into Deliv- ery Status Notifications (DSNs). - MAILbus 400 SMTP Gateway can be configured to perform MIXER ad- dress comment handling. - MAILbus 400 SMTP Gateway supports MIXER address mapping tables. - MAILbus 40 SMTP Gateway can resolve a bodypart with the type/subtype combination message/external body. X.400 Standards 3 MAILbus 400 SMTP Gateway constructs and interprets X.400 messages as defined in CCITT Recommendations X.411 and X.420 (1992). HARDWARE REQUIREMENTS Processors Supported Any Alpha AXP[TM] processor supported by Digital UNIX, provided the system has a minimum of 64 Mbytes of physical memory. The Digital UNIX Software Product Description (41.61.*) contains a list of supported processors. Disk Space Requirements Disk space required for 2650 Kbytes installation: Disk space required for 2650 Kbytes 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. SOFTWARE REQUIREMENTS o Digital UNIX Version 3.0 or later o DECnet[TM]/OSI[R] for Digital UNIX V3.0 or later o MAILbus 400 Message Transfer Agent for Digital UNIX (Base Subset), V1.4A or later o Digital X.500 Directory Service for Digital UNIX (Base Subset), V2.0A or later MAILbus 400 SMTP Gateway also requires a MAILbus 400 MTA and Digital X.500 Directory Server to be available. These servers can either be on the same system as MAILbus 400 SMTP Gateway, or on a remote sys- tem. 4 GROWTH CONSIDERATIONS The minimum hardware/software requirements for any future version of this product may be different from the requirements for the current version. DISTRIBUTION MEDIA MAILbus 400 SMTP Gateway is available as part of the Digital CD-ROM Software Library for Digital UNIX Layered products, part number QA- 054AA-H8. ORDERING INFORMATION Software Licenses: QL-0NNA9-** Software Documentation: QA-0NNAA-GZ Software Product Services: QT-0NNA9-** * Denotes variant fields. For additional information on available li- censes, services, and media, refer to the appropriate price book. The above information is valid at time of release. Please contact your local Digital office for the most up-to-date information. SOFTWARE LICENSING This software is furnished under the licensing provisions of Digital Equipment Corporation's Standard Terms and Conditions. For more in- formation about Digital's licensing terms and policies, contact your local Digital office. License Management Facility Support This layered product supports the Digital UNIX License Management Fa- cility. License units for this product are allocated on an Unlimited System Use basis. 5 For more information on the License Management Facility, refer to the Digital UNIX Software Product Description (41.61.*). SOFTWARE PRODUCT SERVICES MAILbus 400 SMTP Gateway for Digital UNIX can participate in large dis- tributed messaging networks, which may involve multiple vendors' sys- tems in multiple locations. Digital offers a number of consulting ser- vices to assist customers in the planning, installation, management, and integration of these messaging networks. A variety of service options are available from Digital. For more in- formation, contact your local Digital office. SOFTWARE WARRANTY Warranty for this software product is provided by Digital with the pur- chase of a license for the product as defined in the Software Warranty Addendum of this SPD. [R] Internet is a registered trademark of Internet, Inc. [R] OSI is a registered trademark of CA Management, Inc. [R] UNIX is a registered trademark in the United States and other countries licensed exclusively through X/Open Company Ltd. [TM] The DIGITAL Logo, AXP, DEC, DECnet, Digital, and MAILbus 400, are trademarks of Digital Equipment Corporation. Digital Equipment Corporation makes no representations that the use of its products in the manner described in this publication will not infringe on existing or future patent rights, nor do the descriptions contained in this publication imply the granting of licenses to make, use, or sell equipment or software in accordance with the description. 6 Possession, use, or copying of the software described in this publi- cation is authorized only pursuant to a valid written license from Dig- ital or an authorized sublicensor. © Digital Equipment Corporation 1992, 1996. All rights reserved. 7