PMDF System Manager's Guide

The configuration file shown in Example 2-4 is a minimal version of the sort of configuration typical for a system that communicates directly with the Internet via TCP/IP. The system's name in this example is assumed to be sample.com.

Example 2-4 Sample Configuration File

! pmdf.cnf - PMDF configuration file for sample.com. ! ! Rewrite rules for the local host/cluster ! sample $U@sample.com sample.com $U@sample.com ! ! Rewrite rules for the Internet ! ! Ascension Island .AC $U%$H$D@TCP-DAEMON . [text . removed for . brevity] ! Zimbabwe .ZW $U%$H$D@TCP-DAEMON ! ! BITNET (not properly an Internet domain) ! .BITNET $U@$H$D@interbit.cren.net@TCP-DAEMON ! ! Rewrite rules for TCP/IP domain literals ! [1.2.3.4] $U@sample.com [] $U%[$L]@TCP-DAEMON l nox_env_to sample.com tcp_local single_sys smtp mx TCP-DAEMON

This configuration file is quite simple. Messages to the local system (whose name is sample.com) are sent to the local channel. Any other message whose address contains a recognizable top-level domain specification is routed through the SMTP over TCP/IP channel, tcp_local, to the Internet. Any other address is treated as being illegal.