CONTENTS Title Page Copyright Page 1 Introduction to MRX V2.3 2 Upgrading from Earlier Versions 3 Prerequisite Software 4 New Features in MRX V2.3 4.1 Running MRX 4.2 Storing Message Files 4.3 Keeping Processed Message Files 4.4 Using MRXTBED to Transfer Message Files 4.5 Validating O/R Names in Outbound Messages 4.6 Setting the Maximum Number of MTA Connections 4.7 Converting Outbound RMS Files to Binary Bodyparts 4.8 Converting Outgoing Bodyparts into ISO6937 4.9 Running the MRX Installation Verification Procedure 4.10 Updated Country Codes 4.11 Default Setting of /ORGUNIT_V21_IMPL Changed 4.12 Displaying MRXMAN Information 4.13 Using O/R Names Without Organization Name Attributes when Orgunit Routing is Enabled 5 Functional Improvements 5.1 Creating Freeform Names for P2 Recipients 5.2 Suppressing the Creation of ALL-IN-1 Service Messages 5.3 Preventing Interworking Problems with GOSIP Conformant MTAs 5.4 Preventing Service Messages Transferred to MRX from MRS Looping 5.5 Translating Teletext Messages 5.6 Converting WPS-PLUS Messages 5.7 Delivering Looping Messages to Local Recipients 5.8 Translating Messages That Include Domain-Defined Attributes in NBS O/R Names 5.9 Recording Originator Information for Outbound NBS Relayed Messages 5.10 Using Form 1.1 O/R Names That Consist of Country, Administration Domain, and Domain-Defined Attributes 5.11 Using Mixed-Case Characters in Organization Name and Organizational Unit Attributes 5.12 Replying to Recipients in Other Domains 5.13 Including Telephone Numbers in P2 O/R Descriptors 5.14 Processing Inbound ODIF Documents 5.15 Reallocating Aborted Sessions 5.16 Establishing Session Connections 6 Documentation for MRX V2.3 6.1 Returning Comments on the Documentation 6.2 Message Router X.400 Gateway Version Number 7 Restrictions and Documentation Error on MRX V2.3 7.1 Incorrect Version of ODA CDA Gateway Described in VAX Message Router X.400 Gateway Installation Guide 7.2 Using the Generic Mailbox on DECnet/OSI V5.6B 7.3 Using the OSAK Trace Facility 7.4 Messages That Cannot Be Translated Cause MRX to Stop 7.5 MRX Stops if a Device Containing an Enabled Message Directory Becomes Unavailable 7.6 MRXMAN SHOW AREA /OUTPUT Command Only Writes to Files in the Default Directory 7.7 Restrictions on the /VALIDATE_OUTB_ORNAME Parameter 7.7.1 MRX Rejects Messages with Surplus Personal Name Attributes and No Surname 7.7.2 MRX Occasionally Discards Returned Content from Service Messages 7.7.3 Problems with Replying to Messages When the /VALIDATE_OUTB_ORNAME Parameter is Set to ON or AMEND 7.8 MRX Rejects Outbound Messages with Null Attributes in the To: Field Syntax 7.9 MRX Supports a Maximum of Sixteen Levels of Nested Forwarded Messages 7.10 Messages Addressed with Form 2 O/R Names Cannot Be Relayed 7.11 Incorrect Error Message for Form 2 O/R Names 7.12 Failed Session Connections Are Not Re-Enabled when a Message Arrives from a Peer MTA 7.13 MRXMAN TEST Command Causes Error 7.14 MRX Holds Locks on BAD Files 7.15 Missing MTRACE Information Causes Invalid Non-Delivery Notification 7.16 Incorrect Error Message for Ambiguous Recipient 7.17 Error Message from the CVP on a Cluster Repeated