User Guide

24-19
AsyncOS 9.1.2 for Cisco Email Security Appliances User Guide
Chapter 24 Configuring Routing and Delivery Features
Configuring Masquerading
Sample Masquerading Table for a Private Listener
Importing a Masquerading Table
A traditional sendmail /etc/mail/genericstable file can be imported. To import a genericstable file,
first see Appendix A, “FTP, SSH, and SCP Access” to ensure that you can access the appliance.
Place the
genericstable file in the configuration directory, and then use the import subcommand of the
masquerade subcommand to upload the file. Use the commands in this order:
listenerconfig -> edit -> listener_number -> masquerade -> import
Alternatively, you can use the export subcommand to download the existing configuration. A file
(whose name you specify) will be written to the configuration directory. You can modify this file outside
of the CLI and then import it again.
When you use the
import subcommand, ensure that the file contains only valid entries. If there is an
invalid entry (for example, a left-hand side with no right-hand side), the CLI reports syntax errors when
you import the file. If there is a syntax error during import, no mappings in the entire file are imported.
Remember to issue the
commit command after you import a genericstable file so that the configuration
changes for the listener take effect.
Example Masquerading
In this example, the masquerade subcommand of listenerconfig is used to construct a domain
masquerading table for the private listener named “OutboundMail” on the PrivateNet interface.
First, the option to use LDAP for masquerading is declined. (For information on configuring LDAP
masquerading queries, see See Chapter 25, “LDAP Queries” for more information on LDAP
masquerading queries.)
Then, a partial domain notation of
@.example.com is mapped to @example.com so that any email sent
from any machine in the subdomain of
.example.com will be mapped to example.com. Then, the
username
joe is mapped to the domain [e-mail]. The domain masquerading table is then
printed to confirm both entries, and then exported to a file named
masquerade.txt. The config
subcommand is used to disable re-writing addresses in the CC: field, and finally, the changes are
committed.
# sample Masquerading file
@.example.com @example.com # Hides local subdomains in the header
sales [e-mail]
@techsupport [e-mail]
user@localdomain [e-mail]
ALL @bigsender.com
mail3.example.com> listenerconfig
Currently configured listeners: