The following examples show how the header rewriting rules affect
an SMTP mail header. The example site is not a secure gateway and
is configured as follows:
TCPHostName = mvs1.acme.com
ShortTCPHostName = mvs1
AltTCPHostName = seeds.acme.com
NJEHostName = mvs1
NJEDomain = acmenet
AltNJEDomain = centralnet
Note that the above keywords
are configured according to the definitions found in
Predefined keywords within the SMTP rules (for example,
from TCPIP.DATA). In addition, assume that the following hosts are
known to be other NJE hosts:
bird
iron
Then the following header:
From: abc@mvs1 (Brendan Beeper)
To: Jenny Bird <def@bird>
Cc: ghi@iron.acmenet, j@mvs1,
k@seeds.acme.com,
Mailing List <owner@acmenet>,
lmno@iron.centralnet
Subject: New Ore
is rewritten by the default header rewriting rules as:
From: abc@mvs1.acme.com (Brendan Beeper)
To: Jenny Bird <def%bird.acmenet@mvs1.acme.com>
Cc: ghi%iron.acmenet@mvs1.acme.com, j@mvs1.acme.com,
k@mvs1.acme.com,
Mailing List <owner%acmenet@mvs.acme.com>,
lmno%iron.acmenet@mvs1.acme.com
Subject: New Ore
The next example deviates from the defaults listed in
Default SMTP rules. On the configuration
for nonsecure gateways, if you change the rule before the 2 ENDIFs
to:
A '@' AnyNJEHostName '.' AltNJEDomain =>
'<@' TCPHostName ':' A '@' AnyNJEHostName '.' NJEDomain '>';
then
the last address in the Cc: field within our header is rewritten as:
Cc: <@mvs1.acme.com:lmno@iron.acmenet>
Note: Do
not make the change shown in the previous example; it is intended
only as a demonstration of the capabilities of the pattern-matching
language.