Cisco Cisco Email Security Appliance C160 Mode D'Emploi

Ease of use for the mail administrator. The complexities of creating personalized messages for each 
recipient are removed, as IPMM provides variable substitution and an abstracted interface in many 
common languages.

Reduced load on message generation systems. By requiring one copy of the message body and a 
table of required substitutions, most of the message generation “work” is off-loaded from message 
generation systems and moved to the appliance that is configured for optimized outbound mail 
delivery.

Increased delivery throughput. By reducing the resources necessary to accept and queue thousands 
of incoming messages, the appliance can significantly increase out-bound delivery performance.

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

IPMM extends SMTP as the transport protocol. There is no special configuration that needs to be made 
to the appliance. (By default, IPMM can be enabled for private listeners and disabled for public listeners 
on the D-Mode-enabled 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 D-Mode enabled 
appliance interface. 

Use the 

setipmm

 subcommand of 

listenerconfig

 to enable IPMM on the listener. For more 

information, see 

 

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.

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.