Cisco Cisco Email Security Appliance C650 Guía Del Usuario
16-9
Cisco IronPort AsyncOS 7.6 for Email Configuration Guide
OL-25136-01
Chapter 16 Enabling Your C350D Appliance
XDFN
Syntax:
XDFN
<
KEY
=
VALUE
>
[
KEY=VALUE
]
The
XDFN
command sets the per-recipient metadata. Note that key-value pairs can optionally be enclosed
in angle brackets or square brackets.
*PARTS
is a special reserved variable that indicates the index number as defined by the
XPRT
command
(described below). The
*PARTS
variable is split as a comma-delimited list of integers. The integers match
the body parts to be sent as defined by the
XPRT
commands. The other reserved variables are:
*FROM
,
*TO
,
and
*DATE
.
XPRT
Syntax:
The
XPRT
command replaces the SMTP
DATA
command. The command accepts the transfer of the
message part after the command is issued. The command is completed with a single period on a line
followed by a return (which is the same way an SMTP
followed by a return (which is the same way an SMTP
DATA
command is completed).
The special keyword
LAST
indicates the end of the mail merge job and must be used to specify the final
part that will be injected.
After the
LAST
keyword is used, the message is queued, and delivery begins.
Notes on Defining Variables
•
When you define variables with the
XDFN
command, note that the actual command line cannot exceed
the physical limit of the system. In the case of the Cisco IronPort C350D appliance, this limit is 4
kilobytes per line. Other host systems may have lower thresholds. Use caution when defining
multiple variables on very large lines.
kilobytes per line. Other host systems may have lower thresholds. Use caution when defining
multiple variables on very large lines.
•
You can escape special characters using the forward slash “
/
” character when defining variables
key-value pairs. This is useful if your message body contains HTML character entities that might be
mistakenly replaced with variable definitions. (For example, the character entity
mistakenly replaced with variable definitions. (For example, the character entity
™
defines the
HTML character entity for a trademark character. If you created the command
XDFN trade=foo
and
then created a IPMM message containing the HTML character entity “
™
” the assembled
message would contain the variable substitution (“
foo
”) instead of the trademark character. The
same concept is true for the ampersand character “&” which is sometimes used in URLs containing
GET commands.
GET commands.
Example IPMM Conversation
The following is an example IPMM conversation of Example Message #2 (shown above). The message
will be sent to two recipients in this example: “Jane User” and “Joe User.”
will be sent to two recipients in this example: “Jane User” and “Joe User.”
XPRT index_number LAST
Message
.