The MAILbus 400 Message Transfer Agent (MTA) must be properly configured with an "MTA AGENT" definition as well as routing entries in order to direct messages based on X.400 address information to the PMDF-MB400 gateway agent. See your MAILbus 400 documentation in order to configure routing information.

The PMDF-MB400 XAPI agent definition is straightforward and requires nothing more than an agent name, type, and invocation filename.

In order to define the agent to MAILbus 400, if using the MAILbus 400 MTA on OpenVMS, use the commands:

$ mcr ncl NCL> create mta agent "PMDF-MB400" type xapi NCL> set mta agent "PMDF-MB400" invocation filename "PMDF_COM:xapi_slave.com" NCL> enable mta agent "PMDF-MB400"

or if using the MAILbus 400 MTA on UNIX, use:

# ncl ncl> create mta agent "PMDF-MB400" type xapi ncl> set mta agent "PMDF-MB400" invocation filename "/pmdf/bin/xapi_slave" ncl> enable mta agent "PMDF-MB400"

If you are using PMDF-MB400 to connect to a remote Mailbus 400, omit the

set mta agent "PMDF-MB400" invocation filename ...

command and instead let the PMDF system periodically poll MAILbus 400 to pick up messages. Alternatively, replace the invocation filename with the name of a command procedure or script on the remote MAILbus 400 system that executes the command @PMDF_COM:xapi_slave.com (OpenVMS) or /pmdf/bin/xapi_slave (UNIX) on the PMDF system --- for instance, via rsh.