MAILbus 400 Message Store ------------------------------ Release Notes for Digital UNIX Revision/Update Information: Version 1.2 Digital Equipment Corporation Maynard, Massachusetts __________________________________________________________ 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. Possession, use, or copying of the software described in this publication is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. No responsibility is assumed for the use or reliability of software on equipment that is not supplied by Digital Equipment Corporation or its affiliated companies. © Digital Equipment Corporation 1994, 1996. All Rights Reserved. The following are trademarks of Digital Equipment Corporation: DEC, DECnet, Digital, MAILbus, MAILbus 400, PATHWORKS, VAX, VAX DOCUMENT, and the DIGITAL logo. ISOCOR and ISOPRO are trademarks of ISOCOR. MailmaX.400 and MaXware are trademarks of MaXware. Microsoft is a registered trademark of Microsoft Corporation. EXM Mail is a trademark of Enterprise Solutions Limited. Open Software Foundation is a trademark of Open Software Foundation, Inc. OSI is a registered trademark of CA Management, Inc. Route 400 and NET-TEL are trademarks of NET-TEL Computer Systems Limited. UNIX is a registered trademark in the United States and other countries licensed exclusively through X/Open Company Ltd. X/Open is a trademark of the X/Open Company Limited. Windows is a trademark of Microsoft Corporation. This document was prepared using VAX DOCUMENT, Version 2.1. ________________________________________________________________ Contents 1 Introduction.................................... 1 2 Documentation Provided with the MAILbus 400 Message Store Version 1.2....................... 1 3 New Functionality in the MAILbus 400 Message Store Version 1.2............................... 2 4 Interworking with User Agents .................. 3 4.1 Ensuring that EXM Mail Can Contact the Message Store over TCP/IP on PATHWORKS................ 3 4.2 Increasing the Buffer Size When Using a User Agent Over TCP/IP............................. 3 5 Restrictions Lifted Since the MAILbus 400 Message Store Version 1.1....................... 4 5.1 Limit on the Length of a Message Store User's O/R Address................................... 4 5.2 Extended Wildcard Support for Message Store Entities...................................... 4 6 Restrictions in Other Products that Can Affect the Message Store .............................. 4 6.1 User Password Stored with O/R Address Entry Must Be Printable String...................... 5 7 Restrictions in the MAILbus 400 Message Store... 5 7.1 Setup Always Generates New Agent Entity Script........................................ 5 7.2 Some Events Issued as Part of Normal Operation..................................... 6 7.3 Entry Entities Created for Subordinate Entries Do Not Contain Message Identifier............. 6 7.4 Supported Bodyparts .......................... 7 iii 1 Introduction The MAILbus 400[TM] Message Store for Digital[TM] UNIX[R], Version 1.2 provides X.400 message storage and submission services to User Agents. It conforms to CCITT Recommendation X.413 and International Standard ISO/IEC 10021-5. It allows you to run multiple Message Stores on one node. The MAILbus 400 Message Store Version 1.2 is designed to be used with the MAILbus 400 MTA for Digital UNIX, Version 1.4A or later, and uses the MTA's routing information in the Digital X.500 Directory Service to store information about its users. These Release Notes describe: o The documentation provided with the MAILbus 400 Message Store Version 1.2 (see Section 2) o New functionality in the MAILbus 400 Message Store Version 1.2 (see Section 3) o Information about interworking with User Agents (see Section 4) o Restrictions that have been lifted since the MAILbus 400 Message Store Version 1.1 (see Section 5) o Restrictions in other products that can affect the MAILbus 400 Message Store (see Section 6) o Restrictions in the MAILbus 400 Message Store (see Section 7) 2 Documentation Provided with the MAILbus 400 Message Store Version 1.2 The documentation comprises: o MAILbus 400 Message Store Managing (Version 1.2) o MAILbus 400 Message Store Installing on a Digital UNIX System (Version 1.2) o MAILbus 400 Message Store Release Notes for Digital UNIX (Version 1.2 - this document) 1 o MAILbus 400 Message Store for Digital UNIX Software Product Description (Version 1.2) In addition, reference information is available in the Message Store Module Online Help. 3 New Functionality in the MAILbus 400 Message Store Version 1.2 The MAILbus 400 Message Store Version 1.2 offers the following new functionality: o Extended NCL management Management of the Message Store entity and its subentities has been extended as follows: - The Message Store entity has several new counters, which cover normal Message Store activity, and not just error situations. - Message Store Accounting can now be switched on and off. - The User entity has two new status attributes: Information Base Size and Database Occupancy. - There is a new Association entity, which is automatically created when a Message Store user connects, and deleted when the user disconnects. This entity allows you to see who is currently connected to the Message Store. Refer to the Message Store documentation and Online Help for details of new Message Store NCL management. o Performance improvements Submission, retrieval, and delivery operations have been modified to increase the overall performance of the Message Store. Improvements have also been made to the startup time of the Message Store. Message Stores which hold a large number of entries will benefit most from these improvements. o Database improvements 2 The database is now more efficient in its use of disk space. Version 1.1 Message Store databases must be upgraded to the Version 1.2 format using the xms_setup utility. MAILbus 400 Message Store Managing describes how to upgrade your database. o 1992 Standards conformance The Message Store now conforms to the 1992 Revisions of the CCITT Standards X.411, X.413 and X.420. 4 Interworking with User Agents The MAILbus 400 Message Store has interworked, over X.25 and TCP/IP (RFC 1006), with the following User Agents: o EXM Mail[TM] Version 3.0 from Enterprise Solutions Limited[TM]. o MailmaX.400[TM] for Windows, Version 3.1 Remote User Agent from MaXware[TM] o Route 400 Mail[TM] Version 5.00.04/MS from NET-TEL[TM] Computer Systems Limited o ISOPRO[TM] Remote X.400 Document Transport Client for Microsoft[R] Windows, Version 1.41 from ISOCOR[TM] 4.1 Ensuring that EXM Mail Can Contact the Message Store over TCP/IP on PATHWORKS To connect EXM Mail to the Message Store over TCP/IP on PATHWORKS, ensure that EXM Mail uses Version 1.1 of winsock.dll. 4.2 Increasing the Buffer Size When Using a User Agent Over TCP/IP If you are using a User Agent over TCP/IP and feel that message submission is slow, it is recommended that you investigate increasing the User Agent's buffer size to the maximum TPDU setting possible. 3 5 Restrictions Lifted Since the MAILbus 400 Message Store Version 1.1 This section describes the restrictions that have been lifted since Version 1.1 of the MAILbus 400 Message Store. 5.1 Limit on the Length of a Message Store User's O/R Address The limit on the number of characters that the O/R address of a Message Store user, as stored in the user's User entity, can contain has been raised to 1023 characters, including keywords, equals signs (=), semi-colons (;) etc. 5.2 Extended Wildcard Support for Message Store Entities Wildcard support in NCL management commands has been extended as follows: o SHOW MESSAGE STORE * ALL This command shows all the Message Stores currently created. o SHOW MESSAGE STORE ms_id USER "*" ALL This command shows all the users that belong to the named Message Store. o SHOW MESSAGE STORE ms_id USER oraddress ENTRY * ALL This command shows all the entries that belong to the named user. o SHOW MESSAGE STORE ms_id ASSOCIATION "*" ALL This command shows all the users who have User Agents currently connected to the Message Store. 6 Restrictions in Other Products that Can Affect the Message Store The MAILbus 400 Message Store is layered on DECnet[TM]/OSI[R] for Digital UNIX. Read the release notes provided with DECnet/OSI for Digital UNIX to be aware of any restrictions in DECnet/OSI that might affect the MAILbus 400 Message Store, in particular the restrictions on NCL and OSI Transport. 4 The Message Store should be used with the MAILbus 400 MTA for Digital UNIX, Version 1.4A or later. Read the release notes provided with the MAILbus 400 MTA for Digital UNIX to be aware of restrictions in the MTA that might affect the Message Store. Section 6.1 provides information about an additional restriction in the MAILbus 400 MTA that affects the Message Store. 6.1 User Password Stored with O/R Address Entry Must Be Printable String The user password that a user must quote when connecting a User Agent to the Message Store is held in the Password attribute of the user's ORaddress entity, an entity of the MTS module. The value of the Password attribute of the ORaddress entity must be a printable string. Message Store users can change the user password, and might specify characters that are not part of the printable string character set. If a Message Store user provides a non-printable string password, the Message Store does not accept the password, returns an error to the user, and issues the Authentication Error event. If Message Store users experience problems changing their user passwords, advise them that the user password must consist of printable string characters only. The characters of the printable string character set are described in the Message Store Module Online Help. 7 Restrictions in the MAILbus 400 Message Store The following sections list restrictions in the MAILbus 400 Message Store. 7.1 Setup Always Generates New Agent Entity Script Whenever you run the Message Store setup procedure for an existing Message Store, a new script /var/xms/scripts/create_xms_ms-id_agent_entity.ncl is gen- erated, even if you do not specify any new setup values. In the name of this script, ms-id is the identifier of the Message Store. This script creates and enables the Agent entity that represents the Message Store at the local MTA. The existing Agent entity script is renamed to 5 /var/xms/scripts/create_xms_ms-id_agent_entity.ncl.savn, where n is a number. This may cause problems if you have made modifications to the existing script, for example, added commands to enable Archiving for the Message Store at the MTA. When you have re-run the Message Store setup procedure, ensure that you add any changes that you have made in the existing Agent entity script to the new script, and ensure that the new script is executed at the MTA that this Message Store connects to. 7.2 Some Events Issued as Part of Normal Operation In certain circumstances the Message Store issues an MTA Interface Error event, followed by a Directory Service Error event. These two events, when issued together, can be ignored. These events are issued when the DSA releases the connection that the MAILbus 400 MTA has been maintaining with the DSA on behalf of the Message Store. The DSA releases connections that have not been used for a certain period of time as part of normal operation. The next time the Message Store requires the MTA to access the DSA, a new connection between the MTA and the DSA is established. See MAILbus 400 Message Store Managing for information about the MTA Interface Error event issued by the Message Store, and the MAILbus 400 MTA events that you should monitor. For more information about the Directory Service Error event issued by the MAILbus 400 MTA see MAILbus 400 MTA Tuning and Problem Solving. 7.3 Entry Entities Created for Subordinate Entries Do Not Contain Message Identifier Entry entities that the Message Store creates for subordinate entries do not contain the message identifier of the original message. The Message Identifier attribute in such an Entry entity contains null values. An example of a subordinate entry is the returned content of a non- delivery report. 6 7.4 Supported Bodyparts The Message Store supports the following IPM bodyparts: Bilaterally Defined IA5 Text Encrypted Externally Defined G3Fax G4Class1 Message Mixed-mode Nationally Defined ODA Teletex Videotex Voice If the Message Store detects an unsupported bodypart in a message delivered by the MAILbus 400 MTA, it does not accept the message. The MAILbus 400 MTA will generate a non-delivery report for the message. The Message Store does not support ISO6937 bodyparts. If you expect these bodyparts in your messaging environment, you can set content information at the appropriate level in the directory hierarchy of your users' O/R address entries, so that ISO6937 bodyparts are converted to supported bodyparts, for example IA5 Text bodyparts. The following example shows how to set content information on a user's O/R address entry in the directory to ensure that only IA5 Text bodyparts are delivered for the user: NCL> SET MTS "/MTS=ACME" ORADDRESS - "C=NZ;A=NZ-PTT;P=ACME;O=ACME;OU1=AUCK;CN=Tim Slade" - CONTENT INFORMATION [MAXIMUM CONTENT LENGTH = 1000, - CONTENT TYPES = ("{1 3 12 2 1011 5 5 0 1 2}"), - ENCODED INFORMATION TYPES = ( "{2 6 3 4 2}" )] In this example, the following content information is specified: Maximum content length is 1000 Kilobytes Acceptable content type is Interpersonal messaging 1984 Acceptable encoded information type (EIT) is IA5 Text 7 See MAILbus 400 MTA Tuning and Problem Solving for more information about specifying content information. 8