Cisco Cisco Email Security Appliance C680 User Guide

Queue storage efficiency. By storing less information for each message 
recipient, users can achieve orders-of- magnitude, better use of queue storage 
on the C300D appliance.

IPMM extends SMTP as the transport protocol. There is no special configuration 
that needs to be made to the IronPort C300D appliance. (By default, IPMM can 
be enabled for private listeners and disabled for public listeners on the IronPort 
C300D Email Security appliance.) However, if you are not currently using SMTP 
as your injection protocol, you must create a new private listener that utilizes 
SMTP through the IronPort C300D appliance interface. 

Refer to the “Customizing Listeners” chapter in the Cisco IronPort AsyncOS for 
Email Advanced Configuration Guide for more information on configuring 
listeners. Use the 

setipmm

 subcommand of 

listenerconfig

 to enable IPMM on 

the injector. 

IPMM modifies SMTP by altering two commands — 

MAIL FROM

 and 

DATA

 — and 

adding another: 

XDFN

. The 

MAIL FROM

 command is replaced with 

XMRG FROM

 and, 

the 

DATA

 command is replaced with 

XPRT

. 

To generate a Mail Merge message, the commands used to generate the message 
need to be issued in a particular sequence.

The initial EHLO statement, identifying the sending host.

Each message starts with an XMRG FROM: statement, indicating the sender 
address.

Each recipient is then defined:

One or more XDFN variable allocation statements are made, including 
defining the parts (XDFN *PART=1,2,3…), and any other recipient 
specific variables.

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.