Cisco Cisco Email Security Appliance C650 Guía Del Usuario
21-16
Cisco AsyncOS 8.0 for Email User Guide
Chapter 21 Configuring Routing and Delivery Features
Configuring Masquerading
Note
The Masquerading feature is configured on a per-listener basis, as opposed to the Alias Tables
functionality, which is configured for the entire system.
functionality, which is configured for the entire system.
Note
A listener checks the masquerading table for matches and modifies the recipients while the message is
in the work queue, immediately after LDAP recipient acceptance queries and before LDAP routing
queries. Refer to “Understanding the Email Pipeline” in the Cisco IronPort AsyncOS for Email
Configuration Guide.
in the work queue, immediately after LDAP recipient acceptance queries and before LDAP routing
queries. Refer to “Understanding the Email Pipeline” in the Cisco IronPort AsyncOS for Email
Configuration Guide.
The Masquerading feature actually rewrites addresses for the Envelope Sender and the To:, From:, and
CC: fields of the email that has been received. You can specify different masquerading parameters for
each listener you create in one of two ways:
CC: fields of the email that has been received. You can specify different masquerading parameters for
each listener you create in one of two ways:
•
via a static table of mappings you create
•
via an LDAP query.
This section discusses the static table method. The table format is forward-compatible with the
/etc/mail/genericstable
feature of a sendmail configuration on some Unix systems. See
for more information on LDAP masquerading queries.
Masquerading and altsrchost
Generally, the masquerading feature rewrites the Envelope Sender, and any subsequent actions to be
performed on the message will be “triggered” from the masqueraded address. However, when you run
the
performed on the message will be “triggered” from the masqueraded address. However, when you run
the
altscrchost
command from the CLI, the altsrchost mappings are triggered from the original address
(and not the modified, masqueraded address).
For more information, see
and
.
Configuring Static Masquerading Tables
You configure the static masquerading table of mappings by using the
edit -> masquerade
subcommand of the
listenerconfig
command. Alternatively, you can import a file containing the
mappings. See
. The subcommand creates and maintains a
table that maps input addresses, usernames, and domains to new addresses and domains. See
for more information on LDAP masquerading queries.
When messages are injected into the system, the table is consulted, and the message is rewritten if a
match in the header is found.
match in the header is found.
A domain masquerading table is constructed as follows:
Table 21-3
Masquerading Table Syntax
Left-hand Side (LHS)
Separator
Right-hand Side (RHS)
a list of one or more usernames and/or
domains to match
domains to match
whitespace (space or tab
character)
character)
the rewritten username and/or
domain
domain