User Guide

41-9
AsyncOS 9.1.2 for Cisco Email Security Appliances User Guide
Chapter 41 Optimizing the Appliance for Outbound Mail Delivery Using D-Mode
Sending Bulk Mail Using IronPort Mail Merge (IPMM)
• 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
™ 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.
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.”
In this example, the type in
bold represents what you would type in a manual SMTP conversation with
the D-Mode-enabled appliance, type in
monospaced type represents the responses from the SMTP
server, and italic type represents comments or variables.
A connection is established:
The conversation is started:
Variables and parts are set for each recipient:
220 ESMTP
EHLO foo
250-ehlo responses from the listener enabled for IPMM
XMRG FROM:<[e-mail]> [Note: This replaces the MAIL FROM: SMTP command.]
250 OK
XDFN first_name="Jane" last_name="User" color="red" *PARTS=1,2
[Note: This line defines three variables (first_name, last_name, and color) and then
uses the *PARTS reserved variable to define that the next recipient defined will receive
message parts numbers 1 and 2.]
250 OK
RCPT TO:<[e-mail]>
250 recipient <[e-mail]> ok
XDFN first_name="Joe" last_name="User" color="black" *PARTS=1
[Note: This line defines three variables (first_name, last_name, and color) and then
uses the *PARTS reserved variable to define that the next recipient defined will receive
message parts numbers 1 only.]