TCP/IP Configuration and Management Manual

Configuring the NonStop TCP/IP Subsystem
TCP/IP Configuration and Management Manual—427132-004
3-54
Simple Mail Transfer Protocol (SMTP)
RFC 819 describes the specifics of domain-based addressing. These specifics are
briefly described in RFC 822 as well. Essentially, each host is given a name that is a
right-to-left, dot-qualified pseudo-path from a distinguished root. The elements of the
path need not be physical hosts; the domain is logical. For example, at BigCityU one
legal host may be a.CC.BigCityU.EDU; reading from right to left, EDU is a top-level
domain comprising educational institutions, BigCityU is a logical domain name, CC
represents the Computer Center (in this case a strictly logical entity), and a is a specific
host in the Computer Center.
Errors in Configuration Files
In normal operation of the SMTPSND and SMTPRCV processes, errors found in the
configuration file are silently ignored. However, you can verify the address rewriting
mechanism of the configuration file by using the SMTPRCV for testing, as follows:
RUN $SYSTEM.ZTCPIP.SMTPRCV -bt -Cconfiguration-file
The -bt flag tells the SMTPRCV that being used to test the configuration file specified
by -C configuration-file. The default SMTP configuration file
$SYSTEM.ZTCPIP.SMTPCONF is tested if a different file is not specified. This
command prints any errors that are present in the configuration file you specify.
If the configuration file contains no errors, you are prompted for the rule set to use and
an input address to be parsed.
ADDRESS TEST MODE
Enter <ruleset> <address>
>
Enter a line similar to the following:
> 0 [e-mail]
This entry specifies that rule set 0 is to be applied to the address [e-mail] after
it is parsed.
Examples of Address Parsing
Rule set three is always applied first. Rule set three should turn the address into
canonical form which have the following basic syntax:
local-part@host-domain-spec
Rule set zero is applied after rule set three to addresses that actually specify
recipients. The address must resolve to {mailer, host, user}. You must define the mailer
in the mailer definitions from the configuration file.
The parsing rules are applied as follows:
rule set 3 input: "user" "@" "sun" "." "kci"
rule set 8 input: "user" "@" "sun" "." "kci"
rule set 8 returns: "user" "@" "sun" "." "kci"
rule set 6 input: "user" "<" "@" "sun" "." "kci" ">"
rule set 6 returns: "user" "<" "@" "sun" "." "kci" ">"