27.11.2012 Views

IronPort - advanced configuration guide

IronPort - advanced configuration guide

IronPort - advanced configuration guide

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Chapter 2 Configuring Routing and Delivery Features<br />

Sample Masquerading Table for a Private Listener<br />

Importing a Masquerading Table<br />

Example Masquerading<br />

OL-25137-01<br />

# sample Masquerading file<br />

@.example.com @example.com # Hides local subdomains in the header<br />

sales sales_team@success.com<br />

@techsupport tech_support@biggie.com<br />

user@localdomain user@company.com<br />

ALL @bigsender.com<br />

A traditional sendmail /etc/mail/genericstable file can be imported. To import a genericstable file,<br />

first see Appendix B, “Accessing the Appliance” to ensure that you can access the appliance.<br />

Place the genericstable file in the <strong>configuration</strong> directory, and then use the import subcommand of the<br />

masquerade subcommand to upload the file. Use the commands in this order:<br />

listenerconfig -> edit -> injector_number -> masquerade -> import<br />

Alternatively, you can use the export subcommand to download the existing <strong>configuration</strong>. A file<br />

(whose name you specify) will be written to the <strong>configuration</strong> directory. You can modify this file outside<br />

of the CLI and then import it again.<br />

When you use the import subcommand, ensure that the file contains only valid entries. If there is an<br />

invalid entry (for example, a left-hand side with no right-hand side), the CLI reports syntax errors when<br />

you import the file. If there is a syntax error during import, no mappings in the entire file are imported.<br />

Remember to issue the commit command after you import a genericstable file so that the <strong>configuration</strong><br />

changes for the listener take effect.<br />

In this example, the masquerade subcommand of listenerconfig is used to construct a domain<br />

masquerading table for the private listener named “OutboundMail” on the PrivateNet interface.<br />

First, the option to use LDAP for masquerading is declined. (For information on configuring LDAP<br />

masquerading queries, see See Chapter 3, “LDAP Queries” for more information on LDAP<br />

masquerading queries.)<br />

Then, a partial domain notation of @.example.com is mapped to @example.com so that any email sent<br />

from any machine in the subdomain of .example.com will be mapped to example.com. Then, the<br />

username joe is mapped to the domain joe@example.com. The domain masquerading table is then<br />

printed to confirm both entries, and then exported to a file named masquerade.txt. The config<br />

subcommand is used to disable re-writing addresses in the CC: field, and finally, the changes are<br />

committed.<br />

mail3.example.com> listenerconfig<br />

Currently configured listeners:<br />

Cisco <strong>IronPort</strong> AsyncOS 7.6 for Email Advanced Configuration Guide<br />

2-19

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!