Cisco Cisco Email Security Appliance C170 Guía Del Usuario
Chapter 4 Understanding the Email Pipeline
4-6
Cisco IronPort AsyncOS 7.5 for Email Configuration Guide
OL-25136-01
Sender Groups are used to associate one or more senders into groups, upon which
you can apply message filters, and other Mail Flow Policies. Mail Flow Policies
are a way of expressing a group of HAT parameters (access rule, followed by rate
limit parameters and custom SMTP codes and responses).
you can apply message filters, and other Mail Flow Policies. Mail Flow Policies
are a way of expressing a group of HAT parameters (access rule, followed by rate
limit parameters and custom SMTP codes and responses).
Together, sender groups and mail flow policies are defined in a listener’s HAT.
Host DNS verification settings for sender groups allow you to classify unverified
senders prior to the SMTP conversation and include different types of unverified
senders in your various sender groups.
senders prior to the SMTP conversation and include different types of unverified
senders in your various sender groups.
While the connecting host was subject to Host DNS verification in sender groups
— prior to the SMTP conversation — the domain portion of the envelope sender
is DNS verified in mail flow policies, and the verification takes place during the
SMTP conversation. Messages with malformed envelope senders can be ignored.
You can add entries to the Sender Verification Exception Table — a list of
domains and email addresses from which to accept or reject mail despite envelope
sender DNS verification settings.
— prior to the SMTP conversation — the domain portion of the envelope sender
is DNS verified in mail flow policies, and the verification takes place during the
SMTP conversation. Messages with malformed envelope senders can be ignored.
You can add entries to the Sender Verification Exception Table — a list of
domains and email addresses from which to accept or reject mail despite envelope
sender DNS verification settings.
Reputation Filtering allows you to classify email senders and restrict access to
your email infrastructure based on sender’s trustworthiness as determined by the
Cisco IronPort SenderBase Reputation Service.
your email infrastructure based on sender’s trustworthiness as determined by the
Cisco IronPort SenderBase Reputation Service.
For more information, see
.
Received: Header
Using the
listenerconfig
command, you can configure a listener to not include
the Received: header by default to all messages received by the listener.
For more information, see “Advanced Configuration Options” in the
“Customizing Listeners” chapter of the Cisco IronPort AsyncOS for Email
Advanced Configuration Guide.
“Customizing Listeners” chapter of the Cisco IronPort AsyncOS for Email
Advanced Configuration Guide.
Default Domain
You can configure a listener to automatically append a default domain to sender
addresses that do not contain fully-qualified domain names; these are also known
as “bare” addresses (such as “joe” vs. “joe@example.com”).
addresses that do not contain fully-qualified domain names; these are also known
as “bare” addresses (such as “joe” vs. “joe@example.com”).