Cisco Cisco Email Security Appliance C170 사용자 가이드
5-9
Cisco IronPort AsyncOS 7.6 for Email Configuration Guide
OL-25136-01
Chapter 5 Configuring the Gateway to Receive Email
Note
You can also configure AsyncOS to perform this rejection at the message recipient level (RCPT
TO), rather than at the start of the SMTP conversation. Rejecting messages in this way delays
the message rejection and bounces the message, allowing AsyncOS to retain more detailed
information about the rejected messages. This setting is configured from the CLI
TO), rather than at the start of the SMTP conversation. Rejecting messages in this way delays
the message rejection and bounces the message, allowing AsyncOS to retain more detailed
information about the rejected messages. This setting is configured from the CLI
listenerconfig --> setup
command. For more information, see “Customizing Listeners” in
the Cisco IronPort AsyncOS for Email Advanced Configuration Guide.
Step 3
TCPREFUSE
Connection is refused at the TCP level.
Step 4
RELAY
Connection is accepted. Receiving for any recipient is allowed and is not constrained by the
Recipient Access Table.
Recipient Access Table.
•
CONTINUE
The mapping in the HAT is ignored, and processing of the HAT continues. If the incoming
connection matches a later entry that is not CONTINUE, that entry is used instead. The CONTINUE
rule is used to facilitate the editing of the HAT in the Graphical User Interface (GUI). For more
information, see
connection matches a later entry that is not CONTINUE, that entry is used instead. The CONTINUE
rule is used to facilitate the editing of the HAT in the Graphical User Interface (GUI). For more
information, see
.
In addition to these basic access control parameters, the following parameters are available for listeners
you create. Parameters combined with an access rule (ACCEPT or REJECT) are called mail flow
policies. A mail flow policy is a way of expressing a group of HAT parameters (access rule, followed by
connection parameters, rate limiting parameters, custom SMTP codes and responses, and anti-spam,
anti-virus, encryption, and authentication parameters).
you create. Parameters combined with an access rule (ACCEPT or REJECT) are called mail flow
policies. A mail flow policy is a way of expressing a group of HAT parameters (access rule, followed by
connection parameters, rate limiting parameters, custom SMTP codes and responses, and anti-spam,
anti-virus, encryption, and authentication parameters).
Mail flow policies are then mapped to sender groups as entries in a listener’s HAT.
Table 5-3
HAT Mail Flow Policy Parameters
Parameter
Description
Connections
Maximum message size
The maximum size of a message that will be accepted by this listener.
The smallest possible maximum message size is 1 kilobyte.
The smallest possible maximum message size is 1 kilobyte.
Maximum concurrent
connections from a single IP
connections from a single IP
The maximum number of concurrent connections allowed to connect to
this listener from a single IP address.
this listener from a single IP address.
Maximum messages per
connection
connection
The maximum number of messages that can be sent through this listener
per connection from a remote host.
per connection from a remote host.
Maximum recipients per
message
message
That maximum number of recipients per message that will be accepted
from this host.
from this host.
SMTP Banner
Custom SMTP Banner Code
The SMTP code returned when a connection is established with this
listener.
listener.
Custom SMTP Banner Text
The SMTP banner text returned when a connection is established with
this listener.
this listener.
Custom SMTP Reject Banner
Code
Code
The SMTP code returned when a connection is rejected by this listener.
Custom SMTP Reject Banner
Text
Text
The SMTP banner text returned when a connection is rejected by this
listener.
listener.