Cisco Cisco Email Security Appliance X1050 Guía Del Usuario
16-6
Cisco IronPort AsyncOS 7.6 for Email Configuration Guide
OL-25136-01
Chapter 16 Enabling Your C350D Appliance
•
The recipient email address is defined with the RCPT TO: statement. Any variable allocations
prior to the RCPT TO:, but after the prior XMRG FROM, or RCPT TO command, will be
mapped to this recipient email address.
prior to the RCPT TO:, but after the prior XMRG FROM, or RCPT TO command, will be
mapped to this recipient email address.
4.
Each part is defined using the XPRT n command, with each part terminated by a period (.) character
similar to the DATA command. The last part is defined by the XPRT n LAST command.
similar to the DATA command. The last part is defined by the XPRT n LAST command.
Variable Substitution
Any part of the message body, including message headers, can contain variables for substitution.
Variables can appear in HTML messages, as well. Variables are user-defined and must begin with the
ampersand (
Variables can appear in HTML messages, as well. Variables are user-defined and must begin with the
ampersand (
&
) character and end with the semi-colon character (
;
). Variable names beginning with an
asterisk (
*
) are reserved and cannot be used.
Reserved Variables
IPMM contains five special “reserved” variables that are predefined.
For example, the following example message body (including headers) contains four distinct variables
and five substitution locations that will be replaced in the final message. Note that the same variable may
be used more than once in the message body. Also, the reserved variable
and five substitution locations that will be replaced in the final message. Note that the same variable may
be used more than once in the message body. Also, the reserved variable
&*TO;
is used, which will be
replaced with the recipient email address. This reserved variable does not need to be passed in as a
separate variable. The variables in the example appear in bold.
separate variable. The variables in the example appear in bold.
Table 16-2
IPMM: Reserved Variables
*FROM
The reserved variable *FROM is derived from the “Envelope From” parameter. The
“Envelope From” parameter is set by the “XMRG FROM:” command.
“Envelope From” parameter is set by the “XMRG FROM:” command.
*TO
The reserved variable *TO is derived from the envelope recipient value, as set by the
“RCPT TO:” command.
“RCPT TO:” command.
*PARTS
The reserved variable *PARTS holds a comma separated list of parts. It is set prior to
defining a recipient with the “RCPT TO:” and determines which of the “XPRT n”
message body blocks a given user will receive.
defining a recipient with the “RCPT TO:” and determines which of the “XPRT n”
message body blocks a given user will receive.
*DATE
The reserved variable *DATE is replaced with the current date stamp.
*DK
The reserved variable
*DK
is used to specify a DomainKeys Signing profile (this
profile must already exist in AsyncOS). For more information about creating
DomainKeys Signing profiles, see the “Email Authentication” chapter in Cisco
IronPort AsyncOS for Email Advanced Configuration Guide.
DomainKeys Signing profiles, see the “Email Authentication” chapter in Cisco
IronPort AsyncOS for Email Advanced Configuration Guide.