The PMDF-MR configuration utility creates all of the necessary PMDF
channels for you; you do not need to undertake the steps described in
this section. Channels and associated rewrite rules appear in the
mr.chans and mr.rules files in
the PMDF table directory.
39.2.3.1 Channels connecting to Message Router
At least one MR channel is required to connect to Message Router. The
entry for the channel should look like this:
mr_local master user mboxname daemon node gateway-domain-nameHere
mboxname is the name of the Message Router
mailbox created in Section 39.2.1 and
gateway-domain-name is the domain name of the
gateway. Both of these names were specified by you when you ran the
PMDF-MR configuration utility.
node is the DECnet node name for the system where
the appropriate Message Router mailbox resides. If the node is the
local system where PMDF-MR is running, simply omit the daemon
node clause entirely.
For example, a channel for connecting to a local (same node) Message Router might appear as
mr_local master user PMDF mr.acme.com
You may or may not need a rewrite rule that points at this channel block depending on your configuration:
gateway-domain-name $U@gateway-domain-nameFor example,
mr.acme.com $U@mr.acme.com
When configuring using the PMDF-MR configuation utility, you may also
select additional domain names, a1-domain-name
and am-domain-name, to provide direct addressing
for your local Office Server, ALL-IN-1 IOS or A1MAIL (MailWorks) setup.
If so, additional rewrite rules will be present in your
mr.rules file of the form:
a1-domain-name $U%a1-domain-name@gateway-domain-name am-domain-name $U%am-domain-name@gateway-domain-nameFor instance,
a1.acme.com $U%a1.acme.com@mr.acme.com am.acme.com $U%am.acme.com@mr.acme.com
Note:
Rewrite rules and domain name choices for PMDF-MR channels must be carefully coordinated with the PMDF-MR address mapping rules also generated by the PMDF-MR configuration utility and discussed in Section 39.3 . Alterations in PMDF-MR rewrite rules or domain names generally require corresponding changes in the address mapping rule databases, so such changes are usually most conveniently performed by re-running the PMDF-MR configuration utility.
39.2.3.2 Message Router Transfer Service replacement channels
MRIF channels are used to provide Message Router Transfer Service
replacement capabilities. Each channel corresponds to a single Message
Router mailbox. Message Router agents then connect to the channel as a
channel program rather than connecting to a Message Router mailbox.
A typical channel entry looks like this:
mrif_mailbox user mailbox replacement-domain-nameHere
mailbox is the name of the mailbox. This
must match the name of the mailbox the Message Router agent expects to
use. (For example, the ALL-IN-1 mailbox name is commonly A1 and the
MailWorks mailbox name is commonly AM, but your site may be using other
mailbox names. You must configure PMDF-MR to use the names your Message
Router agents are actually using.)
replacement-domain-name is the domain name
associated with the agent --- mail sent to this domain will be
transferred to the agent, and mail coming from the agent will be tagged
with this domain name. Both of these names were specified by you when
you ran the PMDF-MR configuration utility.
It is also customary, though in some configurations not strictly
necessary, to include the PMDF configuration file rewrite rules for any
replacement-domain-name,
replacement-domain-name $U@replacement-domain-name
For instance, for a site acme.com using PMDF-MR in MR TS replacement mode to connect to the mailbox AM, the channel definition might be
mrif_am user AM am.acme.comand a rewrite rule might be
am.acme.com $U@am.acme.com
Note:
Rewrite rules and domain name choices for PMDF-MR channels must be carefully coordinated with the PMDF-MR address mapping rules also generated by the PMDF-MR configuration utility and discussed in Section 39.3 . Alterations in PMDF-MR rewrite rules or domain names generally require corresponding changes in the address mapping rule databases, so such changes are usually most conveniently performed by re-running the PMDF-MR configuration utility.