Previous | Next | Contents | Index |
The following two sections document how to add an addressing channel to your configuration and, if desired, how to customize the command names recognized by the channel.
More recent versions of the PMDF-MTA configuration utility automatically generate an addressing channel in the PMDF configuration. If you have configured PMDF using a recent version of the configuration utility and hence already have an addressing channel in your configuration, then the steps in Section 28.1.3.1 have already been performed for you. |
28.1.3.1 Adding the Channel to the Configuration File
To set up an addressing channel, you must add rewrite rules and a
channel block definition to the PMDF configuration file.
The first step is to pick a domain name for the addressing channel; for example, addressing.example.com. Mail to be processed by the channel should then be addressed to x@addressing.example.com. The value of x is irrelevant --- it is never used by the channel and, at present, simply discarded. After selecting a domain name, add rewrite rules for it to the top of the configuration file
addressing $U%domain-name@ADDRESSING-DAEMON domain-name $U%domain-name@ADDRESSING-DAEMON |
domain-name
is the domain name selected for
the addressing channel. For example, if the domain name selected is
addressing.example.com, then the rewrite rule would appear as
addressing.example.com $U%addressing.example.com@ADDRESSING-DAEMON |
address ADDRESSING-DAEMON |
If desired, additional addressing channels can be added. They should have names beginning with "address_" and not exceed a length of 32 characters.
If you are part of a TCP/IP network, then you can want to add the addressing channel's domain name (or names) you selected to your DNS using MX records. This will allow other machines to route mail to the addressing channel. |
28.1.3.2 Option Files
An option file can be used to alter the addressing commands recognized
by the addressing channel. Option files are stored in the PMDF table
directory and have names of the form x_option
where x
is the name of the channel to which the
option file applies. (In most instances, the file will be
PMDF_TABLE:address_option.
on OpenVMS, or
/pmdf/table/address_option
on UNIX, or typically
C:\pmdf\table\address_option
on NT.)
If you supply an option file, then you must define all commands which are to be accepted. This is even the case if you are just supplying an option file to set some non-command related parameter. This behavior is intentional; it allows commands to be disabled.
Option files consist of several lines. Each line contains the setting for one option. An option setting has the form:
option=command-name |
option
are given in
Table 28-3 and command-name
is a string
specifying the name of a command to establish. Synonymous commands can
be established by using the same option in the options file;
e.g., EMAIL in Example 28-1.
Option | Usage |
---|---|
AFTER | FAX address AFTER attribute |
AT | FAX & printer address AT attribute |
AUTH | FAX address AUTH attribute |
COVER | FAX address COVER attribute |
COMMENTS | RFC 822 Comments: header line |
DEFAULT_DOMAIN | Domain name to use when none specified for a FAX or printer address; by default no default domain name is established |
DELIMITER | Single character used to delimit command names; e.g., the colon, :, in ":stop:" |
DELRCPT | Address to which to send delivery receipts |
DMN | FAX & printer domain name |
Regular RFC 822 To: address (synonym for EMAIL_TO) | |
EMAIL_BCC | Regular RFC 822 Bcc: address |
EMAIL_CC | Regular RFC 822 Cc: address |
EMAIL_TO | Regular RFC 822 To: address |
FN | FAX address FN attribute |
FROM | RFC 822 From: address |
FSI | FAX address FSI attribute |
MIME_MODE | Control whether the addressing channel will process commands from MIME encoded message parts |
MS | Printer address MS attribute |
NDELRCPT | Suppress delivery receipt requests |
O | FAX & printer address O attribute |
OU | FAX & printer address OU attribute |
P1--P8 | Printer address P1--P8 attributes |
PS_QUALIFIERS | RFC 822 X-PS-Qualifiers: header line |
RP_MODE | Control whether the addressing channel operates in a mode compatible with parsing MIME application/remote-printing message parts |
SETUP | FAX address SETUP attribute |
SFN | FAX address SFN attribute |
STN | FAX address STN attribute |
STOP | String to recognize as a stop or end command |
SUBJECT | RFC 822 Subject: header line |
TN | FAX & printer address TN attribute |
TTI | FAX address TTI attribute |
USERNAME | Username to associate with printer channel print jobs |
The example option file given in Example 28-1 establishes the default
command set used by the addressing channel. A copy of this file,
address_option.sample
, can be found in the PMDF table
directory, i.e., PMDF_TABLE:address_option.sample
on OpenVMS or /pmdf/table/address_option.sample
on UNIX.
Example 28-1 Example Addressing Channel Option File |
---|
! *** If you make your own option file, then you must specify _ALL_ the ! *** addressing commands which you use! ! DELIMITER=: MIME_MODE=0 RP_MODE=0 EMAIL_TO=To EMAIL_CC=Cc EMAIL_BCC=Bcc EMAIL_TO=e-mail EMAIL_TO=email EMAIL_TO=PMDF EMAIL_TO=RFC822 COMMENTS=Comments PS_QUALIFIERS=PS Qualifiers AFTER=Transmit after AT=Recipient's name AUTH=Authorization code COVER=Cover page DELRCPT=Delivery receipt DMN=FAX gateway address DMN=Printer domain name FN=FAX telephone number FROM=From FSI=FAX modem's telephone number MS=Mail stop NDELRCPT=No delivery receipt O=Recipient's organization OU=Recipient's address P1=P1 P2=P2 P3=P3 P4=P4 P5=P5 P6=P6 P7=P7 P8=P8 SETUP=Initialization file SFN=My FAX telephone number STN=My telephone number STOP=end STOP=start STOP=stop SUBJECT=Subject TN=Recipient's telephone number TTI=My organization USERNAME=Username USERNAME=User |
One of the most useful options is the DEFAULT_DOMAIN option. To prevent, for instance, users from having to specify
:FAX gateway address: ps-fax |
DEFAULT_DOMAIN=ps-fax |
address_option.sample
, to an option file with the correct
name (e.g., address_option
), and then add to that
file the DEFAULT_DOMAIN setting.
Previous | Next | Contents | Index |