       %                                COMPAQ   	  Software   Product  Description  D  ___________________________________________________________________  D  Product Name:  MAILbus 400 Message Transfer Agent      SPD 42.83.06-                 for OpenVMS VAX, Version 2.0C     PRODUCT DESCRIPTION  E  MAILbus 400[TM] Message Transfer Agent (MTA) for OpenVMS[TM] VAX[TM] E  is a layered software product that resides on an OpenVMS VAX system. G  MAILbus 400 MTA provides electronic messaging services in an open net- E  work environment. These services are used by messaging applications, E  such as user agents and gateways. MAILbus 400 MTA provides the elec- F  tronic messaging services of an X.400 MTA, designed to conform to theF  1992 CCITT series of recommendations and the 1988 joint CCITT and ISOD  Message Handling System Standards and their subsequent revisions. AD  messaging network based on MAILbus 400 MTAs can function as all, orF  part of, a Private Management Domain or Administration Management Do-  main.  E  MAILbus 400 MTA uses DECnet[TM]-Plus for OpenVMS for OSI[R] protocol D  support, and DIGITAL[TM] X.500 Directory Service for directory ser-  vices.   I  MAILbus 400 MTA operates over the OSI protocols, as supported by DECnet- D  Plus for OpenVMS. MAILbus 400 MTA can also operate over TCP/IP net-E  works, using the RFC 1006 protocol, as supported by DECnet-Plus. The D  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   *  o  A VAX Message Router[TM] X.400 Gateway  D                                                           April 1999  D                                                          AE-PVRPH-TE         o  Another vendor's X.400 MTA  D  MAILbus 400 MTA provides management services conforming to the COM-K  PAQ Enterprise Management Architecture (EMA), integrated with DECnet-Plus. D  This provides local and remote management of MAILbus 400 MTA opera-  tion.  F  MAILbus 400 MTA supports an interface for messaging applications suchG  as user agents and gateways. Access to this is provided by MAILbus 400   Application Program Interface.   D  MAILbus 400 MTA provides the following services to collect informa-  tion about messages:   H  o  Accounting services, to record particular items of information about
     messages.   >  o  Archiving services, to retain complete copies of messages.  F  o  Message history logging services, to record information about mes-     sages for tracing purposes.   I  MAILbus 400 MTA provides an Interpersonal Messaging Service (IPMS) body- D  part conversion service, based on recipient capabilities registeredE  in the directory. The set of bodypart converters provided with MAIL- D  bus 400 MTA provides a selected set of conversions between the fol-  lowing bodypart types:     o  IA5     o  Teletex     o  ISO/6937  F  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]  #                                   2        
  o  DECdx[TM]   E  MAILbus 400 MTA supports conversion between Externally Defined Body- D  parts and File Transfer Bodyparts. In addition to providing conver-D  sion services, MAILbus 400 MTA supports transfer and receipt of any7  X.400 IPMS bodypart types, and non-IPMS content types.   D  MAILbus 400 MTA is typically used in conjunction with other COMPAQ-H  supplied messaging products, such as user agents and gateways. The fol-G  lowing are examples of messaging products that can be used in conjunc- D  tion with MAILbus 400 MTA to provide a complete messaging solution:  E  o  DIGITAL Office Server-This is an office system solution providing F     a wide range of services and supporting a number of different mes-     saging clients.   *  o  MAILbus 400 Message Router Gateway forD     OpenVMS VAX - This provides a gateway between the X.400 environ-$     ment and Message Router systems.  D  o  MAILbus 400 SMTP Gateway for DIGITAL UNIX[R]-This is a messagingG     gateway providing connectivity between SMTP and X.400 environments.   D  o  MAILbus 400 Message Store for DIGITAL UNIX-This provides messageD     storage and submission services for users in an open network en-     vironment.  E  o  DEC/EDI[TM] for OpenVMS-This provides a wide range of services to D     enable Electronic Data Interchange (EDI) between business appli-     cations.  E  o  ISOGATE[TM] and ISOGATE Access Unit for cc:Mail[R]-These products F     together provide a gateway between MAILbus 400 MTA and the cc:Mail     electronic mail system.   E  o  ISOGATE and ISOGATE Access Unit for Microsoft[R] Mail-These prod- G     ucts together provide a gateway between MAILbus 400 MTA and the Mi- 8     crosoft Mail for PC Networks electronic mail system.  E  o  ISOCOR[R] X.400 Router for Lotus Notes[R]-This provides a gateway <     between MAILbus 400 MTA and the Lotus Notes environment.  #                                   3          CONFORMANCE TO STANDARDS   F  MAILbus 400 MTA is designed to conform to the 1992 CCITT X.400 seriesG  of recommendations. MAILbus 400 MTA is also designed to conform to the F  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  I  o  Revisions of individual parts of International Standard ISO/IEC 10021   A     -  Part 10021-1: Corrigenda 1, 2, 3, 4, 5, 6, and Amendment 2   F     -  Part 10021-2: Corrigenda 1, 2, 3, 4, 5, 6, 7, and Amendments 1,        2  E     -  Part 10021-4: Corrigenda 1, 2, 3, 4, 5, 6, 7, 8, and Amendment         1  3     -  Part 10021-5: Corrigenda 1, 2, 3, 4, 5, 6, 7   3     -  Part 10021-6: Corrigenda 1, 2, 3, 4, 5, 6, 7   >     -  Part 10021-7: Corrigenda 1, 2, 3, 4, 5, and Amendment 1  F  MAILbus 400 MTA is designed to conform to the International Standard-D  ized Profile ISO/IEC ISP 10611 Common Messaging (AMH1n), and to theH  International Standardized Profile ISO/IEC ISP 12062 Interpersonal Mes-  saging (AMH2n).  F  MAILbus 400 MTA is designed to conform to the following regional pro-  files:   F  o  The Stable Implementation Agreements for Open Systems Interconnec-F     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        0  o  CEN/CENELEC profiles ENV 41201, 41202, 41214    YEAR 2000 READY (Y2K)  E  MAILbus 400 Message Transfer Agent also becomes Year 2000 Ready with F  Version 2.0B release. Any two digit dates received by the MAILbus 400   MTA are interpreted as follows:  :  -  Years "70" to "99" (inclusive) as "1970" to "1999" and  7  -  Years "00" to "69" (inclusive) as "2000" to "2069".   E  MAILbus 400 MTA V2.0B will correctly process, calculate, compare and H  sequence date data from, into and between the twentieth and the twenty-G  first centuries, and the years 1999 and 2000, including leap year cal- D  culations, when used in accordance with the associated COMPAQ Prod-E  uct documentation and provided that all hardware, firmware and soft- E  ware used in combination with such COMPAQ Products properly exchange $  date data with the COMPAQ Products.    HARDWARE REQUIREMENTS    Processors Supported   H  Any OpenVMS VAX configuration supported by DECnet-Plus for OpenVMS VAX,F  with the exception of those listed below, and provided the system hasI  a minimum of 64 Mbytes of physical memory. See the DECnet-Plus for Open- D  VMS VAX Software Product Description (25.03.*) for further informa-+  tion on supported hardware configurations.     Processors Not Supported   E  MicroVAX[TM] I, VAXstation[TM] I, VAX-11/725, VAX-11/782, VAXstation   8000   2  Disk Space Requirements (Block Cluster Size = 1):        #                                   5          (  Disk space required for    19800 blocks  installation:  (  Disk space required for    17800 blocks  use (permanent):   F  These counts refer to the disk space required on the system disk. TheE  sizes are approximate. Actual sizes may vary depending on the user's 9  system environment, configuration, and software options.     CLUSTER ENVIRONMENT  D  This layered product may be installed on each node in any valid andE  licensed VMScluster[TM] configuration. Each node of a VMScluster can F  run one instance of MAILbus 400 MTA. Each MTA is independent and doesF  not share workspace and operates as it would on an individual system.  F  VMScluster configurations are fully described in the VMScluster Soft-F  ware Product Description (29.78.xx) and include CI[TM], Ethernet, and#  Mixed Interconnect configurations.     SOFTWARE REQUIREMENTS  .  One of the following software configurations:  %  o  OpenVMS VAX Operating System V6.2 )     DECnet/OSI for OpenVMS V6.3 with ECO8 E     DIGITAL X.500 Directory Service for OpenVMS (Base component) V3.0      (or later)  %  o  OpenVMS VAX Operating System V7.1 H     DECnet-Plus for OpenVMS V7.1 with ECO2, or later, including the DEC-F     net Application Interface component (formerly known as the OSI Ap-"     plications Kernel or OSAK[TM])F     DIGITAL X.500 Directory Service for OpenVMS (Base component), V3.0     or later      #                                   6        %  o  OpenVMS VAX Operating System V7.2 F     DECnet-Plus for OpenVMS V7.2, including the DECnet Application In-D     terface component (formerly known as the OSI Applications Kernel     or OSAK[TM], V3.0-003OE     DIGITAL X.500 Directory Service for OpenVMS (Base component) V3.0      (or later)    OPTIONAL SOFTWARE  G  o  Office Server V4.0 or later provides an office solution with a wide D     range of services and supporting a number of different messaging     clients   D  o  MAILbus 400 Message Router Gateway V1.1 or later is required for-     communication with Message Router systems   D  o  MAILbus 400 SMTP Gateway for DIGITAL UNIX V2.1 or later provides>     connectivity between SMTP and X.400 messaging environments  E  o  MAILbus 400 Message Store for DIGITAL UNIX V1.2 or later provides D     message storage and submission services in an open network envi-     ronment.  E  o  DEC/EDI for OpenVMS V2.1 or later is required for Electronic Data      Interchange services  E  o  ISOGATE and ISOGATE Access Unit for cc:Mail are required for com- #     munication with cc:Mail systems   G  o  ISOGATE and ISOGATE Access Unit for Microsoft Mail are required for -     communication with Microsoft Mail systems   E  o  ISOCOR X.400 Router for Lotus Notes is required for communication $     with the Lotus Notes environment  G  OpenVMS Tailoring: The following OpenVMS classes are required for full '  functionality of this layered product:     o  OpenVMS Required Saveset    o  Network Support   #                                   7          o  Programming Support   D  For more information on OpenVMS classes and tailoring, refer to theJ  OpenVMS VAX Operating System Software Product Description (SPD 25.01.xx).    GROWTH CONSIDERATIONS  E  The minimum hardware/software requirements for any future version of D  this product may be different from the requirements for the current	  version.     DISTRIBUTION MEDIA   D  MAILbus 400 MTA is available as part of the DIGITAL CD-ROM SoftwareC  Library for OpenVMS VAX Layered Products, part number QA-VWJ8A-H8.     ORDERING INFORMATION     Software Licenses: QL-04QA*-** )  Software Documentation: QA-04QAA-GZ.2.0C '  Software Product Services: QT-04QA*-**   G  *  Denotes variant fields. For additional information on available li- E     censes, services, and media, refer to the appropriate price book.     SOFTWARE LICENSING   D  This software is furnished under the licensing provisions of CompaqD  Equipment Corporation's Standard Terms and Conditions. For more in-D  formation about COMPAQ's licensing terms and policies, contact your  local COMPAQ office.   $  License Management Facility Support  D  This layered product supports the OpenVMS License Management Facil-  ity.   D  License units for this product are allocated on an Unlimited System  Use and Concurrent Use basis.  #                                   8        E  Each Concurrent Use license allows a specified number of messages to E  be processed by the MAILbus 400 MTA in a 24 hour period. If the num- E  ber of messages processed by the MAILbus 400 MTA in a 24 hour period D  exceeds the number of messages for which the MAILbus 400 MTA is li-F  censed, a warning message is output to inform the users that they areF  in breach of their licensing agreement. The MAILbus 400 MTA will con-E  tinue to process messages even if the licensed number of messages is 
  exceeded.  E  The MAILbus 400 MTA Unlimited System Use license imposes no restric- E  tions on the number of messages that the MAILbus 400 MTA can process   in a 24 hour period.   D  All licenses for the MAILbus 400 MTA allow the installation and useD  of the MAILbus 400 MTA base component on any OpenVMS VAX system op-D  erating an application that requires access to the MAILbus 400 MTA.  F  For more information on the License Management Facility, refer to the7  OpenVMS Operating System Software Product Description.     SOFTWARE PRODUCT SERVICES  D  MAILbus 400 MTA can participate in large distributed messaging net-E  works, which may involve multiple vendors' systems in multiple loca- D  tions. COMPAQ offers a number of consulting services to assist cus-E  tomers in the planning, installation, management, and integration of   these messaging networks.  E  A variety of service options are available from COMPAQ. For more in- -  formation, contact your local COMPAQ office.     SOFTWARE WARRANTY  G  Warranty for this software product is provided by COMPAQ with the pur- G  chase of a license for the product as defined in the Software Warranty   Addendum of this SPD.    Warranty Limitations     #                                   9        F  Absolute fidelity between an original document and the resulting doc-E  ument after MAILbus 400 MTA has performed a bodypart conversion on a H  message is not guaranteed. The differences between the X.400 IPMS body-E  part definitions are such that conversions can result in a change in 1  the formatting or content of a message bodypart.     9  [R] OSI is a registered trademark of CA Management, Inc.   7  [R] cc:Mail is a registered trademark of cc:Mail, Inc.   B  [R] Microsoft is a registered trademark of Microsoft Corporation.  0  [R] ISOCOR is a registered trademark of ISOCOR.  '  [TM] ISOGATE is a trademark of ISOCOR.   A  [R] Lotus and Lotus Notes are registered trademarks of Lotus De-       velopment Corp.  B  [R] UNIX is a registered trademark in the United States and otherC      countries licensed exclusively through X/Open[TM] Company Ltd.   :  [TM] X/Open is a trademark of the X/Open Company Limited.  @  [TM] The COMPAQ Logo, CI, DEC, DEC/EDI, DECdx, DECnet, DIGITAL,?      MAILbus 400, Message Router, MicroVAX, OpenVMS, OSAK, VAX, B      VMScluster, VAXstation, and WPS-PLUS are trademarks of COMPAQ      Computer Corporation.  E  Compaq Computer Corporation makes no representations that the use of F  its products in the manner described in this publication will not in-D  fringe on existing or future patent rights, nor do the descriptionsF  contained in this publication imply the granting of licenses to make,G  use, or sell equipment or software in accordance with the description.   E  Possession, use, or copying of the software described in this publi- H  cation is authorized only pursuant to a valid written license from COM-"  PAQ or an authorized sublicensor.  C   Compaq Computer Corporation 1993,1998,1999. All rights reserved.   #                                  10                                                                                                                                                                                                                                                     