Example 8-1 shows a sample configuration dialogue for the node rabbit.acme.com, which is connected via DECnet to the PMDF-MTA node ACME.COM, as shown in Figure 6-1 . Example 8-2 shows a corresponding checklist file.
Whenever appropriate, each prompt also supplies a default answer which
is enclosed within square brackets. 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 8-1 Example PMDF-ACCESS V6.0 configuration
$ SET DEFAULT PMDF_TABLE:
$ PMDF CONFIGURE ACCESS
PMDF-ACCESS Configuration File Creation Utility, Version 6.0
This should NOT be run on a VMScluster where PMDF-MTA is sharing
the PMDF directory with this PMDF-ACCESS node
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 a 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.
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.
TCP/IP networking support:
(0) No TCP/IP support or the PMDF-MTA node is not reachable via TCP/IP
(1) Generic multithreaded TCP/IP *requiring* UCX emulation
PMDF provides support for various VMS TCP/IP packages marketed by
various vendors. Minimum supported versions are described in the
documentation. PMDF uses UCX emulation, which may be a separate
component to be enabled or installed. Answer 1 if you want support
for SMTP over TCP/IP on your system. If no TCP/IP package is
installed or if you don't want PMDF communicating with your TCP/IP
package, enter 0 and press return.
Use which TCP/IP option [1]? 0
Part Two: DECnet connections
Answer YES if this system is attached to a DECnet network
containing one or more remote nodes PMDF should provide access
to. Answer NO if this host is not attached to such a network.
Is this system attached to the PMDF-MTA node using DECnet [Y]? y
Answer YES if the PMDF-MTA node is a remote DECnet system
and is equipped with PhoneNet over DECnet (DN_) channels. Answer
NO if no such systems exist.
Is the PMDF-MTA node attached via PhoneNet over DECnet (DN_ channel) [N]? n
Answer YES if the PMDF-MTA node is a remote DECnet system
and is equipped with SMTP over DECnet (DSMTP_) channels. Answer
NO if no such systems exists.
Is the PMDF-MTA node attached via SMTP over DECnet (DSMTP_ channel) [N]? y
Enter the DECnet name for the PMDF-MTA system attached by an SMTP
over DECnet (DSMTP_) channel. This should be the name the MTA system
is listed under in NCP.
DECnet node name of PMDF-MTA system []? COYOTE
Enter the full domain name corresponding to the DECnet name
you just entered. If the system has no name other than the
DECnet name you just entered, simply enter the DECnet name
again. Remember that if this name gets out to other sites
they may not be able to reply to it if it is just a DECnet name.
Domain name corresponding to previous DECnet node name []? acme.com
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 []? .acme.com
Part Three: Determining local host's name(s).
Enter the 'most official' name for this system. This should be
the official domain name in most cases. This is the name that
will appear in mail addresses on this system, among other things.
Official local host name []? rabbit.acme.com
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 names is
not consistent, just press CR.
Default domain or subdomain for this system/OpenVMS cluster []? .acme.com
Enter the DECnet node name for the local host. This usually should
be the actual node name and not the DECnet OpenVMS cluster alias.
DECnet node name for the local host [RABBIT]? RABBIT
Enter the SCS (OpenVMS cluster) node name for the local host.
SCS (OpenVMS cluster) node name for the local host [RABBIT]? RETURN
Enter any aliases for the local host, these names are rewritten
to the offical local host name with rewrite rules.
Any other aliases for the local host [RETURN if no more]? RETURN
Enter YES if you want to include the other nodes in this OpenVMS cluster
in this configuration. Enter NO if you do not. YES is an appropriate
response in an entirely homogeneous OpenVMS cluster, NO may be appropriate
in a heterogeneous OpenVMS cluster.
Include other OpenVMS cluster members in configuration [Y]? N
Enter a valid user@host type of address for the local Postmaster.
This address will receive notifications 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:
[postmaster@RABBIT.ACME.COM]? RETURN
Part Four: 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
preceding 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
preceding 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.]?
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]? RETURN
Generating the PMDF configuration file...
Generating the PMDF mapping file
Generating the PMDF aliases file...
Generating the PMDF security configuration file...
Generating the PMDF-ACCESS configuration checklist...
***********************************************************************
*
* To complete your PMDF configuration, carry out the steps
* detailed in the checklist file PMDF_ROOT:[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]? n
Example 8-2 Example checklist file for PMDF-ACCESS V5.2 configuration
$ TYPE PMDF_TABLE:access.checklist
Checklist for completing the setup of your PMDF configuration.
Written by SYSTEM, 18-Feb-2000 13:44:18
This file was created by the PMDF configuration generator V6.0.
(1) If you have not already set up your MAIL$BATCH queue or added
the PMDF startup procedures to your system startup, then be sure
to do so. Setting up MAIL$BATCH is crucial to the operstion of
PMDF. Modifying the system startup can, of course, be done after
you have verified the proper operation of PMDF. Refer to the
"Post-Installation tasks" section of the first chapter of the
PMDF Installation Guide.
(2) Define the DECnet objects for SMTP over DECnet on this
system as well as on the PMDF-MTA system COYOTE.
Consult the DECnet Channels chapter of the PMDF System Manager's
Guide for details. Briefly,
$ RUN SYS$SYSTEM:NCP
NCP> DEFINE OBJECT PMDFSMTP FILE PMDF_COM:DSMTP_SLAVE.COM -
NUMBER xxx USER pmdf_account PASSWORD pmdf_pass -
ACCOUNT SYSTEM PROXY NONE
NCP> SET OBJECT PMDFSMTP FILE PMDF_COM:DSMTP_SLAVE.COM -
NUMBER xxx USER pmdf_account PASSWORD pmdf_pass -
ACCOUNT SYSTEM PROXY NONE
where xxx is an unused number which is agreed on by all nodes,
pmdf_account is the username of your PMDF account,
pmdf_pass is the password of the account
(3) On the PMDF-MTA system COYOTE, edit pmdf.cnf
to define rewrite rule(s) for rabbit.acme.com as
RABBIT $U@rabbit.acme.com
rabbit.acme.com $U@rabbit.acme.com
and define a dsmtp_ channel as (minimally)
dsmtp_local single_sys smtp
DSMTP-DAEMON
rabbit.acme.com RABBIT