When using PMDF-MR to act as a Message Router Transport Service replacement, messages to PMDF-MR from Office Server, ALL-IN-1 Electronic Messaging, Teamlinks, or any of the A1MAIL products should be sent to an address of the form

user@host

where user@host is the address of the recipient; i.e., to a regular RFC 822 style address.

When using PMDF-MR to connect to Message Router, messages to PMDF-MR from Office Server, ALL-IN-1 Electronic Messaging, Teamlinks, or any of the A1MAIL products should be sent to an address of the form

user@host@mboxname

where user@host is the address of the recipient and mboxname specifies the Message Router mailbox name, usually PMDF, assigned to PMDF-MR during the configuration of PMDF-MR. (See Section 39.2.1.) If the PMDF-MR gateway does not reside on your local machine, it must be accessible via Message Router. In this case, this portion of the address can include a route which passes through one or more Message Router nodes and ends at the PMDF Message Router mailbox. The following example uses the PMDF-MR gateway on the local machine to reach an Internet address

postmaster@ymir.claremont.edu@pmdf

If the PMDF-MR gateway resides on a remote Message Router node called, for instance, DELTA, one might reach the same Internet address by specifying

postmaster@ymir.claremont.edu@pmdf@delta

Note that the IN% prefix and quoting requirements for PMDF addresses within VMS MAIL do not apply when specifying PMDF addresses to ALL-IN-1 or A1MAIL.

If delivery receipt or read receipt notifications are desired, simply use the standard facilities of Office Server, ALL-IN-1, A1MAIL, or Teamlinks to specify such. Do not use the "(delivery-receipt)" construct described in Section 20.3 with ALL-IN-1 or A1MAIL. Similarly, message attachments are specified through the standard facilities of the ALL-IN-1 or A1MAIL user agents.

The PMDF-MR gateway encodes attachments and non-text body parts using the format specified by the MIME standard, RFC 2045. If support does not exist on the receiving end to recognize this format, the recipient can have to manually extract attachments or decode non-text body parts. If the recipient uses PMDF and PMDF-MR version 4.0 or later, then attachments and non-text body parts will be handled transparently between the sender and recipient. The encoding and format used by PMDF is designed to pass through intermediate gateways and networks which do not support the encoding format, while preserving these capabilities upon arrival at the other end.