Example 7-1 shows a sample PMDF-ACCESS configuration dialogue using
the pmdf configure access utility, and Example 7-2 shows
a corresponding sample checklist file. The sample site ACME.COM is as
described in Chapter 6 . PMDF-ACCESS has been installed on node
beepbeep, and the configuration is being performed on
beepbeep.
Whenever appropriate, each prompt also supplies a default answer which
is enclosed within square brackets. (If you have previously run the
pmdf configure access utility, you will be asked whether
or not it should present your previous answers as the default answers;
in the sample dialogue shown below, the pmdf configure
access utility had been run previously, but we did not choose to
be reminded of those previous answers.) Simply pressing return,
RETURN, selects the default answer. You may use the
backslash character, \, to clear a default answer.
Remember that the values entered in this sample are for purposes of example only. Be sure to use the values appropriate for your system when you perform the actual configuration.
Example 7-1 Example PMDF-ACCESS V6.0 Configuration
# cd /pmdf/table
# pmdf configure access
PMDF-ACCESS Configuration File Creation Utility, Version 6.0
This utility creates an initial PMDF configuration file
(/pmdf/table/pmdf.cnf), an initial PMDF aliases file
(/pmdf/table/aliases), an initial PMDF security configuration file
(/pmdf/table/security.cnf) and an initial PMDF mappings file
(/pmdf/table/mappings). Normally this is done just after
PMDF has been installed. However, it is possible to run this
procedure at any time.
For best results the various network products PMDF is going to be
attached to should be installed and operational when this procedure
is run. This is by no means required, but the defaults provided by
this procedure cannot be selected intelligently without having
various software packages available to interrogate.
Important note: No changes are made to existing PMDF configuration
information until all questions have been answered. This utility
can be aborted at any prompt by entering CTRL/C. The files
output by this utility may optionally be redirected to a different
location so they will have no impact on the existing PMDF configuration.
You have a history file from a previous run of the configure utility.
Do you want to use answers from the previous run as defaults [N]? n
Do you wish to continue [Y]? y
Do you wish to have a detailed explanation printed before each question [N]? y
Part One: TCP/IP networking.
Is your system set up to:
(1) Do host lookups with MX records (name server required)
(2) Do host lookups without MX records
MX (Mail eXchange) records are special entries in the TCP/IP
Domain Name Service database that redirect mail destined for
systems not directly attached to the TCP/IP network to an
intermediate gateway system that is directly attached.
If your system can use MX records to reach the MTA system, you
should answer 1, otherwise if your site has special requirements
has special requirements to ignore MX records then answer 2 if
you have a name server available. Answer 3 if no name server
is available.
Choose one of the above options [1]? 2
This system has one or more names it is known by on TCP/IP.
Enter the most 'official' of these names, preferably a
name the system is registered under in the Domain Name System.
Name of this system on TCP/IP [beepbeep.acme.com] RETURN
PMDF needs to know the IP addresses for all the interfaces used
by TCP/IP on this system. These addresses are needed so that
PMDF can recognize domain literals references to this system.
Such recognition is mandated by RFC1123.
Enter each IP address separately in a.b.c.d format, pressing CR
between each one. When you've entered them all just enter a CR
by itself to end the list
IP addresses for this system [RETURN if no more]? 12.34.56.9
IP addresses for this system [RETURN if no more]? RETURN
Enter the TCP/IP node name of the system which is the gateway for
this PMDF-ACCESS node, the answer should be a node running PMDF-MTA.
The TCP/IP name of the system running PMDF-MTA []? roadrnnr.acme.com
Enter the IP number of the system which is the gateway for this
PMDF-ACCESS node; the answer should be the IP number for the
PMDF-MTA node roadrnnr.acme.com. PMDF needs to know this number to ensure
that incoming SMTP connections from the PMDF-MTA node are allowed
even when other incoming SMTP connections may be blocked.
The IP number of the system running PMDF-MTA []? 12.34.56.7
PMDF has the ability to automatically convert shortform names
appearing on the right hand side of the at sign in an address
into fully qualified domain names. These addresses are then
routed to TCP/IP automatically. This convenience is especially
appropriate when a system is only connected via TCP/IP and not
via other networks. For example, if you were to specify a default
domain of CLAREMONT.EDU and the address USER@SIGURD was used, where
SIGURD has no other special meaning, this address will be rewritten
as USER@SIGURD.CLAREMONT.EDU and routed via TCP/IP. Enter nothing
if you don't want to have shortform addresses handled in this way.
Default domain to attach to shortform host names [none]? .acme.com
PMDF needs to know the IP address of each internal system or subnet,
including those of internal POP or IMAP client systems.
For instance, this information is used to distinguish between
internal and external systems for doing SMTP relay blocking.
Enter each IP address separately in a.b.c.d, or a.b.0.0
or a.b.c.0 format, pressing CR between each one. When you've
entered them all just enter a CR by itself to end the list.
IP addresses for your internal systems or network [RETURN if no more]? 12.34.56.0
IP addresses for your internal systems or network [RETURN if no more]? RETURN
Part Two: Determining local host's name(s).
Enter the 'most official' name for this sytem. This should be
the official domain name in most cases. This is the name that
will appear in mail addresses sent from this system, among
other things.
Official local host name [beepbeep.acme.com]? RETURN
Enter the domain or subdomain your systems are part of, if there
is one and it is consistent. For example, if your system's domain
name is HMCVAX.CLAREMONT.EDU, and in general all your systems are
part of the .CLAREMONT.EDU domain, enter '.CLAREMONT.EDU'. If your
system is not part of a domain or if your use of domain name is
not consistent, just press CR.
Default domain or subdomain for this system [none]? .acme.com
Enter any aliases for the local host; these names are rewritten
to the official local host name with rewrite rules.
Any other aliases for the local host [RETURN if no more]? RETURN
Enter a valid user@host type of address for the local Postmaster.
This address will receive notification of bounced or deferred
mail as well as various other types of status and error reports.
This address is also the one that will receive user queries about
electronic mail.
A user@host style address for the local Postmaster []? root@beepbeep.acme.com
Part Three: Process and write files
Enter the name of the configuration file you wish to have
output. The default action is to produce a real configuration
file; you may wish to choose another file name if you are
not sure you have properly answered all the questions in the
preceeding dialogue.
Configuration file to output [/pmdf/table/pmdf.cnf]? RETURN
Enter the name of the aliases file you wish to have output.
This file contains system-wide local address aliases PMDF will
recognize; special aliases are required for proper operation
of some channels. The default action is to produce a real alias
file; you may wish to choose another file name if you are
not sure you have properly answered all the questions in the
preceeding dialogue, or if you wish to preserve an existing
aliases file
Alias file to output [/pmdf/table/aliases]? RETURN
Enter the name of the mapping file you wish to have output.
The default action is to create a real mapping file;
you may wish to choose another file name if you are
not sure you have properly answered all the questions in the
preceding dialogue.
Mapping file to output [/pmdf/table/mappings]? RETURN
Enter the name of the security configuration file you wish to have
output. The default action is to create a real security.cnf file;
you may wish to choose another file name if you are
not sure you have properly answered all the questions in the
preceding dialogue.
Security configuration file to output [/pmdf/table/security.cnf]? RETURN
This procedure generates a checklist file that contains the list of
steps you must perform in order to complete your PMDF configuration.
This procedure does *NOT* perform these steps itself; you must do
them manually
PMDF checklist file name [/pmdf/table/access.checklist]? RETURN
All configuration questions have been answered.
This question gives you a last chance to change your mind
before any files are written. Answer NO if you are not sure
you want to generate the configuration you have specified. Answer
YES if you do.
Do you wish to generate the configuration files [Y]? y
Generating the PMDF configuration file...
Generating the PMDF mapping file
Generating the PMDF aliases file...
Generating the PMDF security configuration file...
Generating the PMDF checklist...
***********************************************************************
*
* To complete your PMDF configuration, carry out the steps
* detailed in the checklist file /pmdf/table/access.checklist.
*
***********************************************************************
Enter Yes if you want to see the checklist now. You can still type
the file out later if you say No.
Do you want to see the checklist now [Y]? n
Enter YES if you would now like to configure the PMDF Dispatcher.
If you answer NO, then you may configure it later with the command
# pmdf configure dispatcher
Configure the PMDF Dispatcher [Y]? y
PMDF Dispatcher Configuration File Creation Utility, V6.0
This utility creates an initial PMDF Dispatcher configuration file
/pmdf/table/dispatcher.cnf and configuration file for the PMDF HTTP server
/pmdf/table/http.cnf
Do you wish to continue [Y]? y
Do you wish to have a detailed explanation printed before each question [N]? y
Enter the port number on which the PMDF HTTP server should listen
for incoming connections.
What port number do you want the PMDF HTTP server to use [7633]? RETURN
Enter the name of the configuration file for the Dispatcher.
PMDF Dispatcher configuration file name [/pmdf/table/dispatcher.cnf]? RETURN
Enter the name of the configuration file for the HTTP server.
PMDF HTTP server configuration file name [/pmdf/table/http.cnf]? RETURN
This procedure generates a checklist file that contains the list of
steps you must perform in order to complete your PMDF configuration.
This procedure does *NOT* perform these steps itself; you must do
them manually.
PMDF checklist file name [/pmdf/table/dispatcher.checklist]? RETURN
This question gives you a last chance to change your mind
before any files are written. Answer NO if you are not sure
you want to generate the configuration you have specified. Answer
YES if you do.
Do you wish to generate the configuration files [Y]? y
Generating the file /pmdf/table/dispatcher.cnf
Generating the file /pmdf/table/http.cnf
Generating the checklist file, /pmdf/table/dispatcher.checklist
***********************************************************************
*
* To complete your PMDF configuration, carry out the steps
* detailed in the checklist file /pmdf/table/dispatcher.checklist.
*
***********************************************************************
Enter Yes if you want to see the checklist now. You can still type
the file out later if you say No.
Do you want to see the checklist now [Y]? n
Enter YES if you would now like to configure the PMDF POP and/or
IMAP servers. If you answer NO, then you may configure them later
with the command
# pmdf configure mailbox_servers
Configure the POP and IMAP servers [Y]? n
Example 7-2 Example Checklist File for PMDF-ACCESS V6.0 Configuration
# cat /pmdf/table/access.checklist
Checklist for completing the setup of your PMDF configuration.
Written by root, Mon Feb 14 17:26:08 PST 2000
This file was created by the PMDF configuration generator V6.0
(1) Be sure to configure the PMDF Dispatcher, using the
command:
pmdf configure dispatcher
(2) Make sure to perform the remaining post-installation
tasks as described in the PMDF Installation Guide &
Release Notes.
Example 7-3 Sample Dispatcher configuration checklist file
# cat /pmdf/table/dispatcher.checklist
Checklist for completing the setup of your PMDF Service Dispatcher
Written by root, Mon Feb 14 17:30:07 PST 2000
This file was created by the PMDF configuration generator V6.0
(1) You have to start a new Dispatcher or restart the currently running
Dispatcher for the new configuration to take effect. The following
command is to be issued on each node:
pmdf start dispatcher
or
pmdf restart dispatcher
(2) The Dispatcher configuration includes a definition for the
PMDF HTTP server. The PMDF HTTP server may serve out PMDF
documentation, general PMDF operation monitoring information,
and statistics on the Dispatcher's own operation, and allows
for web-based access to PMDF popstore management, and user
mailbox filters.
All access to the PMDF HTTP server is disabled unless an
HTTP_ACCESS mapping table is in use; access may be generally
por selectively enabled via this mapping table. The PMDF-MTA
configuration utility generates an HTTP_ACCESS mapping table
allowing access to "internal" systems. The PMDF-ACCESS
configuration utility generates no HTTP_ACCESS table, so access
will be denied to all by default. See the PMDF System Manager's
Guide for details on the use of that mapping table.
Alternatively or in addition, if there is a PMDF HTTP server
capability that you do not wish to utilize at all, you may
prefer to remove that entire section from the HTTP server
configuration file, /pmdf/table/http.cnf. See the PMDF
System Manager's Guide for details on the format of this file.