DIGITAL Software Product Description ___________________________________________________________________ PRODUCT NAME: MailWorks for UNIX, SPD 45.16.07 Version 2.0 DESCRIPTION The MailWorks for UNIX server provides a way to tie many dissimilar desktops together both within the workgroup and beyond. Users of Mac- intosh, Microsoft Windows, and UNIX Motif clients and others partic- ipate as peers in an integrated workgroup that may be distributed across wide geographic areas. UNIX environments always contain some amount of UNIX mail and connec- tion to the Internet. In addition, many environments are connecting via X.400 protocols, both within an enterprise and with customers, sup- pliers, and research colleagues. MailWorks exchanges messages via multiple messaging protocols. The server itself exchanges messages among the users of the server. It also posts and fetches via sendmail in the TCP/IP environment, or optionally via X.400 protocols in the DECnet/OSI environment. MailWorks is shipped with the MailWorks Client for Digital UNIX, a client built on the Motif standard. Digital supplied clients with which the MailWorks for UNIX server works are available on a separate Mail Client CD-ROM. Client choices include: o TeamLinks Mail client for Windows o TeamLinks Mail client for Macintosh o MailWorks Motif Client for Digital UNIX (included with MailWorks for UNIX) September 1996 AE-Q4MAF-TH o MailWorks Motif Client for SunOS and Solaris o MailWorks for DOS o Microsoft Mail as a client, via the Digital Driver for Microsoft Mail o cc:Mail as a client, via the Digital Driver for cc:Mail o Microsoft Exchange as a client, via the Digital Driver for MAPI o In addition to the Digital supplied clients or drivers, MailWorks for UNIX supports many POP3-based mail clients. For X.400 connection, a MAILbus 400 Message Transfer Agent may be added. Refer to the OPTIONAL SOFTWARE section for more information. Key characteristics of this multiprotocol server include: o The customer has a choice of clients, both from Digital and from other sources, which connect to and utilize the services of Mail- Works. o Users of Motif, Windows, Macintosh and DOS devices can share the same server and the same set of services. o A given user can move from one of these desktop devices to another, using any one to connect to the same server files. For example, a user who has a Motif device in the office may have a Windows lap- top on the road. o MailWorks for UNIX provides performance, flexibility, and low ad- ministrative overhead for workgroups on local area networks (LANs). o MailWorks for UNIX allows users to exchange the kinds of informa- tion they work with daily, including spreadsheets, documents, and scanned images. o MailWorks for UNIX can be extended to include new kinds of enclo- sures. o MailWorks will work on systems that implement C2 security. Mail- Works itself will not enforce discretionary access controls, but will operate properly in a C2 security environment. 2 o Users may send and receive messages via sendmail/SMTP, as well as via MAILbus 400 Message Transfer Agent and X.400. o MailWorks will decode received messages that have been encoded in MIME and will store these messages in decoded form so that non-MIME aware clients will be able to read the messages and attachments. Messages sent via SMTP may be optionally encoded in MIME. MailWorks for UNIX meets the needs of users through the following fea- tures: o Implementation of standards: - X Window System - X.400 electronic messaging standard - Internet electronic messaging standards (RFCs) o Performance and flexibility for LAN-based workgroups: - Easy to integrate with existing UNIX mail systems - Variety of configurations through client/server architecture - Cost effective administration - Group databases (bulletin boards) for sharing messages among groups - Access control for personal and group databases - Flexible configuration of local or remote Message Transfer Agent or X.500 Directory Service Agent - Local delivery of messages addressed to local recipients using either X.400 or SMTP o Management of large volumes of messages: - Message stores for receipt and storage of messages - Hierarchical folders for filing mail - Cross-indexing of messages - Query facility for retrieving messages 3 o Integration of multiple media through multipart messages, which may contain: - Spreadsheets - Scanned images - Documents - Voice files - Video files Services Provided by the Server MailWorks for UNIX uses a client/server architecture, which separates the desktop software for creating and reading messages (client) from the facility that posts, fetches, and stores the messages themselves (server). The client sends and receives messages and interacts with a message store on behalf of a user. Clients with which the MailWorks for UNIX server works are based on the OSF/Motif Graphical User Interface (GUI), Microsoft Windows, and Macintosh user interfaces. MailWorks for UNIX includes the following services: o Message store server The message store server receives incoming messages, and stores and manages them efficiently in message stores, or "drawers." A mes- sage store can be a personal message store, which stores messages for an individual user, or a group message store, which stores mes- sages to be shared by a group of users. A user's message store can be temporarily disabled to allow back- ups, or to allow the message store to be moved. While a message store is disabled, the user cannot connect to it, and incoming mail can- not be delivered. Because message stores are disabled on a user- by-user basis, it is possible to disable a set of users to do backup of one disk, without disabling the entire mail system. o POP3 Server 4 The POP3 server allows POP3-based clients (such as Eudora, Netscape Navigator) to retrieve received mail. The POP3 server allows read- ers to retrieve mail that was received from other local users, re- mote SMTP users, or remote X.400 users. o Transport service The transport service delivers messages on the LAN and across wide- area networks with the Internet or X.400 transport interfaces. The transport service delivers messages that are addressed to local MailWorks for UNIX users directly to the appropriate message store. It gives other messages to either the Internet or X.400 transport interfaces, depending on the mail address. o Message store registry The message store registry tracks the location of message stores across a local area network, so the user agent can access any mes- sage store. To ease administration, the registry also stores aliases and distribution lists so all users on a LAN can use the same names when sending mail. o Internet mail transport interface The Internet mail transport interface sends messages to and receives messages from sendmail and SMTP. This transport delivers outgoing mail to the sendmail or mmdf transport agents. The sendmail or mmdf transport agents deliver incoming mail to a MailWorks for UNIX pro- gram that invokes the MailWorks for UNIX transport service. o MAIL-11 mail exchange MailWorks for UNIX can be configured to exchange messages with Open- VMS mail and other products based on the MAIL-11 protocol. The setup utility in DECnet/OSI can be used to configure sendmail with a MAIL- 11 mailer, or Digital TCP/IP Service for OpenVMS can be used on the target VAX system. o X.400 mail transport interface 5 The X.400 mail transport interface sends messages to and receives messages from X.400 networks through the MailWorks for UNIX server via the XAPI Application Interface to a standards-compliant Mes- sage Transfer Agent (MTA) such as the Digital MAILbus 400 Message Transfer Agent. o sendmail Aliases Messages may be addressed to a valid sendmail Alias, which in turn may be a single user or a distribution list. Maintenance of the send- mail Alias table is outside the scope of this product. o Directory access MailWorks for UNIX provides consistent directory lookup services to all of the supported clients. These directory services include a LAN-based directory listing and support for the optional DEC X.500 Directory Service. In the case of the Microsoft Mail Client, the cc:Mail Client, and the Microsoft Exchange Client, this expanded consistent support is an extension of the client features provided via the MailWorks for UNIX server. The LAN-based and X.500 directory services are provided via the In- foBroker Directory Assistant Server, which is bundled with Mail- Works for UNIX. If the DEC X.500 Directory Service has been pur- chased and implemented, the X.500 directory is checked instead of the LAN-based directory. Message Stores and Bulletin Boards In general, each user on a LAN has a single personal message store for storing their own messages. If users assume more than one role in an organization, such as system administrator and end user, they can use a separate message store for each role. Groups of users, such as project teams or special interest groups, can set up group message stores instead of distribution lists. Group mes- sage stores can be accessed by more than one user at a time, and can 6 serve as bulletin boards or forums for discussion. Group message stores offer the following advantages: o They ensure that all members of a group see the same messages. o They can track read and unread messages for each member of the group. o They keep a common, historical record of all messages. o They use much less disk space and network bandwidth because sep- arate copies are not distributed to and stored by each member of the group. Message Management This section describes what services MailWorks for UNIX provides to the MailWorks Motif Client for Digital UNIX. The capabilities of other client interfaces may vary slightly. See the client capabilities sec- tion of each client SPD to determine what features the client has im- plemented. Because the volume of message traffic is growing rapidly for the av- erage mail user, the MailWorks Motif Client for Digital UNIX provides an intuitive, flexible, and efficient way for users to manage the mes- sages in their message stores. These message management features in- clude the following: o Hierarchical folders for filing mail Each message store provides an In Box folder for receiving incom- ing mail, an Out Box folder for saving (automatically) a copy of all outgoing mail, and a Trash folder for removing messages. To delete messages, users move them to the Trash folder. Messages can be re- trieved from the Trash folder until the user empties the Trash folder. In addition, users can create new folders and subfolders to store messages. o Cross-indexing of folders When a user files a message in multiple folders, MailWorks Server for UNIX creates "virtual copies" of the message to conserve disk 7 space. MailWorks for UNIX keeps one real copy of the message and cross-indexes that copy to the other folders. When the user makes a change to one copy of the message, that change appears on all copies. o Query facility to retrieve messages With the query facility, users can quickly search the folder hi- erarchy to retrieve messages that satisfy a set of fields. Users can specify a subject, sender, recipients, range of dates, keywords, and text from the message body. As a result of the query, MailWorks for UNIX places virtual copies of all messages satisfying the query in a temporary folder, which can then be sorted. Access Control Access Control services are implemented on the server, and are there- fore available to all connected clients. The actual user interface ca- pabilities may vary slightly from one client implementation to another. MailWorks for UNIX provides access control for setting permissions on each message store. In MailWorks, access control applies a set of five different permissions to three different classes of users. MailWorks for UNIX uses the same classes of users as the UNIX access control model: user, group, and other. MailWorks for UNIX provides the following per- missions: o Deliver Permits a user to deliver new mail to a message store. Most mes- sage stores grant delivery access to others, so the user or group can receive messages from outside the LAN. In some situations, how- ever, it is appropriate to restrict delivery access. For example, a group can choose to grant delivery access only to itself, or an executive can limit delivery access to a secretary so messages can be screened. o Read Permits a user to browse the message store and view any message. 8 o View Permits a user to browse the message store and have it monitor which messages are read and unread. Because the read and unread data takes up a small amount of disk space, most group message stores of a mod- est size grant monitor access to all members of the group. For larger groups, restricting monitor access can reduce disk space. o Write Permits a user to create, delete, or move messages and folders in the message store. o Administer Permits a user to change the access rights of the message store. Typically, only the owner (user) of a message store is granted ad- ministrative access. Multipart Messages With MailWorks for UNIX and its clients, users can compose and receive messages that consist of multiple parts known as enclosures, attach- ments, or "bodyparts." Each attachment is typed according to the kind of information it contains. For example, a single message can consist of text, a fax, and a spreadsheet. Users or administrators can con- figure and extend the attachment types available at a site. Recipients using the Motif client can view all enclosed parts of a mes- sage at the same time through predefined tools for each attachment type and multiple MailWorks for UNIX windows and panes in each window. In addition, any attachment can be exported to and imported from the UNIX file system. 9 Configurations MailWorks for UNIX can be tailored easily to support any site's con- figuration because of its client/server architecture, and its abil- ity to use remotely accessed message stores, remote MAILbus 400 MTA, and remote X.500 Directory Service Agents. Because the MailWorks server consists of a number of different indi- vidual processes, those processes may be run on a single system, or distributed across a number of systems in the network. As an example, it is possible to run message store servers on several systems in a LAN with a common message store registry on one system-this provides the scaleability of multiple systems, while at the same time supports local delivery and simplified addressing for all users sharing the com- mon message store registry. UNIX Mail Configurations MailWorks for UNIX integrates easily into existing UNIX mail systems. MailWorks for UNIX supports three basic types of UNIX mail configu- rations: o MailWorks for UNIX interworking directly with Internet users. o MailWorks for UNIX interworking directly with Internet users and also with MAILbus 400. One message may be sent to two addresses, one via sendmail and one via X.400. The sendmail address for the MailWorks user is a normal sendmail address. o MailWorks for UNIX connecting only with MAILbus 400, and interwork- ing with Internet users via the MAILbus 400 SMTP Gateway. One mes- sage may be sent to two addresses, one via sendmail and one via X.400. The sendmail address for the MailWorks user is to the SMTP Gate- way node, resolved in X.500 to forward the message to MailWorks. In environments where the majority of other users are using products based on sendmail, the first or second scenarios would be preferable. In environments where X.500 is fully deployed or where the topology or enterprise prefers centralized administration of sendmail connec- tion, the third scenario would be preferred. 10 Client/Server Protocols Supported Clients may connect to the Server over the LAN via TCP/IP or (option- ally) DECnet. See the client capabilities section of the Mail Client SPD to determine which protocol the client supports for server con- nection. Dial-In Support The MailWorks for UNIX server supports client access via TCP/IP, TCP, SLIP, or PPP. See the client capabilities section of each client SPD to determine whether the client can attach remotely to the server via one of these protocols. Standards Supported MailWorks for UNIX adheres to the following standards: o X Window System o X.400 electronic messaging standard o Internet electronic messaging standards (RFCs) When sending via X.400, messages are structured as 1988 P1 messages, with P2 header information, and with attachments as X.400 Bodypart 15. If necessary, the MAILbus 400 Message Transfer Agent can modify the message structure when exchanging messages with 1984 P1 systems, to pass the message as a 1984 P1 message with untagged binary attachments, or as a 1984 P1 message with Nationally Defined bodypart 310 for ex- change of tagged attachments with Digital's Message Router. See the MAILbus 400 documentation for implementation considerations. SMTP messages can be run through the uudecode process and restructured as Bodypart 15 messages with appropriate tags. 11 Internet Standards Conformance o RFC 791, Internet Protocol o RFC 793, Transmission Control Protocol o RFC 821, Simple Mail Transfer Protocol o RFC 822, Standard for the format of ARPA Internet text messages o RFC 1006, ISO transport services on top of TCP o RFC 1034, Domain names - concepts and facilities o RFC 1035, Domain names - implementation and specification o RFC 1101, DNS encoding of network names and other types o RFC 1327, Mapping between X.400 (1988)/ISO 10021 and RFC 822 o RFC 1487, X.500 Lightweight Directory Access Protocol o RFC 1521, Multipurpose Internet Mail Extensions (MIME) (part 1) o RFC 1522, Multipurpose Internet Mail Extensions (MIME) (part 2) o RFC 1725, Post Office Protocol (POP3) X.400 Standards Conformance These products are designed to conform to the 1988 joint CCITT and ISO Messaging Handling System Standards P1, P2, and P22: o 1988 joint CCITT and ISO Message Handling System (MHS) standards, together with the errata published in the ISO Technical Corrigenda 1-4 and the CCITT Implementor's Guide V8.0 (1993) o CEN/CENELEC profile ENV 41214 o MHS Chapters (7 and 8) of the Stable Implementation Agreement for OSI protocols (Version 5, Edition 1, December 1991), produced by the OSI Implementor's workshop o US GOSIP V1.0 o US GOSIP V2.0 12 o U.K. GOSIP V4.1 o CEN/CENELEC ENV 41 201 (profile (A/3211) for private domains) o CEN/CENELEC ENV 41 202 (profile (A/311) for administration domains) o X.400 API Association, Directory Services API Specification (XDS) V2.0 o X.400 API Association, X.400 API Specification (XAPI) V3.0 These profiles are not uniform and where differences exist, the prod- uct follows the NIST profile. Some restrictions on the level of ser- vice obtained between message originator and recipient may apply if all the systems involved in the message transfer do not conform to the X.400 recommendations. Contact your local Digital office for information on the conformance status, test reports, and registration. MailWorks Motif Client for Digital UNIX The MailWorks Motif Client for Digital UNIX is available for systems running Digital UNIX, SunOS, and Solaris. The MailWorks Motif Client for Digital UNIX is the only client shipped on CD-ROM #2, along with the server. The Motif Clients for SunOS and Solaris are available on CD-ROM #1. See Ordering Information for more details. The MailWorks Motif Client features an intuitive interface that ad- dresses the needs of a broad range of users, regardless of their tech- nical sophistication. The MailWorks Motif Client provides separate win- dows for composing and reading mail, so users can work on several dif- ferent tasks simultaneously. In addition, the MailWorks Motif Client provides dialogs for composing mail addresses, managing folder hier- archies, and querying folders-tasks that are usually difficult in tra- ditional mail systems. When users need information, they can access online help from any window or dialog. 13 MailWorks Motif Client for Digital UNIX uses the following types of windows: o Composition windows Users can compose new messages, reply to messages, and forward mes- sages. o Browser windows Users can read, locate, and manage messages and folders. o View windows Users can display the contents of individual messages and folders in a separate window from the browser window. All windows share the same menus, allowing the user to access all ap- plicable operations from all windows. Most menu items apply to all win- dows; those that do not apply to a particular window are grayed out. The MailWorks Motif Client uses dialogs for guiding users through tasks and displaying error messages. Most dialogs are nonmodal, so users can continue working in other windows or dialogs while the dialog is dis- played. To compose a message, users enter text into the headers and the first message attachment. If they desire, users can add headers or additional attachments to the message. To edit a new attachment, users select the Edit button in the pane for the attachment. (Users can select a pre- ferred editor for each attachment type, as discussed in the "Exten- sibility" section.) To post the message, the user selects Post from the Messages menu. When a user reads a message, the heading and message body appear in the lower panes of the browser window. The message displayed may con- tain multiple parts. Because some attachments can be read only in sep- arate windows, the browser window indicates the attachment type and provides a view button in the pane for the attachment. 14 To help users navigate the folder hierarchy and file selected messages in appropriate folders, MailWorks Motif Client provides a folder browser dialog. This dialog displays three levels of the folder hierarchy at a time. Users move down the hierarchy by selecting folders in the mid- dle and right panes, and move up the hierarchy by selecting the left arrow button and folders in the left pane. Users can move or copy se- lected messages into the selected folder with either the Move or Copy buttons. To help users construct and understand complex mail addresses, the Mail- Works Motif Client for Digital UNIX provides address composition di- alogs for the following forms of addresses: Internet, UUCP, X.400, and local recipients. Other X11 Display Devices Other X11 display devices may be used in conjunction with this client, as long as the client software is being executed on a Digital UNIX de- vice. Valid X11 display devices include Digital's eXcursion for PC. Standards Compliance The MailWorks Motif Client for Digital UNIX is designed to adhere to the following interface standards: o OSF Motif 1.2 Style Guide o Inter-Client Communications Conventions Manual (ICCCM) o FIPS 158, User Interface Component of the Applications Portabil- ity Profile, standard for well-behaved X Window applications o X11R4 o POSIX 1003.1 Extensibility 15 As the base of UNIX applications broadens with the availability of more standards-based applications, extensibility will play an important role in creating an integrated environment for users. Because the MailWorks for UNIX architecture exploits object-oriented design and complies with emerging standards in internationalization, MailWorks for UNIX can be extended to incorporate new applications. Third parties and end users can extend MailWorks for UNIX by: o Adding new attachment types o Defining viewers, editors, and converters for each attachment type o Adding new clients o Using scripting to develop custom functions For multipart messages that contain attachments (or "bodyparts") of different types, each attachment type has an associated ISO object- id that identifies the kind of data in it. Each instance of an attach- ment type stores a copy of this ISO object-id. If desired, third par- ties can add attachment types to MailWorks for UNIX by editing a con- figuration file and adding the new object-id and associated informa- tion. The MailWorks Motif Client for Digital UNIX uses the object-id to se- lect an applicable viewer, editor, or converter for processing the at- tachment: o Viewer Reads or views an attachment. o Editor Creates a new attachment or modifies an existing one. Examples of editors are vi and emacs for text, FrameMaker for documents, and WingZ for spreadsheets. o Converter 16 Changes the type and internal representation of an attachment. For example, a converter can convert an attachment into a different for- mat, so it can be edited with a different editor. If there is no viewer for a particular attachment type, but there is a converter available to transform that type to another preferred type, converters can also be implemented to perform those transformations on behalf of the user. MailWorks for UNIX supports a series of mh-style command-line commands. These may be used directly by command-line users, or the user can de- velop shell scripts that use these commands to perform more complex functions. Local Language Support The MailWorks Motif Client for Digital UNIX can be localized to use different local languages because it is built on the following stan- dards: o X/Open message catalogs, which keep all text strings separate from executables and get loaded at run time MailWorks Motif Client for Digital UNIX is built on the following ad- ditional standards: o OSF/Motif compound strings, which support display of arbitrary char- acter sets o OSF/Motif standard widget set HARDWARE REQUIREMENTS The following processors are supported. 17 Enterprise DEC/4610,4620,4710,4720 DEC/7610,7620,7630,7640,7700 DEC/10610,10620,10630,10640 AlphaServer 8200 Uni AlphaServer 8400 Dual AlphaServer 8200 Dual AlphaServer 8400 Uni Departmental DEC/3500,3500S,3500X,3800,3800S,3900 AlphaServer 2000 4/200,2100 4/275,2100 4/200 Workgroup DEC/2300S,2500 DEC/3300,3300L,3300X,3300LX,3400,3400S, 3600,600S,3700 AlphaStation 200 4/100, 200 4/166, 200 4/233, 250 4/266,400 4/233 AlphaServer 1000 4/200 AXPpci 33 AXPvme Reference can be made to the configuration charts listed in the Dig- ital UNIX Operating System Software Product Description (SPD 41.61.xx). 18 Disk Space Requirements MailWorks for UNIX requires the following amount of permanent disk space: o /usr file system - 60 MB o /var file system - 1 MB In addition to the above, disk space must be available for users' mes- sage stores. Finally, sufficient swap space must be available. Depending on the num- ber of users and how they use the system, the demands on swap space can be significant. Memory Requirements for Motif Support The minimum supported memory for this application running in a stan- dalone Motif environment with both the client and server executing on that same system is 64 MB. The performance and memory usage of Motif applications are particu- larly sensitive to system configuration. Less memory may be required on the client system (the system where the software is installed and executed) if the server (the component that displays the application) resides on another system. More memory may be required on a system with several applications running or may be desirable to improve the per- formance of an application. Memory Requirements for Server Support The minimum memory supported is 64 MB. However, the use of this soft- ware in conjunction with increased memory capability improves perfor- mance. The memory size suggested for most typical hardware configu- rations is 1/2 to 1 MB per user, depending on usage levels and pat- terns. With sufficient memory and disk space MailWorks for UNIX is certified for use for 250 concurrent users per cpu, which generally supports ap- proximately 1000 registered users. 19 SOFTWARE REQUIREMENTS For MailWorks for UNIX and MailWorks Motif Client for Digital UNIX: o Digital UNIX Operating System V3.2c o InfoBroker V2.1A (license included with MailWorks for UNIX) o X.500 Directory Server subset DXBASE200 (X.500 Directory Server li- cense not required) o DECnet subset DNARFC1006 (DECnet license not required) o DECnet subset DNANETMAN (DECnet license not required) For connection to MAILbus 400 Message Transfer Agent and X.400 des- tinations: o DECnet/OSI V3.0 for DEC OSF/1 AXP 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 Shrinkwrap packages are available that include license(s), media, and documentation. These packages always include one server license and 2 CD-ROMs containing the MailWorks for UNIX Server and Mail Clients. CD-ROM #1 contains clients for: o TeamLinks Mail V2.7 for Windows o TeamLinks Mail V2.5 for Macintosh o Digital Driver V1.2 for cc:Mail o Digital Driver V1.5 for MS-Mail o Digital Driver V1.2 for MAPI 20 o MailWorks Motif Client V2.0 for Sun/OS and Solaris o Documentation for the above-named clients CD-ROM #2 contains software for: o MailWorks for UNIX Server o MailWorks Motif Client V2.0 for Digital UNIX (the only client on this CD-ROM) o InfoBroker prerequisite components o The MailWorks for UNIX Installation and MailWorks for UNIX Release Notes o MailWorks V2.0 for UNIX Software Product Description (SPD 45.16.07) MailWorks for UNIX and the MailWorks Motif Client for Digital UNIX are also available as part of the Digital UNIX Alpha Software Library Pack- age on CD-ROM (order number QA-054AA-H8) for service customers. New customers and customers not on service must purchase one of the Mail- Works V2.0 for UNIX shrinkwrap packages. The software documentation for MailWorks for UNIX is also available as part of the Digital UNIX Alpha Online Documentation Library on CD-ROM (order number QA-4KP8A-G8). The software documentation for the products on the Mail Client CD-ROM are available separately as well. See the individual Client SPD for ordering information. ORDERING INFORMATION You need to order: o A Server License o One Client Access License per individual 21 The Server Software Package listed below includes the server software; the client software; the server license; the client access license for 25,100, or 500; and the associated documentation: Server Software Package: QB-0PC**-S* These items can be ordered individually as well: Server Software License: QM-0PC**-AA Server Software Documentation: QA-0PCAA-GZ Server Software Product Services: QT-0PCA*-** Client Access License: QM-5HMAA-A* * Denotes variant fields. For additional information on available li- censes, services, and media, refer to the appropriate price book. OPTIONAL SOFTWARE This section describes optional software that may be added to Mail- Works for UNIX. Client Choices o MailWorks Motif Client for SunOS and Solaris o Various POP3 clients, such as Eudora and Netscape Navigator o TeamLinks Mail for Microsoft Windows, SPD 55.49.xx o TeamLinks Mail for Macintosh, SPD 39.62.xx o Digital Driver for cc:Mail, SPD 56.15.xx o Digital Driver for MAPI, SPD 64.33.xx o Digital Driver for Microsoft Mail SPD 55.71.xx o DEC TCP/IP Services for OpenVMS VAX, SPD 25.A4.xx; or DEC TCP/IP Services for OpenVMS AXP, SPD 46.46.xx 22 These may be used optionally to receive SMTP messages from Mail- Works for UNIX via sendmail. Alternatively, DECnet/OSI on Digital UNIX may be configured to add a MAIL-11 mailer to sendmail. Optional Additional Services o MAILbus 400 Message Transfer Agent, SPD 46.89.xx, required for mes- sage transfer via X.400 protocols. May be accessed remotely. o DEC X.500 Directory Service, SPD 40.77.xx. May be accessed remotely. o MAILbus 400 SMTP Gateway, SPD 46.91.xx. May be used where central- ized administration of Internet connection is preferred. SOFTWARE LICENSING With MailWorks V2.0 for UNIX a switch is being made from "standard" licensing to PC-style (shrinkwrap) licensing with a Server/CAL approach. See below for a description of these licenses. Initial Licenses: You are required to purchase a MailWorks Server License to install, tune, and test both the Server Software and the Client Software. Each Server License permits you to install the Server Software on a sin- gle server, and install the Client Software on any number of client computers that are connected to the computer on which the Server Soft- ware resides. You are required to purchase a MailWorks Client Access License (CAL) for each individual that has access to the Server Software, whether Digital or third-party client software is used on the client comput- ers. Upgrade Licenses: A license for a prior version of MailWorks for UNIX is a prerequisite for the purchase of any of the upgrade offers. 23 The Upgrade Server License provides the same rights as the initial Server License (see above). The Upgrade Client Access License provides the same rights as the initial Client Access License (also above). EXISTING CLIENT QUALIFIES FOR THIS SOFTWARE LI- NUMBER OF UPGRADE CALs CENSE Traditional 25 Concurrent Use 1 Personal Use 1 SOFTWARE PRODUCT SERVICES A variety of service options are available from Digital. DECstart Ser- vice is recommended for every new customer. For more information, con- tact 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 to this SPD. Warranty Limitations Achievement of the full level of messaging services specified in the CCITT 1988 X.400 Recommendations is possible only if all systems in- volved in the origination, transfer, and delivery of a message con- form to those X.400 recommendations. Absolute fidelity between an original document and the resulting doc- ument as printed or displayed by the receiving system is not guaran- teed. The differences between vendors' approaches to word processing systems, the transformations required for the transfer and printing of a document, and the types of printers used may all affect the re- sulting printed document. The above information is valid at time of release. Please contact your local Digital office for the most up-to-date information. 24 TRADEMARKS [TM] cc:Mail is a trademark of cc:Mail, Inc., a subsidiary of Lotus Development Corporation. . FrameMaker is a registered trademark of Frame Technology Corporation. . Macintosh is a registered trademark of Apple Computer, Inc. [TM] Netscape Navigator is a trademark of Netscape Communications Corp. . Microsoft, Microsoft Mail, MS-DOS, Windows, Windows 95, and Microsoft Exchange Server are trademarks or registered trade- marks of Microsoft Corporation. . Motif, OSF/1, and OSF/Motif are registered trademarks of the Open Software Foundation. . POSIX is a registered trademark of Institute of Electrical and Electronics. [TM] SunOS is a trademark of, and Solaris is a registered trade- mark of Sun Microsystems Inc. . UNIX is a registered trademark in the United States and other countries, licensed exclusively through X/Open Company Ltd. . WingZ is a registered trademark of Informix Software, Inc. [TM] X/Open is a trademark of X/Open Company Limited. [TM] X Window System is a trademark of the Massachusetts Institute of Technology. [TM] The DIGITAL logo, Alpha AXP, AlphaServer, AlphaStation, AXP, DEC, DECnet, DECstart, eXcursion, MAILbus, MailWorks, Open- VMS, TeamLinks, and VAX are trademarks of Digital Equipment Corporation. ©1996 Digital Equipment Corporation. All rights reserved. 25