Cisco Cisco Email Security Appliance C190 사용자 가이드
Chapter 16 Enabling Your C300D/C350D/C360D Appliance
16-540
Cisco IronPort AsyncOS 7.1 for Email Configuration Guide
OL-22158-02
•
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.
recipient, users can achieve orders-of- magnitude, better use of queue storage
on the C300D appliance.
Using the Mail Merge
SMTP Injection
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.
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
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.
need to be issued in a particular sequence.
Step 1
The initial EHLO statement, identifying the sending host.
Step 2
Each message starts with an XMRG FROM: statement, indicating the sender
address.
address.
Step 3
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.
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.
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.