PMDF System Manager's Guide

The following example configuration file for OpenVMS or UNIX (since an l channel is used; on NT a msgstore channel would be used instead) shows how rewrite rules are used to route messages to the proper channel. No domain names are used in order to keep things as simple as possible.

Example 2-2 A Simple Configuration File

! test.cnf - An example configuration file for PMDF. (1) ! ! This is only an example of a configuration file. It serves ! no useful purpose and should not be used in a real system. ! a $U@a (2) b $U@b c $U%c@b d $U%d@a (3) l (4) local-host a_channel 822 (5) a e b_channel 733 network b f

The key items in the configuration file shown in Example 2-2 are

1. Exclamation points, !, are used to introduce comment lines. The exclamation point must appear in the first column. An exclamation point appearing anywhere else is interpreted as a literal exclamation point.
2. The rewrite rules appear in the first half of the configuration file. Absolutely no blank lines should appear amongst the lines of rewrite rules. Lines with comments (beginning with an exclamation point in the first column) are, however, permitted.
3. The first blank line to appear in the file signifies the end of the rewrite rules section and the start of the channel blocks.
4. The first channel block to appear is always the local channel. On OpenVMS and UNIX platforms, this is the "l" channel (lowercase letter L); on NT, this must be a msgstore channel. Blank lines then separate each channel block from one another. Exception: a defaults channel may appear before the local channel.
5. A channel named a_channel. Note the use of a channel keyword (822) with this channel.

The routing and queuing of messages by the configuration seen in Example 2-2 is shown in Table 2-9 below.

Table 2-9 Message Routing and Queuing Generated by Example 2-2

Address	Routed to	Queued to channel
u@a	a	a_channel
u@b	b	b_channel
u@c	b	b_channel
u@d	a	a_channel
u@e	e	a_channel
u@f	f	b_channel