Operations << >>

Testing X.400 Connections to Foreign Sites

When you finish configuring a connection between Microsoft Exchange Server and a foreign system, you should test it before allowing general message transfer or starting any message-based services.

  1. Send a message from the local site to the foreign X.400 system using any Microsoft Exchange Server client. To test MAPI message encapsulation, include rich text formatting and an attachment, such as a file or embedded OLE object, to verify preservation of X.400 message contents and body parts.
  2. Verify that the message arrives at the foreign system recipient's mailbox.
  3. Examine the message text, formatting, and attachments.
  4. Messages viewed with an X.400 client should contain plain text and file attachments, plus an attachment containing all the attributes the X.400 client cannot display. Messages viewed with a Microsoft Exchange Server client or another MAPI client should contain rich text and all attachments.
  5. Send a message from the foreign X.400 system to the local site using the appropriate X.400 user agent program (client).
  6. Verify that the message arrives at the local recipient's mailbox.
  7. If the message is delayed or does not arrive, use the Windows NT Event Viewer to examine the Windows NT application event log for a cause. Microsoft Exchange Server MTA activity is logged as ExchangeMTA for message transfer to and from foreign systems.

For more information on using the event logs and diagnostics logging to track messaging difficulties, see Microsoft Exchange Server Maintenance and Troubleshooting.