Cisco Cisco Email Security Appliance C160 Mode D'Emploi

An alias in the left-hand side can contain the following formats:

Specifies an alias to match. There must be a preceding 
“domains” attribute specified in the table. The lack of this 
parameter will produce an error. 

Specifies an exact email address to match on. 

You can enter multiple aliases, separated by commas on a single left-hand side 
line. 

Each recipient in the right-hand side can be a full 

user@domain

 email address, or 

another alias.

An alias file can contain “global” aliases (aliases that are applied globally instead 
of to a specific domain) with no implied domain, domain contexts within which 
aliases have one or more implied domains, or both.

 “Chains” (or recursive entries) of aliases may be created, but they must end in a 
full email address.

A special destination of 

/dev/null

 is supported to drop the message in order to 

be compatible with context of a sendmail configuration. If a message is mapped to 

 

/dev/null

 via an alias table, the dropped counter is increased. (See “Managing 

and Monitoring via the CLI” in the Cisco IronPort AsyncOS for Email Daily 
Management Guide.) The recipient is accepted but not enqueued.

To import an alias table, first see 

 to 

ensure that you can access the appliance. 

Use the 

export

 subcommand of the 

aliasconfig

 command to save any existing 

alias table. A file (whose name you specify) will be written to the 

/configuration

 

directory for the listener. You can modify this file outside of the CLI and then 
re-import it. (If you have malformed entries in the file, errors are printed when 
you try to import the file.) 

Place the alias table file in the 

/configuration

 directory, and then use the 

import

 

subcommand of the 

aliasconfig

 command to upload the file. 

Comment out lines in the table using a number symbol (#) at the beginning of each 
line.