Software Product Description ___________________________________________________________________ PRODUCT NAME: MailWorks for OpenVMS, Version 1.3A SPD 39.59.02 DESCRIPTION This document describes the following components of the MailWorks prod- uct family: MailWorks Server for OpenVMS, MailWorks for OpenVMS Video Terminals and MailWorks for OpenVMS DECwindows. These components are layered software products that reside on OpenVMS. MailWorks is an electronic messaging application that implements the international messaging standards set by the CCITT X.400 P2 recommen- dations. It provides a means of exchanging messages and attached data with other users. Layered on top of Digital Equipment Corporation's VAX Message Router (SPD 26.33.xx), MailWorks interacts with all other MAILbus gateways and complementary products. The MailWorks Server for OpenVMS supports clients on DOS PC, Microsoft Windows environment and Apple Macintosh computers. The supported clients include MailWorks for DOS, the TeamLinks products for Microsoft Win- dows and Macintosh, cc:Mail Connection for Mailworks, and the Microsoft Mail Driver for MailWorks. The MailWorks Server for OpenVMS supports the MailWorks for OpenVMS Video Terminals and MailWorks for OpenVMS DECwindows components. The MailWorks for OpenVMS Video Terminals and MailWorks for OpenVMS DECwindows components reside with the MailWorks Server and are not clients. MailWorks for OpenVMS on VAX and AXP are identical in functionality, with the following restrictions: o Clusters of mixed VAX and AXP are not supported. o MailWorks for OpenVMS DECwindows is not supported on AXP. DIGITAL January 1995 AE-PNDEC-TK o ALL-IN-1 Mail for Macintosh and ALL-IN-1 Mail for Windows are not supported on AXP. o The MailWorks WAN and LAN packages are available only on VAX. o DX, WPL, DDIF, and DTIF converters are not included on AXP. MailWorks was formerly named ALL-IN-1 MAIL and DEC MAILworks. Client software performs services for users. This software resides on an intelligent desktop device and takes advantage of the processing power on the desk. The OpenVMS components (for Video Terminals or DECwindows devices) run on the OpenVMS VAX operating system and must reside within the same node or VAXcluster as the server. Clients are connected to the MailWorks Server, which performs local and wide area network delivery services. Transport between MailWorks Servers, and between MailWorks Servers and the ALL-IN-1 product family, is performed by the VAX Message Router. Optional gateways may also be connected to the VAX Message Router as needed for mail transfer in a multivendor environment. Users might alternately use an intelligent workstation in the office, a video terminal at home, or a laptop PC while traveling. Clients are provided for all three situations and for others, all using the same user mailbox and files on the server. MailWorks adheres to the National Institute for Science and Technol- ogy (NIST) profile of 1984 CCITT X.400 recommendations. It provides a level of messaging service compatible with that of the electronic messaging subsystem of the ALL-IN-1 integrated office system, and adds new service elements defined in X.400 and MailWorks. 2 Features Transports The MailWorks Server for OpenVMS supports three different client-to- server transport connections. They are DECnet, TCP/IP, and asynchronous connections with Kermit or Zmodem. The MailWorks Server can support all of these transports simultane- ously. The client specifies which transport it will use to connect to the server. By default the server will support DECnet and asynchronous connections. To make a TCP/IP connection, the proper software must be running on the server along with the correct configuration modifica- tions to enable this transport. Even if DECnet is not being used to connect from the client to the Mail- Works Server, it is still required to run on the VAX with the Mail- Works Server for the various network connections made by the MailWorks Server. Compatibility with VMSmail Users can migrate easily from VMSmail to MailWorks. The interfaces are logical extensions of the VMSmail interface, and commands and services will be familiar. Addresses and distribution lists used in VMSmail can be used in MailWorks. From the OpenVMS components, nickname logicals may be used. Most addresses used in VMSmail distribution lists may be used in MailWorks with similar restrictions as found when using such a list from another node. No file cabinet conversion is required for the Video Terminal compo- nent. A one-time file cabinet conversion is required to make OpenVMS mail messages available from the PC. Messages can be exchanged with VMSmail on the same system or elsewhere in the network by means of the VAX Message Router VMSmail Gateway. This is included in the MailWorks Wide Area Network and Local Area Network Server Packages for VAX or can be purchased as an option. 3 Users can select an editor for use in MailWorks Video Terminal and DECWin- dows components. Any editor called or spawned under VMSmail can be called or spawned from MailWorks. Compatibility with ALL-IN-1 Messages can be exchanged with the ALL-IN-1 integrated office system by means of the VAX Message Router using the same style of address- ing. The services of MailWorks are compatible with services in the elec- tronic messaging subsystem of ALL-IN-1. For example, read receipts from either product are honored by the other. Distribution lists created in the ALL-IN-1 integrated office system can be used in MailWorks. They work with the same restrictions found when sending a list to another ALL-IN-1 office system node. (Refer to product documentation for details.) Addressing strings used in the ALL-IN-1 office system work equally well in MailWorks, with the exception of addressing strings that invoke ALL-IN-1 foreign protocol hook (those beginning with an underscore). X.400 Message Transport Messages can be exchanged with other MailWorks domains and services that meet international X.400 P2 conformance criteria. Within a customer network, messages are transported by means of VAX Message Router. Transport to another vendor's X.400 service requires an OSI networking stack and the VAX Message Router X.400 Gateway (MRX). OSI message exchange requires at least one MRX Gateway in each Dig- ital domain (usually one per customer network). Refer to the VAX Mes- sage Router X.400 Gateway Software Product Description (SPD 27.50.xx) for hardware/software requirements. Supporting the Multivendor Environment 4 MAILbus offers a series of off-the-shelf gateways and a gateway de- velopment kit to create other gateways for message exchange with other vendors' proprietary mail systems. Refer to the appropriate Software Product Description for the products' hardware/software requirements. Addressing Options MailWorks uses Digital's Enterprisewide Distributed Directory Service (DDS) as its user address directory. This distributed directory, avail- able as part of the VAX Message Router, links MailWorks, TeamLinks Mail, the ALL-IN-1 integrated office system, the gateways, and any other agents sharing its directory services. The DDS directory is a networking resource available only while the server connection is in place. In addition, the MailWorks OpenVMS components provide a Personal Ad- dress Book (PAB). The PAB allows users to store and retrieve commonly used mail addresses, along with name, phone number, and nickname. The MailWorks OpenVMS components also support creation and access of distribution lists, which provides an easy way to address large groups of users. These distribution lists can be shared among a group of users by using the OpenVMS Access Control facilities. During addressing, users can easily access DDS, the PAB, and distri- bution lists. All three services can be used in combination during mes- sage creation. Filing Services MailWorks provides a filing structure of drawers and folders as well as access to RMS files. Filing services are similar in nature to VMS- mail. A DECwindows device with local storage may have one or more draw- ers on the local device in addition to one or more drawers on the server. OpenVMS based drawers may be shared among groups of users, with each user's privileges defined by OpenVMS access controls. Message Retrieval 5 Messages can be retrieved based on user specification of certain header fields and filing structures. File Formats MailWorks is designed to handle various file formats with features that allow configuration for maximum readability of messages. The system allows for the automated handling of messages in different formats and for invocation of other file formatting or conversion routines. The MailWorks OpenVMS components can be set up to invoke viewers or applications based on the file type of each attachment. MailWorks can be set to perform automatic conversions of message com- ponents as they are delivered, using optional third-party converters such as KEYpak for OpenVMS (SPD 32.71.xx). This is an additional-cost option. Users can register their file format preferences in the pro- file. For advice on interchange of specific file formats, especially across gateways, consult your local Digital office. Help Users can get help for MailWorks using the Help facility. Help pro- vides basic information on how to perform the function in question with- out users having to reference the documentation. Printing MailWorks takes advantage of Digital's standard OpenVMS printing. Users can specify the printer destination and options. Messaging Functions Users can create, read, and send messages using the commands provided. Messages can contain information in a variety of file format types. Messages can be forwarded to another destination. Message attachments may include another message, a document or file, or even a binary file. 6 When replying to a message, the system automatically addresses the an- swer for transfer back to the original sender. Users can reply to the sender, all the original recipients, or to a reply-to list. Messages can be addressed to one or more users at any valid MAILbus destination (e.g., VMSmail, X.400, etc.) worldwide. File formats may possibly be modified by gateways or user agents to make the memo read- able to the recipient. Not all file formats are supported by all gate- ways and user agents. Care should be taken in planning the network ca- pabilities to ensure maximum readability of memos. Delivery Reports and Read Receipts Users can specify Delivery Reports and Read Receipts when sending a message. This causes a message to be generated and returned to the orig- inator when the message is delivered or read. New Mail Notification Users can choose to receive notification of the arrival of new mes- sages. Message Redirection Users can request that all incoming messages be automatically redi- rected to a secondary address. Priority-Based Delivery Users can choose priority for message delivery. The grade of deliv- ery (express, first class, second class) can be specified. Message Classes Users can set a number of indicators to give the recipient informa- tion about the nature of the message: Importance (high, medium, low), Sensitivity (not restricted, personal, private, company confidential). These fields may also be used to locate classes of messages in the file cabinet. System Management 7 Required local system management for the mail system is minimal and usually automated. A system manager or administrator is required to create a standard OpenVMS account; when the user first accesses MailWorks, basic account setup functions are performed automatically; most rou- tine functions can be performed by the users. There are no special utilities to run for file cabinet maintenance. All user areas on the server should be backed up or restored using stan- dard OpenVMS utilities. The mail management design adheres to the coordinated management sys- tem used by the MAILbus family of products. The MailWorks Server pro- vides a management utility that allows configuration changes to be made and the status of the mail system to be checked. Internationalization MailWorks Server for OpenVMS, MailWorks for OpenVMS Video Terminals, and MailWorks for OpenVMS DECwindows are designed to support multi- lingual operations. They can be deployed in a multilingual network and can support multilingual operations on a single server system. Mail- Works Server for OpenVMS, MailWorks for OpenVMS Video Terminals, and MailWorks for OpenVMS DECwindows support the Digital Multinational char- acter set. MailWorks Documentation MailWorks Server documentation consists of the MailWorks for OpenVMS Installation and the MailWorks for OpenVMS System Manager's Guide. The installation guide includes information on installing the DECwindows and Video Terminals components. The documentation also includes user guides for the DECWindows and Video Terminal components. 8 MailWorks for OpenVMS Video Terminals MailWorks for OpenVMS Video Terminals looks like VMSmail but commu- nicates directly with the MailWorks Server, and uses a rich protocol that accesses the full range of messaging services. This component is co-located with the MailWorks Server. It provides ordinary terminals with the same access to the services of MailWorks. MailWorks for OpenVMS DECwindows MailWorks for OpenVMS DECwindows is a DECwindows component of Mail- Works. MailWorks for OpenVMS DECwindows adheres to the DECwindows Style Guide and can be used either on a workstation that is co-located with the MailWorks server or remotely using an X11 display server device supported by Digital. Access from Other Platforms Because MailWorks conforms to the DECwindows standards, users of de- vices which have X-servers available can access the mail software. In this case, the message composition and storage activities are not han- dled on the desktop device but on the MailWorks platform. The windows display is handled by the desktop device. This feature provides ac- cess for additional desktop devices that conform to the DECwindows stan- dards. HARDWARE REQUIREMENTS Processors Supported VAX: VAX 4000 Model 100 VAX 4000 Model 200 VAX 4000 Model 300 VAX 4000 Model 400 VAX 4000 Model 500 VAX 4000 Model 600 9 VAX 6000 Model 200 Series VAX 6000 Model 300 Series VAX 6000 Model 400 Series VAX 6000 Model 500 Series VAX 6000 Model 600 Series VAX 7000 Model 600 Series VAX 8200, VAX 8250, VAX 8300 VAX 8350, VAX 8500, VAX 8530 VAX 8550, VAX 8600, VAX 8650 VAX 8700, VAX 8800, VAX 8810 VAX 8820, VAX 8830, VAX 8840 VAX 9000 Model 110 VAX 9000 Model 210 VAX 9000 Model 300 Series VAX 9000 Model 400 Series VAX 10000 Model 600 Series 10 VAX 4050 VAX 4100/4100A/4105/4105A VAX 4200 VAX 4500 VAX 4600 VAX 6220/6230/6240 VAX 6320/6330/6340/6350/6360 VAX 6410/6420/6430/6440/6450/6460 VAX 6510/6520/6530/6540/6550/6560 VAX 6610/6620/6630/6640/6650/6660 VAX 7610/7620/7630/7640/7650/7660 VAX 7710/7720/7730/7740/7750/7760 VAX 8200/8250 VAX 8300/8350 VAX 8530/8550 VAX 8600/8650 VAX 8700 VAX 8800/8810/8820/8830/8840/8842 VAX 8974/8978 VAX 9210 VAX 9410/9420/9430/9440 VAX 10610/10620/10630/10640/10650/10660 VAX 10710/10720/10730/10740/10750/10760 VAX 730 VAX 750 VAX 780/785 VAXft Model 110 VAXft Model 310 VAXft Model 410 VAXft Model 610 VAXft Model 612 VAX-11/750, VAX-11/780, VAX-11/785 11 VAXft 310/410/610/810 VAX 4300 VAX 4400 VAX 4500A/4505A VAX 4600A VAX 4700A/4705A VAX 6210 VAX 6310 VAXft 100 VAXft 310/410/610 Server MicroVAX: MicroVAX II, MicroVAX 2000 MicroVAX 3100 MicroVAX 3100 Model 10/10E MicroVAX 3100 Model 20/20E MicroVAX 3100 Model 30 MicroVAX 3100 Model 40 MicroVAX 3100 Model 80 MicroVAX 3100 Model 85 MicroVAX 3100 Model 90 MicroVAX 3100 Model 95 MicroVAX 3300, MicroVAX 3400 MicroVAX 3500, MicroVAX 3600 MicroVAX 3800, MicroVAX 3900 VAXstation:VAXstation II, VAXstation 2000 VAXstation 3100 VAXstation 3100 Model 30 VAXstation 3100 Model 38 VAXstation 3100 Model 40 VAXstation 3100 Model 48 VAXstation 3100 Model 76 VAXstation 3200, VAXstation 3500 VAXstation 3520, VAXstation 3540 12 VAXstation 4000 Model 60 VAXstation 4000 Model 90 VAXstation 4000 VLC VAXstation 8000 VAXserver: VAXserver 3100, VAXserver 3300, VAXserver 3400, VAXserver 3500, VAXserver 3600, VAXserver 3602, VAXserver 3800, VAXserver 3900 VAXserver 4000 Model 200 VAXserver 4000 Model 300 VAXserver 4000 Model 500 VAXserver 6000 Model 210 VAXserver 6000 Model 220 VAXserver 6000 Model 310 VAXserver 6000 Model 320 VAXserver 6000 Model 410 VAXserver 6000 Model 420 VAXserver 6000 Model 510 VAXserver 6000 Model 520 VAXserver 6000 Model 610 VAXserver 6000 Model 620 VAXserver 6000 Model 630 VAXserver 6210 VAXserver 6310 VAXserver 6220 VAXserver 6320 VAXserver 6410/6420 VAXserver 6510/6520 VAXserver 9110 VAXserver 9310/9320/9330/9340 Processors Not Supported VAX: VAX-11/725, VAX-11/730, VAX-11/782 13 MicroVAX: MicroVAX I VAXstation:VAXstation I, VAXstation 8000 14 AXP: DEC/4610, DEC/4620 DEC/4710, DEC/4720 DEC/7610, DEC/7620, DEC/7630, DEC/7640 DEC/7700 DEC/10610, DEC/10620, DEC/10630, DEC/10640 DEC/3500, DEC/3500S, DEC/3500X DEC/3800, DEC/3800S DEC/3900 AlphaServer 2000 4/200 AlphaServer 2100 4/275, AlphaServer 2100 4/200 DEC/2300S DEC/2500 DEC/3300, DEC/3300L, DEC/3300X, DEC/3300LX DEC/3400, DEC/3400S DEC/3600, DEC/3600S DEC/3700 VMEAlpha64/SP AXPvme, AXPpci 33 AlphaStation 200 4/233, AlphaStation 200 4/166 AlphaStation 400 4/233 AlphaStation 600 4/266 AlphaServer 1000 4/200 AlphaStation 400 AlphaStation 200 AlphaServer 2200 4/275 DEC/7600 SMP DEC/10600 SMP DEC/4600 SMP DEC/4700 SMP AlphaServer 2000 4/200 SMP, 2100 4/200 SMP DEC/7700 SMP AlphaServer 2100 4/275 SMP 15 Other Hardware Requirements MailWorks for OpenVMS Video Terminals The software for MailWorks for OpenVMS Video Terminals is packaged with the MailWorks Server for OpenVMS and runs on all the same supported processors as the server. The MailWorks command-line interface is supported on any VT1xx, VT2xx, VT3xx terminal or any output device running a Digital-supplied and - supported emulator for the above. MailWorks for OpenVMS DECwindows The software for MailWorks for OpenVMS DECwindows is packaged with the MailWorks Server for OpenVMS and runs on all the same supported pro- cessors as the server. Use of the interface requires one of the fol- lowing workstations, or a valid X11 display device supported by Dig- ital. VAXstation:VAXstation II, VAXstation 2000 VAXstation 3100 Series, VAXstation 3200 VAXstation 3500, VAXstation 3520 VAXstation 3540 Processor Restrictions A TK50 Tape Drive is required for standalone MicroVAX 2000 and VAXs- tation 2000 systems. The component software must run within the same VAXcluster as the server software. When the product is used remotely by an X11 display device, the in- terface quality depends on the screen size, resolution and aspect of the X11 display server device. 16 Disk Space Requirements for OpenVMS Components (Block Cluster Size = 1) ___________________________________________________________________ During instal- lation___________After_____________________________________________ 22,000___________15,000____________________________________________ The sizes are approximate; actual sizes may vary depending on the user's system environment, configuration, and software options. The user space required on the server is determined by the amount of mail the user files. Memory Requirements for DECwindows Support The minimum supported memory for this application running in a stan- dalone DECwindows environment with both the client and server execut- ing on that same system is 8 MB. The performance and memory usage of DECwindows applications are par- ticularly sensitive to system configuration. Less memory may be re- quired on the client system (the system where the software is installed and executed) if the display server (the component that displays the application) resides on another system. More memory may be required on a system with several applications running, or where it may be de- sirable to improve the performance of an application. CLUSTER ENVIRONMENT The OpenVMS layered product components of this product are fully sup- ported when installed on any valid and licensed VAXcluster* config- uration without restrictions. The HARDWARE REQUIREMENTS sections of this Software Product Description detail any special hardware required by this product. * V5.x VAXcluster configurations are fully described in the VAXclus- ter Software Product Description (SPD 29.78.xx) and include CI, Eth- ernet, and Mixed Interconnect configurations. 17 SOFTWARE REQUIREMENTS REQUIRED SOFTWARE For the MailWorks Server for OpenVMS to support any or all of the clients, and for MailWorks for OpenVMS Video Terminals: OpenVMS VAX: o OpenVMS VAX Operating System V5.5-2 or higher o DECnet * DECnet for OpenVMS VAX V5.5 or higher, or * DECnet/OSI for OpenVMS VAX V5.6B ECO 10 or higher (Note: long node names are not supported) OpenVMS AXP: o OpenVMS AXP Operating System, V6.1 o DECnet * DECnet for OpenVMS AXP V6.1, or * DECnet/OSI for OpenVMS AXP V5.8 (Note: long node names are not supported) The MailWorks Server delivers messages among all the users of any com- bination of the available clients or components that use this one server. Thus, all users on a single VAXcluster or on a single LAN may exchange messages via a single MailWorks Server. The VAX Message Router Transfer Service is required to exchange mes- sages with users on other servers or other electronic messaging prod- ucts. On OpenVMS VAX, it may co-reside with the MailWorks Server or may reside on another DECnet node. On OpenVMS AXP, it must reside on another VAX node. To communicate with VMSmail users, the VMSmail Gate- way is also required. 18 Most configurations will require VAX Message Router, and all sites mi- grating from or interacting with a VMSmail product will require the VMSmail Gateway. The MailWorks Wide Area Network and Local Area Net- work Server Packages combine these underlying software components with the MailWorks Server on VAX. For the MailWorks for OpenVMS DECwindows on the Workstation (not avail- able on OpenVMS AXP) o OpenVMS VAX Operating System V5.5-2 or higher (and necessary com- ponents of OpenVMS DECwindows) o DECnet * DECnet for OpenVMS VAX V5.5 or higher, or * DECnet/OSI for OpenVMS VAX V5.6B ECO 10 or higher (Note: long node names are not supported). This product can run in any of the following ways: o On a workstation that is a member of the same Local Area VAXclus- ter as the mail server software o On a separate workstation device that is not a member of the VAX- cluster where the component and mail server software are running, but is connected to VAXcluster via DECnet o On the server CPU or VAXcluster using an attached X11 display de- vice supported by Digital OpenVMS DECwindows is part of the OpenVMS Operating System but must be installed separately. Installation of OpenVMS DECwindows gives the user the option to install any or all of the following three compo- nents: o OpenVMS DECwindows Compute Server (Base kit; includes runtime sup- port) o OpenVMS DECwindows Device Support o OpenVMS DECwindows Programming Support 19 For standalone execution, the following DECwindows components must be installed on the workstation machine: o OpenVMS DECwindows Compute Server o OpenVMS DECwindows Device Support For remote execution, the following DECwindows components must be in- stalled on the machines: On the X11 Display Device: o OpenVMS DECwindows Compute Server o OpenVMS DECwindows Device Support o OpenVMS DECwindows Programming Support On the X11 Client System: o OpenVMS DECwindows Compute Server o OpenVMS DECwindows Device Support o OpenVMS DECwindows Programming Support OPTIONAL SOFTWARE OpenVMS VAX: o TCP/IP * DEC TCP/IP Services for OpenVMS V3.2 (SPD 25.A4.xx) * TCP/IP MultiNet V3.3 Revision B or higher * Wollongong Pathway Runtime V1.1 and Wollongong Pathway Access V1.0 o VAX Message Router V3.3 or higher (SPD 26.33.xx) o VAX Message Router VMSmail Gateway V3.3 or higher (SPD 26.33.xx) o VAX Message Router/P Gateway V1.3 or higher (SPD 28.94.xx) (to con- nect to IBM PROFS and OfficeVision/VM systems) 20 o VAX Message Router/S Gateway V1.3 or higher (SPD 29.24.xx) (to con- nect to IBM DISOSS systems) o VAX Message Router X.400 Gateway V2.3 or higher (SPD 27.50.xx) o CDA Converter Library for OpenVMS V2.2 (SPD 31.31.xx) o KEYpak for OpenVMS V3.2 (SPD 32.71.xx) o PATHWORKS for OpenVMS, Version 4.2 or higher (only needed if us- ing MailWorks for DOS new mail notification). OpenVMS AXP: o TCP/IP * DEC TCP/IP Services for OpenVMS AXP V3.2 * TCP/IP MultiNet V3.3 Revision B or higher * Wollongong Pathway Runtime V1.1 and Wollongong Pathway Access V1.1 o VAX Message Router V3.3A (Note: Message Router only runs on a VAX and must be accessed remotely from the AXP). o KEYpak for OpenVMS V3.2 (SPD 32.71xx) o PATHWORKS for OpenVMS, Version 4.2 or higher (only needed if us- ing MailWorks for DOS new mail notification). 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 9-track 1600 BPI Magtape, TK50 Streaming Tape 21 ORDERING INFORMATION Operation of the MailWorks Server for OpenVMS product requires at least one mail client or MailWorks for OpenVMS Video Terminals or Mailworks for OpenVMS DECwindows. Server Options Choose one of the following server options: o MailWorks Local Area Network Server Package This license package is used in customer situations where a LAN with multiple servers is needed for implementing Mail, VAX Message Router is not already owned, MailWorks for OpenVMS will be implemented on a VAX, and it is not necessary to connect to other X.400 messaging prod- ucts. Software Licenses: QP-00PAA-** Software Product Services: QT-YCZA*-** This package includes licenses for MailWorks Server for OpenVMS VAX and VAX Message Router. Media and documentation update service for these components must be purchased separately. Refer to service offerings for MailWorks Server for OpenVMS and to the Software Product Descrip- tion for VAX Message Router (SPD 26.33.xx). o MailWorks Wide Area Network Server Package This package is used in multiserver configurations where there is a requirement to work with another X.400 messaging product and/or VMS- mail. Software Licenses: QL-YFUA*-** Software Product Services: QT-YCZA*-** This package includes licenses for MailWorks Server for OpenVMS, VAX Message Router VMSmail Gateway, and VAX Message Router X.400 Gateway. Media and documentation update services for these components must be purchased separately depending upon which components will be imple- mented. Refer to service offerings for MailWorks Server for OpenVMS, 22 plus one of the two gateway packages: VAX Message Router VMSmail Gate- way (SPD 26.33.xx) or VAX Message Router X.400 Gateway (SPD 28.50.xx). Service on either gateway covers service for the Message Router it- self. Software Media: QA-YFUAA-H* This part number includes media and documentation for MailWorks Server for OpenVMS VAX, VAX Message Router, and VMSmail Gateway. Media and documentation for the VAX Message Router X.400 Gateway must be pur- chased separately. o MailWorks Server for OpenVMS This product implements MailWorks Server on a node, VAXcluster, or Lo- cal Area Network where the VAX Message Router is already licensed, or where it is not necessary to connect to any other node or any other messaging product. Software Licenses: QL-YCZ9*-**, QL-3NG9*-** Software Media: QA-YCZA*-**, QA-3NGAA-H8 Software Documentation: QA-YCZAA-GZ, QA-3NGAA-GZ Software Product Services: QT-YCZA*-**, QT-3NGA*-** Component Options MailWorks for OpenVMS DECwindows Software Licenses: QL-VZ7A*-** Software Media: Included with the server media Software Documentation: QA-VZ7AA-GZ Software Product Services: QT-VZ7A*-** MailWorks for OpenVMS Video Terminals Software Licenses: QL-YHSA*-**, QL-3P9A*-** Software Media: Included with the server media Software Documentation: QA-YHSAA-GZ, QA-3P9AA-GZ 23 Software Product Services: QT-YHSA*-* * 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 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 The OpenVMS layered products support the OpenVMS License Management Facility. The MailWorks Server for OpenVMS is licensed for either un- limited use or for a specific number of concurrrent users on a sin- gle processor. License units for MailWorks for OpenVMS Video Terminals and MailWorks for OpenVMS DECwindows components are licensed for either personal use or for unlimited use on a single processor. The MailWorks Local and Wide Area Network Server Packages is licensed on a clusterwide power rating basis. For more information on the License Management Facility, refer to the OpenVMS VAX Operating System Software Product Description (SPD 25.01.xx) or the License Management Facility manual of the OpenVMS Operating Sys- tem documentation set. SOFTWARE PRODUCT SERVICES A variety of service options are available from Digital. For more in- formation, contact your local Digital office. 24 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] IBM and PROFS are registered trademarks of International Busi- ness Machines Corporation. [R] KEYpak is a registered trademark of Keyword Office Technolo- gies, Ltd. [R] Microsoft is a registered trademarks of Microsoft Corporation. [R] MultiNet is a registered trademark of TGV, Inc. [TM]Apple and Macintosh are trademarks of Apple Computer, Inc. [TM]Windows is a trademark of Microsoft Corporation. [TM]The DIGITAL Logo, ALL-IN-1, AXP, CI, DEC, DECnet, DECwindows logo, Digital, DX, CDA, DDIF, MAILbus, MAILworks, MicroVAX, OpenVMS, PATHWORKS, TeamLinks, TK, VAX, VAXcluster, VAXft, VAXserver, VAXstation, and WPS-PLUS are trademarks of Digital Equipment Corporation. [TM]cc:Mail is a Trademark of cc:Mail, Inc., a wholly owned sub- sidiary of Lotus Development Corporation. 25