PMDF includes a number of test utilities, including utilities
for testing general address rewriting and access control (PMDF
TEST/REWRITE), testing low level PMDF mappings and pattern
matching (PMDF TEST/MAPPING and PMDF TEST/MATCH), and for a
variety of channel specific applications.
1 /CC
Test cc:Mail channel address transformations.
Syntax
PMDF TEST/CC [test-address|test-time]
Command Qualifiers Defaults
/822TOLAN /822TOLAN
/BACKWARD /FORWARD
/CHANNEL=channel-name /CHANNEL=cc_local
/DEBUG /NODEBUG
/ENVELOPE /HEADER
/FORWARD /FORWARD
/HEADER /HEADER
/LANTO822 /822TOLAN
/TIME See text
1.1 – Restrictions
This utility is supplied only with the PMDF-LAN optional layered
product.
1.2 – Prompts
Address: test-address
Time: test-time
1.3 – Parameters
test-address
Optional address to test.
test-time
Optional time to test.
1.4 – Description
Test a cc:Mail channel's transformation of an address or time.
1.5 – Command Qualifiers
1.5.1 /822TOLAN
/822TOLAN (default)
/LANTO822
The testing process can test conversion of RFC 822 addresses to
cc:Mail format, /822TOLAN, or test conversion of cc:Mail format
addresses to RFC 822 format, /LANTO822.
1.5.2 /BACKWARD
/BACKWARD
/FORWARD (default)
The testing process can test conversion of backwards or forwards
pointing addresses; the default is forward pointing addresses.
1.5.3 /CHANNEL
/CHANNEL=channel-name
Different cc:Mail channels may be configured to perform different
transformations. If this qualifier is not specified, the default
is to test the cc_local channel.
1.5.4 /DEBUG
/DEBUG
/NODEBUG (default)
The testing process is capable of producing detailed processing
information. The /DEBUG qualifier enables this output; it is
disabled by default.
1.5.5 /ENVELOPE
/ENVELOPE
/HEADER (default)
The testing process can test envelope or header addresses; the
default is header addresses.
1.5.6 /TIME
The testing process by default tests address transformations, but
the /TIME qualifier specifies that it should instead test time
transformations.
1.6 – Examples
$ PMDF TEST/CC adam@ccmail.examle.com
ADAM
$ PMDF TEST/CC postmaster@example.com
POSTMASTER at PMDF
$ PMDF TEST/CC service@example.com
SERVICE@EXAMPLE.COM at PMDF
This example shows testing a cc_local channel's transformation
of several addresses. The output shown corresponds to a cc_
local channel with official host name ccmail.example.com and
channel option CC_GATEWAY_NAME=PMDF, and where the site has
example.com as the official local host name.
2 /CHANNEL
2.1 – X400
Test X.400 channel connection.
Syntax
PMDF TEST/CHANNEL X400
Command Qualifiers Defaults
/MTA=mta-id See text
/TRANSFER=file-spec See text
2.1.1 – Restrictions
This utility is supplied only with the PMDF-X400 optional layered
product.
2.1.2 – Parameters
X400
The string parameter X400 is required.
2.1.3 – Description
The PMDF TEST/CHANNEL X400 utility can be used to test the
configuration of the X400_LOCAL channel and verify that it can
successfully connect to the remote MTA. Network configuration
errors and validation problems will be reported by the utility.
Any file can be specified for transfer via the /TRANSFER
qualifier. However, if the file does not contain P1/P2/P22
information valid to the remote X.400 MTA, then the behavior
is undefined. Some X.400 MTAs, such as PMDF-X400 and HP's Message
Router X.400 Gateway, MRX, will accept any data and generate an
error at a later stage in processing. Other MTAs, such as PP and
EAN will abort the network connection as soon as they detect that
the incoming data is invalid.
If PMDF TEST/CHANNEL X400 does not complete the connection
successfully, it will indicate whether it is having trouble
making the network connection itself or the network connection
is rejected due to validation failure. If the former, make sure
that the remote TSAP address is correctly specified for this MTA.
If the latter, then check the MTA names and passwords. Remember
that each MTA validates the name and password sent by the other
MTA. Both sides of the connection must pass validation or the
connection will be terminated with a validation failure error.
Log or trace information on the remote MTA can prove invaluable
when tracing validation failures or problems with messages being
rejected.
An additional level of detail, showing every I/O operation as
well as every byte of data sent and received on the network
connection, can be enabled by defining the logical name PMDF_
UNIXLIB_TRACE before running PMDF TEST/CHANNEL X400. The
equivalence value for the logical name may be a filename or the
reserved word "TTY". In the latter case, trace output will be
directed to the process's SYS$OUTPUT. For example:
$ DEFINE PMDF_UNIXLIB_TRACE TTY
followed by a PMDF TEST/CHANNEL X400 command will result in all
of the test output as well as a complete trace of all data sent
and received. The additional level of detail afforded by I/O
tracing may be required should you need to work with Process
Software support personnel to solve a problem.
2.1.4 – Command Qualifiers
2.1.4.1 /MTA
/MTA=mta-id
Specifies the MTA to connect to when PMDF-X400 is configured for
more than one remote MTA. This qualifier is only applicable when
PMDF-X400 has been configured to support more than one remote
MTA. The mta-id value must be an MTA identification as defined in
the X400-MTAID database. Note that in a single MTA configuration,
as generated by the PMDF CONFIGURE X400 utility, there is no MTA
identification nor X400-MTAID database.
2.1.4.2 /TRANSFER
/TRANSFER=file-spec
Use RTS to transfer the specified file, file-spec. If no file is
given it will default to NLA0: and transfer 0 bytes of data. Note
that transferring 0 bytes of data by specifying /TRANSFER is not
the same as transferring nothing, which is the behavior when this
qualifier is not present.
2.1.5 – Examples
$ PMDF TEST/CHANNEL X400
23:12:57.74: RTS rts_send: initializing
23:12:57.85: RTS Transfer mode is NORMAL 1988
23:12:57.85: RTS rts_send: preparing for RTS transfer to MTA
23:12:57.85: RTS rts_send: found cached connection, slot = 0
23:12:57.85: RTS rts_
send: no cached connection, opening new connection
23:12:57.85: RTS88 Local host is NAPLES.EXAMPLE.COM
23:12:57.85: RTS88 Connecting to "MTA"/"MTA"/"X400-88"
/Internet=OTHERMTA.EXAMPLE.COM
23:12:57.85: RTS88.Request user-data: MTA-
NAME [MyMTA] PASSWORD [secret]
23:12:57.89: RTS88 Called presentation address: "MTA"/"MTA"/"X400-
88"
/Internet=12.34.56.78
23:12:57.90: RTS88 Calling presentation address: "MTA"/"MTA"/"PMDF-
X400"/
23:12:58.55: RTS.Response user-data: MTA-
NAME [OtherMTA] PASSWORD []
23:12:58.55: RTS rts_send: Connection successful sd = 4
23:12:58.57: RTS rts_send: new connection cached, slot = 0
23:12:58.57: X400 TEST: RTS test successful!
23:12:58.57: RTS rts_disconnect_all
23:12:58.57: RTS disconnecting slot 0
23:12:58.57: RTS88 rts88_disconnect: closing sd 4
23:12:58.57: RTS88.CloseRequest
This example shows testing an outgoing X.400 connection for a
configuration with an PMDF_TABLE:X400_LOCAL_OPTION. file of:
MODE=1988-NORMAL
LOCAL_MTANAME="MyMTA"
LOCAL_PASSWORD="secret"
LOCAL_ADDR="MTA"/"MTA"/"PMDF-X400"
REMOTE_MTANAME="OtherMTA"
REMOTE_PASSWORD=""
REMOTE_ADDR="MTA"/"MTA"/"X400-88"/Internet=OTHERMTA.EXAMPLE.COM
3 /FAX_ROUTING
Test the effect on DATA_TO_BITMAP channel processing options of
FAX routing mappings.
Syntax
PMDF TEST/FAX_ROUTING [routing]
Command Qualifiers Defaults
/DEBUG /NODEBUG
/IMAGE_FILE=file-spec /IMAGE_FILE=PMDF_CONFIG_DATA
/MAPPING_FILE=file-spec /MAPPING_FILE=PMDF_MAPPING_FILE
3.1 – Restrictions
This utility is supplied only with the PMDF-FAX optional layered
product.
3.2 – Prompts
Routing: routing
3.3 – Parameters
routing
Optional routing to test.
3.4 – Description
TEST/FAX_ROUTING may be used to test entries in the FAX_ROUTING
mapping tables used by the DATA_TO_BITMAP channel of PMDF-FAX.
These entries are used to alter, on a per received FAX basis, the
processing options used by that channel.
The specified routing will be looked up in the FAX_ROUTING
mapping table and, if found, the mapping result-a list of
processing options for the DATA_TO_BITMAP channel-will be parsed.
If a routing is specified on the command line, TEST/FAX_ROUTING
acts upon the specified routing and then exits. If no routing is
specified on the command line, then TEST/FAX_ROUTING will prompt
for routings until a CTRL/Z is entered.
3.5 – Command Qualifiers
3.5.1 /DEBUG
/DEBUG
/NODEBUG (default)
The testing process is capable of producing detailed processing
information. The /DEBUG qualifier enables this output; it is
disabled by default.
3.5.2 /IMAGE_FILE
/IMAGE_FILE[=filename]
/NOIMAGE_FILE
The /IMAGE_FILE qualifier serves two purposes. The first is when
/NOIMAGE_FILE is specified; this instructs TEST/FAX_ROUTING to
ignore any compiled configuration unconditionally and to read
configuration information from the various text files instead.
When the /IMAGE_FILE qualifier is specified without an optional
file name, PMDF TEST/FAX_ROUTING will load the compiled
configuration from the file PMDF_CONFIG_DATA. If, instead, a
file name is specified then PMDF TEST/FAX_ROUTING will load the
compiled configuration from the specified file.
3.5.3 /MAPPING_FILE
/MAPPING_FILE=filename
TEST/FAX_ROUTING normally consults the default mapping file,
PMDF_MAPPING_FILE, during processing. The /MAPPING_FILE qualifier
specifies an alternate file to use in place of PMDF_MAPPING_FILE.
This qualifier has no effect unless /NOIMAGE_FILE is specified
or no compiled configuration exists; use of any compiled
configuration will preclude reading any sort of mapping file.
3.6 – Examples
The FAX_ROUTING table entry,
6215319 /OUTPUT_AS=EMAIL/OUTPUT_FORMAT=DDIF/TO=dan@example/
may be tested with this utility:
$ PMDF TEST/FAX_ROUTING 6215319
Processing options:
OUTPUT_FORMAT = DDIF
PAGE_MAGNIFICATION = 0.95
OUTPUT_AS = EMAIL
TO = dan@example
SAVE_INPUT = FALSE
4 /FF
Test MS Mail channel address transformations.
Syntax
PMDF TEST/FF [test-address|test-time]
Command Qualifiers Defaults
/822TOLAN /822TOLAN
/BACKWARD /FORWARD
/CHANNEL=channel-name /CHANNEL=ff_local
/DEBUG /NODEBUG
/ENVELOPE /HEADER
/FORWARD /FORWARD
/HEADER /HEADER
/LANTO822 /822TOLAN
/TIME See text
4.1 – Restrictions
This utility is supplied only with the PMDF-LAN optional layered
product.
4.2 – Prompts
Address: test-address
Time: test-time
4.3 – Parameters
test-address
Optional address to test.
test-time
Optional time to test.
4.4 – Description
Test a MS Mail channel's transformation of an address or time.
4.5 – Command Qualifiers
4.5.1 /822TOLAN
/822TOLAN (default)
/LANTO822
The testing process can test conversion of RFC 822 addresses to
MS Mail format, /822TOLAN, or test conversion of MS Mail format
addresses to RFC 822 format, /LANTO822.
4.5.2 /BACKWARD
/BACKWARD
/FORWARD (default)
The testing process can test conversion of backwards or forwards
pointing addresses; the default is forward pointing addresses.
4.5.3 /CHANNEL
/CHANNEL=channel-name
Different MS Mail channels may be configured to perform different
transformations. If this qualifier is not specified, the default
is to test the ff_local channel.
4.5.4 /DEBUG
/DEBUG
/NODEBUG (default)
The testing process is capable of producing detailed processing
information. The /DEBUG qualifier enables this output; it is
disabled by default.
4.5.5 /ENVELOPE
/ENVELOPE
/HEADER (default)
The testing process can test envelope or header addresses; the
default is header addresses.
4.5.6 /TIME
The testing process by default tests address transformations, but
the /TIME qualifier specifies that it should instead test time
transformations.
4.6 – Examples
$ PMDF TEST/FF adam@msmail.example.com
CSI:EXAMPLE/HQ/ADAM
$ PMDF TEST/FF "EXAMPLE/ADMIN/CARL@msmail.example.com"
CSI:EXAMPLE/ADMIN/CARL
$ PMDF TEST/FF service@example.com
SMTP:SERVICE@EXAMPLE.COM
This example shows testing a ff_local channel's transformation
of several addresses. The output shown corresponds to a ff_
local channel with the official host name msmail.example.com
and with the channel option settings FF_DEFAULT_NETWORK=EXAMPLE
and FF_DEFAULT_POSTOFFICE=HQ.
5 /GROUPWISE
Test GroupWise (WordPerfect Office) channel address
transformations; a synonym for PMDF TEST/WPO.
Syntax
PMDF TEST/GROUPWISE [test-address|test-time]
Command Qualifiers Defaults
/822TOLAN /822TOLAN
/BACKWARD /FORWARD
/CHANNEL=channel-name /CHANNEL=wpo_local
/DEBUG /NODEBUG
/ENVELOPE /HEADER
/FORWARD /FORWARD
/HEADER /HEADER
/LANTO822 /822TOLAN
/TIME See text
5.1 – Restrictions
This utility is supplied only with the PMDF-LAN optional layered
product.
5.2 – Prompts
Address: test-address
Time: test-time
5.3 – Parameters
test-address
Optional address to test.
test-time
Optional time to test.
5.4 – Description
Test a GroupWise (WordPerfect Office) channel's transformation of
an address or time; a synonym for PMDF TEST/WPO.
5.5 – Command Qualifiers
5.5.1 /822TOLAN
/822TOLAN (default)
/LANTO822
The testing process can test conversion of RFC 822 addresses
to GroupWise format, /822TOLAN, or test conversion of GroupWise
format addresses to RFC 822 format, /LANTO822.
5.5.2 /BACKWARD
/BACKWARD
/FORWARD (default)
The testing process can test conversion of backwards or forwards
pointing addresses; the default is forward pointing addresses.
5.5.3 /CHANNEL
/CHANNEL=channel-name
Different GroupWise channels may be configured to perform
different transformations. If this option is not specified, the
default is to test the wpo_local channel.
5.5.4 /DEBUG
/DEBUG
/NODEBUG (default)
The testing process is capable of producing detailed processing
information. The /DEBUG qualifier enables this output; it is
disabled by default.
5.5.5 /ENVELOPE
/ENVELOPE
/HEADER (default)
The testing process can test envelope or header addresses; the
default is header addresses.
5.5.6 /TIME
The testing process by default tests address transformations, but
the /TIME qualifier specifies that it should instead test time
transformations.
5.6 – Examples
$ PMDF TEST/GROUPWISE adam@groupwise.example.com
EXAMPLE.HQ.ADAM
$ PMDF TEST/GROUPWISE postmaster@example.com
EXAMPLE.PMDF.POSTMASTER
$ PMDF TEST/GROUPWISE service@example.com
EXAMPLE.PMDF."service@example.com"
This example shows testing a wpo_local channel's transformation
of several addresses. The output shown corresponds to a wpo_
local channel with official host name groupwise.example.com and
channel options WPO_DEFAULT_DOMAIN=EXAMPLE, WPO_DEFAULT_PO=HQ,
WPO_GATEWAY_DOMAIN=EXAMPLE, and WPO_GATEWAY_PO=PMDF, and where
the site has example.com as the official local host name.
6 /LN
Test Lotus NotesMail channel address transformations.
Syntax
PMDF TEST/LN [test-address|test-time]
Command Qualifiers Defaults
/822TOLAN /822TOLAN
/BACKWARD /FORWARD
/CHANNEL=channel-name /CHANNEL=ln_local
/DEBUG /NODEBUG
/ENVELOPE /HEADER
/FORWARD /FORWARD
/HEADER /HEADER
/LANTO822 /822TOLAN
/TIME See text
6.1 – Restrictions
This utility is supplied only with the PMDF-LAN optional layered
product.
6.2 – Prompts
Address: test-address
Time: test-time
6.3 – Parameters
test-address
Optional address to test.
test-time
Optional time to test.
6.4 – Description
Test a Lotus NotesMail channel's transformation of an address or
time.
6.5 – Command Qualifiers
6.5.1 /822TOLAN
/822TOLAN (default)
/LANTO822
The testing process can test conversion of RFC 822 addresses to
Lotus NotesMail format, /822TOLAN, or test conversion of Lotus
NotesMail format addresses to RFC 822 format, /LANTO822.
6.5.2 /BACKWARD
/BACKWARD
/FORWARD (default)
The testing process can test conversion of backwards or forwards
pointing addresses; the default is forward pointing addresses.
6.5.3 /CHANNEL
/CHANNEL=channel-name
Different Lotus NotesMail channels may be configured to perform
different transformations. If this qualifier is not specified,
the default is to test the ln_local channel.
6.5.4 /DEBUG
/DEBUG
/NODEBUG (default)
The testing process is capable of producing detailed processing
information. The /DEBUG qualifier enables this output; it is
disabled by default.
6.5.5 /ENVELOPE
/ENVELOPE
/HEADER (default)
The testing process can test envelope or header addresses; the
default is header addresses.
6.5.6 /TIME
The testing process by default tests address transformations, but
the /TIME qualifier specifies that it should instead test time
transformations.
6.6 – Examples
$ PMDF TEST/LN adam@notesmail.example.com
adam @ PMDF
This example shows testing a ln_local channel's transformation
of an address. The output shown corresponds to a ln_local
channel with official host name notesmail.example.com and
channel option LN_GATEWAY_DOMAIN=PMDF.
7 /MAPPING
Test a mapping table in the mapping file.
Syntax
PMDF TEST/MAPPING [input-string]
Command Qualifiers Defaults
/FLAGS=(a,b,c,...) /NOFLAGS
/IMAGE_FILE=file-spec /IMAGE_FILE=PMDF_CONFIG_DATA
/MAPPING_FILE=file-spec /MAPPING_FILE=PMDF_MAPPING_FILE
/OPTION_FILE=file-spec /OPTION_FILE=PMDF_OPTION_FILE
/TABLE=table-name None
7.1 – Restrictions
None.
7.2 – Prompts
Enter table name: table-name
7.3 – Parameters
input-string
Optional input string to map.
7.4 – Description
TEST/MAPPING may be used to test the behavior of a mapping table
in the mapping file. The result of mapping an input string
will be output along with information about any metacharacters
specified in the output string.
If an input string is supplied on the command line, then only the
result of mapping that input string will be output. If no input
string is specified TEST/MAPPING will enter a loop, prompting
for an input string, mapping that string, and prompting again
for another input string. TEST/MAPPING will exit when a CTRL/Z is
entered.
7.5 – Command Qualifiers
7.5.1 /FLAGS
/FLAGS=(a,b,c,...)
/NOFLAGS
The /FLAGS qualifier is used to specify particular flags to set
during the mapping testing; for instance, the E (envelope), B
(header/body), or I (message id) flags when testing a REVERSE
mapping.
7.5.2 /IMAGE_FILE
/IMAGE_FILE[=filename]
/NOIMAGE_FILE
The /IMAGE_FILE qualifier serves two purposes. The first is when
/NOIMAGE_FILE is specified; this instructs TEST/MAPPING to ignore
any compiled mapping information unconditionally and to read
mapping information from the mapping file itself.
When the /IMAGE_FILE qualifier is specified without an optional
file name, PMDF will load the compiled configuration file PMDF_
CONFIG_DATA. If, instead, a file name is specified then that
file, which is expected to be a compiled configuration image,
will be loaded instead.
7.5.3 /MAPPING_FILE
/MAPPING_FILE=filename
This qualifier instructs TEST/MAPPING to use the specified
mapping file rather than the default mapping file, PMDF_MAPPING_
FILE.
This qualifier has no effect unless /NOIMAGE_FILE is specified
or no compiled configuration exists; use of any compiled
configuration will preclude reading any sort of mapping file.
7.5.4 /OPTION_FILE
/OPTION_FILE=filename
/NOOPTION_FILE
This qualifier instructs TEST/MAPPING to use the specified option
file rather than the default option file PMDF_OPTION_FILE.
This qualifier has no effect unless /NOIMAGE_FILE is specified
or no compiled configuration exists; use of any compiled
configuration will preclude reading any sort of option file.
Use of the qualifier /NOOPTION_FILE will prevent the file
PMDF_OPTION_FILE from being read in when there is no compiled
configuration.
7.5.5 /TABLE
/TABLE=table-name
This qualifier specifies the name of the mapping table to test.
If this qualifier is not specified, then TEST/MAPPING will prompt
for the name of a table to use.
7.6 – Examples
In the following example, the sample PAGER mapping is tested.
The /MAPPING_FILE qualifier is used to select the mapping file
PAGER_TABLE.SAMPLE instead of the default mapping file.
$ PMDF TEST/MAPPING/NOIMAGE/MAPPING_FILE=PMDF_TABLE:pager_table.sample
Enter table name: PAGER
Input string: H|From: "Daniel C. Newman"
<dan@example.com> (Doof City)
Output string: H|F:dan
Output flags: [0, 1, 2, 'Y' 89]
Input string: ^Z
$
8 /MATCH
Test a mapping wildcard pattern.
Syntax
PMDF TEST/MATCH
Command Qualifiers Defaults
None. None.
8.1 – Restrictions
None.
8.2 – Prompts
Pattern: mapping-pattern
Target: target-string
8.3 – Parameters
None.
8.4 – Description
TEST/MATCH may be used to test wildcard and glob matching, such
as in a mapping pattern.
When invoked, TEST/MATCH prompts for a pattern and then for a
target string to compare against the pattern, and will output
whether or not the target string matched and if it did match,
which characters in the target string matched which wildcard or
glob of the pattern. TEST/MATCH will loop, prompting for input,
until exitted with a CTRL/Z.
8.5 – Examples
In the following example, the sample mapping pattern
$[AX1]*@*.EXAMPLE.COM is tested for several sample target
strings.
$ PMDF TEST/MATCH
Pattern: $[ax1]*@*.example.com
[ 1S] cglob [1ax]
[ 2] "@"
[ 3S] glob, req 109, reps 2
[ 4] "."
[ 5] "a"
[ 6] "c"
[ 7] "m"
[ 8] "e"
[ 9] "."
[ 10] "c"
[ 11] "o"
[ 12] "m"
Target: xx11a@sys1.example.com
Match.
0 - xx11a
1 - sys1
Pattern: $[ax1]*@*.example.com
[ 1S] cglob [1ax]
[ 2] "@"
[ 3S] glob, req 109, reps 2
[ 4] "."
[ 5] "a"
[ 6] "c"
[ 7] "m"
[ 8] "e"
[ 9] "."
[ 10] "c"
[ 11] "o"
[ 12] "m"
Target: 12a@node.example.com
No match.
Pattern: $[ax1]*@*.example.com
[ 1S] cglob [1ax]
[ 2] "@"
[ 3S] glob, req 109, reps 2
[ 4] "."
[ 5] "a"
[ 6] "c"
[ 7] "m"
[ 8] "e"
[ 9] "."
[ 10] "c"
[ 11] "o"
[ 12] "m"
Target: 1xa@node.example.com
Match.
0 - 1xa
1 - node
Pattern: ^Z
$
9 /MHS
Test MHS channel address transformations.
Syntax
PMDF TEST/MHS [test-address|test-time]
Command Qualifiers Defaults
/822TOLAN /822TOLAN
/BACKWARD /FORWARD
/CHANNEL=channel-name /CHANNEL=mhs_local
/DEBUG /NODEBUG
/ENVELOPE /HEADER
/FORWARD /FORWARD
/HEADER /HEADER
/LANTO822 /822TOLAN
/TIME See text
9.1 – Restrictions
This utility is supplied only with the PMDF-LAN optional layered
product.
9.2 – Prompts
Address: test-address
Time: test-time
9.3 – Parameters
test-address
Optional address to test.
test-time
Optional time to test.
9.4 – Description
Test a MHS Mail channel's transformation of an address or time.
9.5 – Command Qualifiers
9.5.1 /822TOLAN
/822TOLAN (default)
/LANTO822
The testing process can test conversion of RFC 822 addresses to
MHS format, /822TOLAN, or test conversion of MHS format addresses
to RFC 822 format, /LANTO822.
9.5.2 /BACKWARD
/BACKWARD
/FORWARD (default)
The testing process can test conversion of backwards or forwards
pointing addresses; the default is forward pointing addresses.
9.5.3 /CHANNEL
/CHANNEL=channel-name
Different MHS channels may be configured to perform different
transformations. If this option is not specified, the default is
to test the mhs_local channel.
9.5.4 /DEBUG
/DEBUG
/NODEBUG (default)
The testing process is capable of producing detailed processing
information. The /DEBUG qualifier enables this output; it is
disabled by default.
9.5.5 /ENVELOPE
/ENVELOPE
/HEADER (default)
The testing process can test envelope or header addresses; the
default is header addresses.
9.5.6 /TIME
The testing process by default tests address transformations, but
the /TIME qualifier specifies that it should instead test time
transformations.
9.6 – Examples
$ PMDF TEST/MHS adam@mhs.example.com
ADAM@EXAMPLE
$ PMDF TEST/MHS postmaster@example.com
POSTMASTER@PMDF
$ PMDF TEST/MHS service@example.com
MAILER@PMDF {smtp:SERVICE@example.COM}
This example shows testing an mhs_local channel's
transformation of several addresses. The output shown
corresponds to a mhs_local channel with official host
name mhs.example.com and channel options MHS_DEFAULT_
WORKGROUP=EXAMPLE, MHS_GATEWAY_WORKGROUP=PMDF, MHS_GATEWAY_
USERNAME=MAILER, and MHS_GATEWAY_TYPE=SMTP, and where the site
has example.com as the official local host name.
10 /REWRITE
Test address rewriting specified by a PMDF configuration
Syntax
PMDF TEST/REWRITE [test-address[,...]]
Command Qualifiers Defaults
/ALIAS_FILE=file-spec /ALIAS_FILE=PMDF_ALIAS_FILE
/CHANNEL /CHANNEL
/CHECK_EXPANSIONS /NOCHECK_EXPANSIONS
/CONFIGURATION_FILE=file-spec /CONFIGURATION_FILE=PMDF_CONFIG_FILE
/DATABASE=database-list See text
/DEBUG /NODEBUG
/DELIVERY_RECEIPT See text
/DESTINATION_CHANNEL=channel None
/FILTER /NOFILTER
/FROM=address /FROM=postmaster@localhost
/GREY=setting /GREY=0
/IMAGE_FILE=file-spec /IMAGE_FILE=PMDF_CONFIG_DATA
/LOCAL_ALIAS=value None
/MAPPING_FILE=file-spec /MAPPING_FILE=PMDF_MAPPING_FILE
/OPTION_FILE=file-spec /OPTION_FILE=PMDF_OPTION_FILE
/READ_RECEIPT See text
/REPROCESSING /REPROCESSING
/RESTRICTED=setting /RESTRICTED=0
/SOURCE_CHANNEL=channel /SOURCE_CHANNEL=L
10.1 – Restrictions
None.
10.2 – Prompts
Address: test-address[,...]
10.3 – Parameters
test-address
Optional parameter specifying one or more addresses to rewrite.
10.4 – Description
TEST/REWRITE provides a straightforward test facility for
examining PMDF's address rewriting and channel mapping process
without actually sending any message. Various qualifiers can be
used to control whether TEST/REWRITE uses the configuration text
files or the compiled configuration (if present), the amount of
output produced, and so on.
If one or more test addresses are specified on the command
line, TEST/REWRITE applies PMDF address rewriting to those
addresses, reports the results, and exits. If no test address
is specified TEST/REWRITE will enter a loop, prompting for
addresses, rewriting them, and prompting again for more
addresses. TEST/REWRITE will exit when a CTRL/Z is entered.
When testing rewriting of a alias corresponding to a mailing list
which has an AUTH_ or CANT_ type of named parameter controlling
who is authorized to post to the list, or when testing rewriting
when SEND_ACCESS or related mapping tables are in effect, note
that by default TEST/REWRITE uses as the posting address the
return address of the local postmaster as specified by the
RETURN_ADDRESS option in the PMDF option file. To specify a
different posting address for the rewriting process, use the
/FROM qualifier.
10.5 – Command Qualifiers
10.5.1 /ALIAS_FILE
/ALIAS_FILE=filename
TEST/REWRITE normally consults the default alias file PMDF_ALIAS_
FILE during the rewriting process. The /ALIAS_FILE qualifier
specified an alternate file for TEST/REWRITE to use.
This qualifier has no effect unless /NOIMAGE_FILE is specified
or no compiled configuration exists; use of any compiled
configuration precludes reading any sort of alias file.
10.5.2 /CHANNEL
/CHANNEL (default)
/NOCHANNEL
This qualifier controls whether the utility outputs detailed
information, e.g., channel flags, regarding the channel an
address matches.
10.5.3 /CHECK_EXPANSIONS
/CHECK_EXPANSIONS
/NOCHECK_EXPANSIONS (default)
This qualifier controls checking of alias address expansion.
Normally PMDF considers the expansion of an alias to have been
successful if any of the addresses the alias expands to are
legal. The /CHECK_EXPANSIONS qualifier causes a much stricter
policy to be applied; TEST/REWRITE checks each expanded address
in detail and reports a list of any addresses, expanded or
otherwise, that fail to rewrite properly. For addresses that
match the L channel, PMDF also performs validity checks.
10.5.4 /CONFIGURATION_FILE
/CONFIGURATION_FILE=filename
TEST/REWRITE normally consults the default configuration
file PMDF_CONFIG_FILE during the rewriting process. The
/CONFIGURATION_FILE qualifier specifies an alternate file to
use in place of the file PMDF_CONFIG_FILE.
This qualifier has no effect unless /NOIMAGE_FILE is specified
or no compiled configuration exists; use of any compiled
configuration will preclude reading any sort of configuration
file.
10.5.5 /DEBUG
/DEBUG
/NODEBUG (default)
The address rewriting process is capable of producing additional,
detailed explanations of what actions are taken and why. The
/DEBUG qualifier enables this output; it is disabled by default.
10.5.6 /DATABASE
/DATABASE=database-list
TEST/REWRITE normally consults the usual PMDF databases
during its operation. This qualifier is used to either disable
references to various databases or to redirect the database paths
to nonstandard locations.
The allowed list items are ALIAS, NOALIAS, PERSONAL_ALIAS,
NOPERSONAL_ALIAS, DOMAIN, NODOMAIN, FORWARD, NOFORWARD, GENERAL,
NOGENERAL, REVERSE, and NOREVERSE. The list items beginning with
"NO" disable use of the corresponding database. The remaining
items require an associated value, which is taken to be the name
of that database.
10.5.7 /DELIVERY_RECEIPT
/DELIVERY_RECEIPT
/NODELIVERY_RECEIPT
The /DELIVERY_RECEIPT and /NODELIVERY_RECEIPT qualifiers, which
explicitly set the corresponding receipt request flags, can
be useful when testing the handling of receipt requests when
rewriting forwarded addresses or mailing lists.
10.5.8 /DESTINATION_CHANNEL
/DESTINATION_CHANNEL=channel
The /DESTINATION_CHANNEL qualifier controls what destination or
target channel TEST/REWRITE rewrites addresses for. Some address
rewriting is destination channel specific; this qualifier allows
control of the assumed destination channel.
10.5.9 /FILTER
/FILTER
/NOFILTER (default)
The /FILTER qualifier may be used to have PMDF TEST/REWRITE
output any filters (personal mailbox, channel, or system)
applying for the address in question.
10.5.10 /FROM
/FROM=address
/NOFROM
This qualifier controls what envelope From: address is used for
access control probes and mailing list access probes. If the
/FROM qualifier is omitted, then the address used for access
checks is the postmaster return address. Specifying either
/FROM=<> or /NOFROM tells the utility to use an empty envelope
From: address for access checks.
10.5.11 /GREY
/GREY=setting
/NOGREY (default)
This qualifier controls the setting of the Grey Book flag. By
default, this flag has value 0. When set to 1, /GREY=1, the Grey
Book flag will be set on and addresses will be rewritten using
the Grey Book format.
This flag is used to force rewriting of address in accordance
with the JANET (Grey Book) specifications. The most significant
effect is that domain specifications appear in reverse order,
e.g., edu.claremont.ymir and not ymir.claremont.edu. See the PMDF
System Manager's Guide for further details.
Grey Book address formats are not currently used in PMDF, so this
qualifier's usefulness is problematic at best.
10.5.12 /IMAGE_FILE
/IMAGE_FILE[=filename]
/NOIMAGE_FILE
The /IMAGE_FILE qualifier serves two purposes. The first is
when /NOIMAGE_FILE is specified; this instructs TEST/REWRITE
to ignore any compiled configuration unconditionally and to read
configuration information from the various text files instead.
When the /IMAGE_FILE qualifier is specified without an optional
file name, PMDF TEST/REWRITE will load the compiled configuration
from the file PMDF_CONFIG_DATA. If, instead, a file name is
specified then TEST/REWRITE will load the compiled configuration
from the specified file.
10.5.13 /LOCAL_ALIAS
/LOCAL_ALIAS=value
/NOLOCAL_ALIAS (default)
This qualifier controls the setting of an alias for the local
host. PMDF supports multiple "identities" for the local host;
the local host may have a different identity on each channel.
This qualifier may be used to set the local host alias to the
specified value; appearances of the local host in rewritten
addresses will be replaced by this value.
10.5.14 /MAPPING_FILE
/MAPPING_FILE[=filename]
/NOMAPPING_FILE
This qualifier instructs TEST/REWRITE to use the specified
mapping file rather than the default mapping file named by the
PMDF_MAPPING_FILE logical name, usually PMDF_TABLE:MAPPINGS.
This qualifier has no effect unless /NOIMAGE_FILE was specified
or no compiled configuration exists; use of any compiled
configuration will preclude reading the mapping file.
Use of the /NOMAPPING_FILE qualifier will prevent the PMDF_
MAPPING_FILE file from being read in when there is no compiled
configuration.
10.5.15 /OPTION_FILE
/OPTION_FILE=filename
/NOOPTION_FILE
This qualifier instructs TEST/REWRITE to use the specified option
file rather than the default option file PMDF_OPTION_FILE.
This qualifier has no effect unless /NOIMAGE_FILE is specified
or no compiled configuration exists; use of any compiled
configuration will preclude reading any sort of option file.
Use of the qualifier /NOOPTION_FILE will prevent the file
PMDF_OPTION_FILE from being read in when there is no compiled
configuration.
10.5.16 /READ_RECEIPT
/READ_RECEIPT
/NOREAD_RECEIPT
The /READ_RECEIPT and /NOREAD_RECEIPT qualifiers, which
explicitly set the corresponding receipt request flags, can
be useful when testing the handling of receipt requests when
rewriting forwarded addresses or mailing lists.
10.5.17 /REPROCESSING
/REPROCESSING (default)
/NOREPROCESSING
This qualifier allows the utility to display the contents of a
mailing list which uses the [REPROCESS] named parameter in its
alias definition.
10.5.18 /RESTRICTED
/RESTRICTED=value
/NORESTRICTED
This qualifier controls the setting of the restricted flag. By
default, this flag has value 0. When set to 1, /RESTRICTED=1, the
restricted flag will be set on and addresses will be rewritten
using the restricted mailbox encoding format recommend by
RFC1137.
This flag is used to force rewriting of address mailbox names in
accordance with the RFC1137 specifications; see the PMDF System
Manager's Guide for further details.
10.5.19 /SOURCE_CHANNEL
/SOURCE_CHANNEL=channel
The /SOURCE_CHANNEL qualifier controls what source channel to
rewrite addresses for. Some address rewriting is source channel
specific; TEST/REWRITE normally pretends that the channel source
it is rewriting for is the local channel, L.
10.6 – Examples
This example shows the typical output generated by
TEST/REWRITE. Perhaps the single most important piece of
information generated by TEST/REWRITE is the last few lines
of the TEST/REWRITE output, 6, which give the channel to
which TEST/REWRITE would submit a message with the specified
test address and the form in which the test address would be
rewritten for that channel. This output is invaluable when
debugging configuration problems.
$ PMDF TEST/REWRITE DAN@EXAMPLE.COM
forward channel = tcp_local
channel description =
channel user filter =
dest channel filter =
source channel filter =
channel flags #0 = BIDIRECTIONAL SINGLE_SYSTEM IMMNORMAL NOSERVICEALL
channel flags #1 = SMTP RANDOMMX MAYTLS DEFAULT
channel flags #2 = NOLOCALPOST POSTHEADBODY HEADERINC NOEXPROUTE
channel flags #3 = LOGGING NOGREY NORESTRICTED
channel flags #4 = EIGHTNEGOTIATE NOHEADERTRIM NOHEADERREAD RULES
channel flags #5 = MASTER_DEBUG
channel flags #6 = LOCALUSER REPORTHEADER
channel flags #7 = SWITCHCHANNEL NOREMOTEHOST DATEFOUR DAYOFWEEK
channel flags #8 = NODEFRAGMENT EXQUOTA REVERSE NOCONVERT_OCTET_STREAM
channel flags #9 = NOTHURMAN INTERPRETENCODING INCLUDEFINAL RECEIVEDFROM
linelength = 998
addrsperfile = 127
channel env addr type = SOURCEROUTE
channel hdr addr type = SOURCEROUTE
channel official host = TCP-DAEMON
channel local alias =
channel queue name = MAIL_TCP_BATCH
channel after param = 60
channel daemon name = fw.example.com
channel user name =
urgentnotices = 1 4 8 12
normalnotices = 1 4 8 12
nonurgentnotices = 1 4 8 12
channel rightslist ids =
backward channel = tcp_local
header To: address = DAN@EXAMPLE.COM
header From: address = DAN@EXAMPLE.COM
envelope To: address = DAN@EXAMPLE.COM (route (TCP-DAEMON,TCP-DAEMON))
envelope From: address = DAN@EXAMPLE.COM
name =
mbox = DAN
Extracted address action list:
DAN@EXAMPLE.COM
Extracted 733 address action list:
DAN@EXAMPLE.COM
Address list expansion: