ESA 9-6 CLI Reference Guide
ESA 9-6 CLI Reference Guide
6 for
Cisco Email Security Appliances
July 6, 2015
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL
STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT
WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT
SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR
LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCBs public
domain version of the UNIX operating system. All rights reserved. Copyright 1981, Regents of the University of California.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED AS IS WITH
ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION,
THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE,
OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING,
WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO
OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this
URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership
relationship between Cisco and any other company. (1110R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display
output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in
illustrative content is unintentional and coincidental.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
2015 Cisco Systems, Inc. All rights reserved.
CONTENTS
Preface
1
2
Additional Resources 2
Documentation 2
Knowledge Base 2
Cisco Support Community 3
Customer Support 3
Registering for a Cisco Account 3
Cisco Welcomes Your Comments 3
CHAPTER
1-1
CHAPTER
1-2
1-5
2-1
CHAPTER
2-6
3-1
3-2
Anti-Spam 3-6
antispamconfig 3-6
antispamstatus 3-8
antispamupdate 3-8
incomingrelayconfig 3-9
slblconfig 3-12
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
Contents
3-21
3-32
3-35
3-13
Contents
dnshostprefs 3-58
dnslistconfig 3-59
dnslisttest 3-60
dnsstatus 3-60
General Management/Administration/Troubleshooting
addressconfig 3-62
adminaccessconfig 3-64
certconfig 3-69
date 3-74
diagnostic 3-74
diskquotaconfig 3-78
ecconfig 3-80
ecstatus 3-81
ecupdate 3-81
encryptionconfig 3-81
encryptionstatus 3-85
encryptionupdate 3-85
featurekey 3-86
featurekeyconfig 3-87
generalconfig 3-87
healthcheck 3-88
healthconfig 3-89
ntpconfig 3-90
reboot 3-91
repengstatus 3-92
resume 3-92
resumedel 3-93
resumelistener 3-93
revert 3-94
settime 3-95
settz 3-95
shutdown 3-96
sshconfig 3-97
status 3-99
supportrequest 3-100
supportrequeststatus 3-102
supportrequestupdate 3-103
suspend 3-103
suspenddel 3-104
suspendlistener 3-104
3-61
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
Contents
tcpservices 3-105
techsupport 3-106
tlsverify 3-107
trace 3-108
trackingconfig 3-110
tzupdate 3-110
updateconfig 3-111
updatenow 3-116
version 3-116
wipedata 3-117
upgrade 3-118
LDAP 3-118
ldapconfig 3-119
ldapflush 3-123
ldaptest 3-124
sievechar 3-125
Mail Delivery Configuration/Monitoring
addresslistconfig 3-126
aliasconfig 3-128
archivemessage 3-130
altsrchost 3-131
bounceconfig 3-133
bouncerecipients 3-136
bvconfig 3-138
deleterecipients 3-139
deliveryconfig 3-140
delivernow 3-141
destconfig 3-142
hostrate 3-149
hoststatus 3-150
imageanalysisconfig 3-151
oldmessage 3-153
rate 3-153
redirectrecipients 3-154
resetcounters 3-155
removemessage 3-155
showmessage 3-156
showrecipients 3-156
status 3-158
tophosts 3-159
3-126
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
Contents
topin 3-160
unsubscribe 3-160
workqueue 3-162
Networking Configuration / Network Tools
etherconfig 3-163
interfaceconfig 3-165
nslookup 3-167
netstat 3-168
packetcapture 3-169
ping 3-171
ping6 3-172
routeconfig 3-172
setgateway 3-175
sethostname 3-176
smtproutes 3-176
sslconfig 3-178
sslv3config 3-180
telnet 3-181
traceroute 3-181
traceroute6 3-182
3-162
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
Contents
logconfig 3-230
rollovernow 3-238
snmpconfig 3-238
tail 3-240
Reporting 3-241
reportingconfig
3-242
Senderbase 3-245
sbstatus 3-245
senderbaseconfig
3-246
3-268
3-293
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
Preface
The instructions in this book are designed for an experienced system administrator with knowledge of
networking and email administration.
If you have already cabled your appliance to your network, ensure that the default IP address for the
appliance does not conflict with other IP addresses on your network. The IP address assigned to the
Management port by the factory is 192.168.42.42. See the Setup and Installation chapter in the user
guide for your release for more information about assigning IP addresses to the appliance.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
Preface
Typographic Conventions
Typeface or
Symbol
Meaning
Examples
Please choose an IP interface for this Listener.
AaBbCc123
mail3.example.com> commit
Please enter some comments describing your changes:
[]> Changed the system hostname
AaBbCc123
AaBbCc123
Additional Resources
Documentation
Documentation for your Email Security appliance is available from:
http://www.cisco.com/en/US/products/ps10154/tsd_products_support_series_home.html
Knowledge Base
To access the Knowledge Base for information about Cisco Content Security products, visit:
http://www.cisco.com/web/ironport/knowledgebase.html
Note
You need a Cisco.com User ID to access the site. If you do not have a Cisco.com User ID, see Registering
for a Cisco Account, page 3.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
II
Preface
Customer Support
Use the following methods to obtain support:
U.S.: Call 1 (408) 526-7209 or Toll-free 1 (800) 553-2447
International: http://www.cisco.com/en/US/support/tsd_cisco_worldwide_contacts.html
Support Site: http://www.cisco.com/en/US/products/ps11169/serv_group_home.html
If you purchased support through a reseller or another supplier, please contact that supplier directly with
your product support issues.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
III
Preface
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
IV
CH A P T E R
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
1-1
Chapter 1
Description
Platform Availability
antispamstatus
C- and X- Series
antispamupdate
C- and X- Series
antivirusstatus
C- and X- Series
antivirusupdate
C- and X- Series
archivemessage
C- and X- Series
bouncerecipients
clearchanges or clear
Clear changes
commit
Commit changes
commitdetail
C- and X- Series
date
deleterecipients
delivernow
diagnostic
Check RAID disks, network caches, and SMTP connections. Clear C-, X-, and M-Series
network caches.
dig
C- and X- Series
displayalerts
dlprollback
C- and X- Series
dlpstatus
C- and X- Series
dlpupdate
C- and X- Series
dnsflush
dnslisttest
C- and X- Series
dnsstatus
ecstatus
C-Series
ecupdate
C-Series
emdiagnostic
encryptionstatus
Shows the version of the PXE Engine and Domain Mappings file
C- and X-Series
encryptionupdate
C- and X-Series
featurekey
findevent
graymailstatus
C- and X-Series
graymailupdate
C- and X-Series
grep
healthcheck
C- and X-Series
help or h or ?
Help
hostrate
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
1-2
Chapter 1
hoststatus
last
ldapflush
C- and X- Series
ldaptest
C- and X- Series
loadlicense
mailconfig
nslookup
netstat
outbreakflush
C- and X- Series
outbreakstatus
C- and X- Series
outbreakupdate
C- and X- Series
oldmessage
C- and X- Series
packetcapture
password or passwd
ping
ping6
quit or q or exit
Quit
rate
reboot
redirectrecipients
C- and X- Series
removemessage
C- and X- Series
repengstatus
resetconfig
resetcounters
resume
resumedel
Resume deliveries
resumelistener
Resume receiving
revert
rollovernow
saveconfig
sbstatus
C- and X- Series
settime
showmessage
C- and X- Series
showconfig
showlicense
showrecipients
C- and X- Series
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
1-3
Chapter 1
shutdown
slblconfig
C- and X-Series
status
System status
supportrequest
supportrequeststatus
supportrequestupdate
suspend
suspenddel
Suspend deliveries
suspendlistener
Suspend receiving
systemsetup
C- and X- Series
tail
techsupport
telnet
tlsverify
Establish an outbound TLS connection to a remote host and debug C- and X- Series
any TLS connection issues
tophosts
topin
trace
traceroute
traceroute6
tzupdate
updatenow
upgrade
Install an upgrade
version
wipedata
Wipe the core files on the disk and check the status of the last
coredump operation
webcacheflush
websecuritydiagnostics
who
whoami
workqueue
C- and X- Series
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
1-4
Chapter 1
Description
Platform Availability
addressconfig
addresslistconfig
C- and X- Series
adminaccessconfig
C- and X- Series
aggregatorconfig
C- and X- Series
alertconfig
aliasconfig
C- and X- Series
altsrchost
C- and X- Series
ampconfig
antispamconfig
C- and X- Series
antivirusconfig
C- and X- Series
bounceconfig
bvconfig
C- and X- Series
callaheadconfig
certconfig
clusterconfig
C- and X- Series
deliveryconfig
C- and X- Series
destconfig
C- and X- Series
dictionaryconfig
diskquotaconfig
dmarcconfig
C- and X- Series
dnsconfig
C- and X- Series
dnshostprefs
dnslistconfig
C- and X- Series
domainkeysconfig
C- and X- Series
ecconfig
emconfig
C- and X- Series
encryptionconfig
C- and X- Series
etherconfig
exceptionconfig
C- and X- Series
featurekeyconfig
filters
C- and X- Series
generalconfig
graymailconfig
Configure graymail detection and safe unsubscribe global settings C- and X- Series
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
1-5
Chapter 1
healthconfig
imageanalysisconfig
incomingrelayconfig
C- and X- Series
interfaceconfig
ldapconfig
C- and X- Series
listenerconfig
C- and X- Series
loadconfig
localeconfig
C- and X- Series
logconfig
ntpconfig
outbreakconfig
C- and X- Series
policyconfig
C- and X- Series
quarantineconfig
C- and X- Series
reportingconfig
rollbackconfig
routeconfig
scanconfig
C- and X- Series
senderbaseconfig
C- and X- Series
setgateway
sethostname
settz
sievechar
C- and X- Series
smimeconfig
smtpauthconfig
C- and X- Series
smtproutes
snmpconfig
Configure SNMP
sshconfig
sslconfig
sslv3config
Enable/Disable SSLv3
stripheaders
C- and X- Series
tcpservices
textconfig
C- and X- Series
trackingconfig
unsubscribe
updateconfig
C- and X- Series
LDAP
urllistconfig
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
1-6
Chapter 1
userconfig
Manage user accounts and connections to external authentication C-, X-, and M- Series
sources.
websecurityadvancedconfig
websecurityconfig
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
1-7
Chapter 1
CLI Commands (Commit Required)
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
1-8
CH A P T E R
Username: admin
Password: ironport
For example:
login: admin
password: ironport
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
2-1
Chapter 2
Command Prompt
The top-level command prompt consists of the fully qualified hostname, followed by the greater than (>)
symbol, followed by a space. For example:
mail3.example.com>
If the appliance has been configured as part of a cluster with the Centralized Management feature, the
prompt in the CLI changes to indicate the current mode. For example:
(Cluster Americas) >
or
(Machine los_angeles.example.com) >
When there is a default setting, the setting is displayed within the command prompt brackets. For
example:
Ethernet interface:
1. Data 1
2. Data 2
3. Management
[1]> 1
When a default setting is shown, typing Return is equivalent to typing the default:
Ethernet interface:
1. Data 1
2. Data 2
3. Management
[1]> (type Return)
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
2-2
Chapter 2
Command Syntax
When operating in the interactive mode, the CLI command syntax consists of single commands with no
white spaces and no arguments or parameters. For example:
mail3.example.com> systemsetup
Select Lists
When you are presented with multiple choices for input, some commands use numbered lists. Enter the
number of the selection at the prompt.
For example:
Log level:
1. Error
2. Warning
3. Information
4. Debug
5. Trace
[3]> 3
Yes/No Queries
When given a yes or no option, the question is posed with a default in brackets. You may answer Y, N,
Yes, or No. Case is not significant.
For example:
Do you want to enable FTP on this interface?
[Y]> n
Subcommands
Some commands give you the opportunity to use subcommands. Subcommands include directives such
as NEW, EDIT, and DELETE. For the EDIT and DELETE functions, these commands provide a list of the
records previously configured in the system.
For example:
mail3.example.com> interfaceconfig
Within subcommands, typing Enter or Return at an empty prompt returns you to the main command.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
2-3
Chapter 2
Escape
You can use the Control-C keyboard shortcut at any time within a subcommand to immediately exit
return to the top level of the CLI.
History
The CLI keeps a history of all commands you type during a session. Use the Up and Down arrow keys
on your keyboard, or the Control-P and Control-N key combinations, to scroll through a running list of
the recently-used commands.
mail3.example.com> (type the Up arrow key)
Command Completion
The command-line interface supports command completion. You can type the first few letters of some
commands followed by the Tab key, and the CLI completes the string for unique commands. If the letters
you entered are not unique among commands, the CLI narrows the set. For example:
mail3.example.com> set (type the Tab key)
setgateway, sethostname, settime, settz
mail3.example.com> seth (typing the Tab again completes the entry with
sethostname)
For both the history and file completion features of the CLI, you must type Enter or Return to invoke the
command.
Configuration Changes
You can make configuration changes while email operations proceed normally.
Configuration changes will not take effect until you complete the following steps:
Step 1
Step 2
Step 3
Changes to configuration that have not been committed will be recorded but not put into effect until the
commit command is run.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
2-4
Chapter 2
Note
Not all commands require the commit command to be run. See Chapter 1, CLI Quick Reference Guide
for a summary of commands that require commit to be run before their changes take effect.
Exiting the CLI session, system shutdown, reboot, failure, or issuing the clear command clears changes
that have not yet been committed.
Note
To successfully commit changes, you must be at the top-level command prompt. Type Return at an empty
prompt to move up one level in the command line hierarchy.
[Y]> y
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
2-5
Chapter 2
Batch Commands
Batch Commands
AsyncOS includes support for batch command formats that allow you to execute certain CLI commands
using a new, single-line CLI format. This format reduces the number of inputs required to complete tasks
and provides a mechanism allowing you to easily automate common configuration tasks. Batch
commands also allow you to issue commands remotely using an SSH client. This enables you to easily
script CLI commands and execute them on multiple appliances at one time.
Not all commands have a batch equivalent, but all batch commands can be executed as non-batch
commands.
Batch command syntax is dependent on the specific command being used. Please see the appropriate CLI
example in Chapter 3, The Commands: Reference Examples for more information about syntax
specific to that command.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
2-6
Chapter 2
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
2-7
Chapter 2
Batch Commands
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
2-8
Chapter 2
4. TCP Refuse
5. Continue
6. Policy: ACCEPTED
7. Policy: BLOCKED
8. Policy: THROTTLED
9. Policy: TRUSTED
[1]> 8
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
2-9
Chapter 2
Batch Commands
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
2-10
CH A P T E R
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-1
Chapter 3
Step 2
Step 3
Usage
Commit: This command requires a commit.
Cluster Management: This command can be used in all three machine modes (cluster, group, machine).
Batch Command: This command supports a batch format. For details, see the inline help by typing the
command: help ampconfig.
Examples
Configure Email Security appliance to Use Public Cloud File Analysis Server, page 3-3
(Public Cloud File Analysis Services Only) Configuring Appliance Groups, page 3-4
Configure Email Security appliance to Use an On-Premises File Analysis Server, page 3-5
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-2
Chapter 3
1. Microsoft Executables
Do you want to modify the file types selected for File Analysis? [N]>
1. Microsoft Executables
Configure Email Security appliance to Use Public Cloud File Analysis Server
mail.example.com> ampconfig
File Reputation: Enabled
File Analysis: Enabled
File types selected for File Analysis:
Microsoft Windows / DOS Executable
Appliance Group ID/Name: Not part of any group yet
Choose the operation you want to perform:
- SETUP - Configure Advanced-Malware protection service.
- ADVANCED - Set values for AMP parameters (Advanced configuration).
- CLEARCACHE - Clears the local File Reputation cache.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-3
Chapter 3
[]> advanced
Enter cloud query timeout?
[15]>
Enter cloud domain?
[cloud-domain.com]>
Enter reputation cloud server pool?
[cloud-server-pool.com]>
Do you want use the recommended reputation threshold from cloud service? [Y]>
Choose a file analysis server:
1. AMERICAS (https://americas-fa.com)
2. Private Cloud
[1]>
...
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-4
Chapter 3
Note
After you configure an appliance group, you cannot use the setgroup subcommand. If you want to need
to modify the group for any reason, you must open a case with Cisco TAC.
You can view the details of the appliance group using the viewgroup subcommand.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-5
Chapter 3
Anti-Spam
Anti-Spam
This section contains the following commands:
antispamconfig
antispamstatus
antispamupdate
incomingrelayconfig
antispamconfig
Description
Configure anti-spam policy.
Usage
Commit: This command requires a commit.
Cluster Management: This command can be used in all three machine modes (cluster, group, machine).
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-6
Chapter 3
Example
The following examples demonstrates the configuration for Anti-Spam functionality.
mail3.example.com> antispamconfig
Choose the operation you want to perform:
- IRONPORT - Configure IronPort Anti-Spam.
- CLOUDMARK - Configure Cloudmark Service Provider Edition.
- MULTISCAN - Configure IronPort Intelligent Multi-Scan.
[]> ironport
IronPort Anti-Spam scanning: Disabled
Choose the operation you want to perform:
- SETUP - Edit IronPort Anti-Spam settings.
[]> setup
IronPort Anti-Spam scanning: Disabled
Would you like to use IronPort Anti-Spam scanning? [Y]> y
The IronPort Anti-Spam License Agreement is displayed (if you have not already accepted
it).
Do you accept the above IronPort Anti-Spam license agreement? []> Y
Increasing the following size settings may result in decreased performance. Please consult
documentation for size recommendations based on your environment.
Never scan message larger than: (Add a trailing K for kilobytes, M for megabytes, or no
letters for bytes.)
[1M]>
Always scan message smaller than: (Add a trailing K for kilobytes, M for megabytes, or no
letters for bytes.)
[512K]>
Please specify the IronPort Anti-Spam scanning timeout (in seconds)
[60]>
Would you like to enable regional scanning? [N]>
IronPort Anti-Spam scanning is now enabled on the system. Please note: you must issue the
'policyconfig' command (CLI) or Mail Policies (GUI) to configure
Cisco IronPort scanning behavior for default and custom Incoming and Outgoing Mail
Policies. This is recommended for your DEFAULT policy.
IronPort Anti-Spam scanning: Enabled
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-7
Chapter 3
Anti-Spam
antispamstatus
Description
Display anti-spam status.
Usage
Commit: This command does not require a commit.
Cluster Management: This command can be used in all three machine modes (cluster, group, machine).
Batch Command: This command does not support a batch format.
Example
mail3.example.com> antispamstatus
Last
Never
Never
Never
Never
Never
Never
Never
Update
Version
updated
3.4.0-013
updated
3.4.0-013
updated 3.3.1-009-20141210_214201
updated
20141211_111021
updated 20141211_111021-20141211_170330
updated
unavailable
updated
unavailable
antispamupdate
Description
Manually request an immediate update of Anti-Spam rules and related CASE components. This also
includes the Anti-Spam rules and CASE components used by Intelligent Multi-Scan (IMS), but not for
the third-party anti-spam engines used by IMS.
Usage
Commit: This command does not require a commit.
Cluster Management: This command is restricted to machine mode. It is further restricted to the login
host (i.e., the specific machine you are logged onto).
Batch Command: This command does not support a batch format.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-8
Chapter 3
Example
mail3.example.com> antispamupdate
Choose the operation you want to perform:
- MULTISCAN - Request updates for Intelligent Multi-Scan
- IRONPORT - Request updates for IronPort Anti-Spam
- CLOUDMARK - Request updates for Cloudmark Anti-Spam
[]> ironport
Requesting check for new CASE definitions
incomingrelayconfig
Description
Use the incomingrelayconfig command to enable and configure the Incoming Relays feature. In the
following examples, the Incoming Relays feature is first enabled, and then two relays are added, one is
modified, and one is deleted.
Usage
Commit: This command requires a commit.
Cluster Management: This command can be used in all three machine modes (cluster, group, machine).
Batch Command: This command does not support a batch format.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-9
Chapter 3
Anti-Spam
[]> relaylist
There are no relays defined.
Choose the operation you want to perform:
- NEW - Create a new entry
[]> new
Enter a name for this incoming relay (Ex: "first-hop")
[]> first-hop
Enter the IP address of the incoming relay.
For IPv4, CIDR format subnets such as 10.1.1.0/24, IP address ranges such as 10.1.1.10-20,
and subnets such as 10.2.3. are allowed.
For IPv6, CIDR format subnets such as 2001:db8::/32 and IP address ranges such as
2001:db8::1-2001:db8::11 are allowed.
Hostnames such as crm.example.com and partial hostnames such as .example.com are allowed.
[]> 192.168.1.1
Do you want to use the "Received:" header or a custom header to determine the originating
IP address?
1. Use "Received:" header
2. Use a custom header
[1]> 1
Within the "Received:" header, enter the special character or string after which to begin
parsing for the originating IP address:
[from]> [
Within the headers, enter the position of the "Received:" header that contains the
originating IP address:
[1]> 1
There is 1 relay defined.
Choose the operation you want to perform:
- NEW - Create a new entry
- EDIT - Modify an entry
- DELETE - Remove an entry
- PRINT - Display the table
[]> print
Incoming
relay name:
----------first-hop
IP address:
----------192.168.1.1
Header
to parse:
--------Received
Match
after:
-----[
Hops:
----1
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-10
Chapter 3
For IPv4, CIDR format subnets such as 10.1.1.0/24, IP address ranges such as 10.1.1.10-20,
and subnets such as 10.2.3. are allowed.
For IPv6, CIDR format subnets such as 2001:db8::/32 and IP address ranges such as
2001:db8::1-2001:db8::11 are allowed.
Hostnames such as crm.example.com and partial hostnames such as .example.com are allowed.
[]> 192.168.1.2
Do you want to use the "Received:" header or a custom header to determine the originating
IP address?
1. Use "Received:" header
2. Use a custom header
[1]> 2
Enter the custom header name that contains the originating IP address:
[]> x-Connecting-IP
There are 2 relays defined.
Choose the operation you want to perform:
- NEW - Create a new entry
- EDIT - Modify an entry
- DELETE - Remove an entry
- PRINT - Display the table
[]> print
Incoming
relay name:
----------first-hop
second-hop
Header
to parse:
--------Received
x-Connecting-IP
IP address:
----------192.168.1.1
192.168.1.2
Match
after:
-----[
n/a
Hops:
----1
n/a
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-11
Chapter 3
Anti-Spam
slblconfig
Description
Configure End-User Safelist/Blocklist.
Note
Safelists/Blocklists must be enabled on the appliance via the GUI in order to run this command.
Usage
Commit: This command does not require a commit.
Batch Command: This command supports a batch format.
filename - Name of the file that has to be imported. The file must be in the /configuration
directory on the appliance.
The appliance saves a .CSV file to the /configuration directory using the following naming
convention:
slbl<timestamp><serial number>.csv.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-12
Chapter 3
1. slbl.csv
Choose the file to import from.
[1]> 1
Do you want to ignore invalid entries? [Y]> Y
End-User Safelist/Blocklist import has been initiated...
Please wait while this operation executes.
End-User Safelist/Blocklist successfully imported.
Choose the operation you want to perform:
- IMPORT - Replace all entries in the End-User Safelist/Blocklist.
- EXPORT - Export all entries from the End-User Safelist/Blocklist.
[]>
Command
graymailconfig
graymailstatus
graymailupdate
graymailconfig
Description
Configure graymail detection and safe unsubscribing global settings.
Note
To enable graymail detection and safe unsubscribing, anti-spam scanning must be enabled
globally.This can be either the IronPort Anti-Spam or the Intelligent Multi-Scan feature.
To configure policy settings for graymail detection and safe unsubscribing, use the policyconfig
command. For more information, see Create an Incoming Policy to Drop the Messages Identified as Bulk
Email or Social Network Email, page 3-215.
Usage
Commit: This command requires a commit.
Cluster Management: This command can be used in all three machine modes (cluster, group, machine).
Batch Command: This command supports a batch format. For details, see the inline help by typing the
command: help graymailconfig.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-13
Chapter 3
Example
Graymail Detection: Disabled
Choose the operation you want to perform:
- SETUP - Configure Graymail.
[]> setup
Would you like to use Graymail Detection? [Y]>
Increasing the following size settings may result in decreased performance.
Please consult documentation for size recommendations based on your
environment.
Maximum Message Size to Scan (Add a trailing K for kilobytes, M for megabytes,
or no letters for bytes.):
[1M]>
Timeout for Scanning Single Message(in seconds):
[60]>
Graymail Safe Unsubscribe: Disabled
Would you like to use Graymail Safe Unsubscribe? [Y]>
Graymail Detection and Safe Unsubscribe is now enabled. Please note: The global
settings are recommended only for your DEFAULT mail policy. To configure policy
settings, use the incoming or outgoing policy page on web interface or the
'policyconfig' command in CLI.
graymailstatus
Description
Display the details of the existing graymail rules.
Usage
Commit: This command does not require a commit.
Cluster Management: This command can be used in all three machine modes (cluster, group, machine).
Batch Command: This command does not support a batch format
Example
mail.example.com> graymailstatus
Component
Graymail Library
Graymail Tools
Version
01.378.53#15
1.0
Last Updated
Never updated
Never updated
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-14
Chapter 3
graymailupdate
Description
Manually request update of the graymail rules.
Usage
Commit: This command does not require a commit.
Cluster Management: This command can be used in all three machine modes (cluster, group, machine).
Batch Command: This command does not support a batch format
Example
mail.example.com> graymailupdate
Anti-Virus
This section contains the following CLI commands:
antivirusconfig
antivirusstatus
antivirusupdate
antivirusconfig
Description
Configure anti-virus policy.
Usage
Commit: This command requires a commit.
Cluster Management: This command can be used in all three machine modes (cluster, group, machine).
Batch Command: This command does not support a batch format.
Example
In the following example, the antivirusconfig command is used to enable Sophos virus scanning on
the system and set the time-out value to 60 seconds. To configure the update server, update interval, and
optional proxy server, see updateconfig on page 111.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-15
Chapter 3
Anti-Virus
Note
The first time you invoke the antivirusconfig command, you may be presented with a license
agreement, if you did not accept the license during the systemsetup command. If you do not accept the
license agreement, the Sophos virus scanning engine will not be enabled on the appliance.
mail3.example.com> antivirusconfig
Choose the operation you want to perform:
- SOPHOS - Configure Sophos Anti-Virus.
- MCAFEE - Configure McAfee Anti-Virus.
[]> sophos
Sophos Anti-Virus: Disabled
Choose the operation you want to perform:
- SETUP - Configure Sophos Anti-Virus.
[]> setup
Sophos Anti-Virus scanning: Disabled
Would you like to use Sophos Anti-Virus scanning? [Y]> y
(First time users see the license agreement displayed here.)
Please specify the Anti-Virus scanning timeout (in seconds)
[60]> 60
Sophos Anti-Virus scanning is now enabled on the system.
Please note: you must issue the 'policyconfig' command (CLI) or Mail
Policies (GUI) to configure Sophos Anti-Virus scanning behavior for default and custom
Incoming and Outgoing Mail Policies.
This is recommended for your DEFAULT policy.
Sophos Anti-Virus: Enabled
Choose the operation you want to perform:
- SETUP - Configure Sophos Anti-Virus.
[]>
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-16
Chapter 3
Sophos Anti-Virus:
Product - 3.87
Engine - 2.25.0
Product Date - 01 Nov 2004
Virus
Virus
Virus
Virus
Virus
Virus
Virus
Virus
Virus
Virus
Virus
Sig.
Sig.
Sig.
Sig.
Sig.
Sig.
Sig.
Sig.
Sig.
Sig.
Sig.
23
22
22
21
21
21
20
19
19
18
17
Dec
Dec
Dec
Dec
Dec
Dec
Dec
Dec
Dec
Dec
Dec
2004
2004
2004
2004
2004
2004
2004
2004
2004
2004
2004
01:24:02
19:10:06
06:16:32
18:33:58
14:50:46
06:13:40
20:52:04
23:34:06
00:50:34
07:02:44
22:32:08
antivirusstatus
Description
Display Anti-Virus status.
Usage
Commit: This command does not require a commit.
Cluster Management: This command can be used in all three machine modes (cluster, group, machine).
Batch Command: This command does not support a batch format.
Example
mail3.example.com> antivirusstatus
Choose the operation you want to perform:
- MCAFEE - Display McAfee Anti-Virus version information
- SOPHOS - Display Sophos Anti-Virus version information
[]> sophos
SAV Engine Version
3.85
IDE Serial
2004101801
Engine Update
Mon Sep 27 14:21:25 2004
Last IDE Update
Mon Oct 18 02:56:48 2004
Last Update Attempt
Mon Oct 18 11:11:44 2004
Last Update Success
Mon Oct 18 02:56:47 2004
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-17
Chapter 3
antivirusupdate
Description
Manually update virus definitions.
Usage
Commit: This command does not require a commit.
Cluster Management: This command is restricted to machine mode. It is further restricted to the login
host (i.e., the specific machine you are logged onto).
Batch Command: This command does not support a batch format.
Example
mail3.example.com> antivirusupdate
Choose the operation you want to perform:
- MCAFEE - Request updates for McAfee Anti-Virus
- SOPHOS - Request updates for Sophos Anti-Virus
[]> sophos
Requesting update of virus definitions
mail3.example.com>
commit
commitdetail
clearchanges or clear
help or h or ?
rollbackconfig
quit or q or exit
commit
Description
Commit changes. Entering comments after the commit command is optional.
Usage
Commit: N/A
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-18
Chapter 3
Cluster Management: This command can be used in all three machine modes (cluster, group, machine).
Batch Command: This command does not support a batch format.
Example
mail3.example.com> commit
Please enter some comments describing your changes:
[]> Changed "psinet" IP Interface to a different IP ad dress
Do you want to save the current configuration for rollback? [Y]> n
Changes committed: Fri May 23 11:42:12 2014 GMT
commitdetail
Description
Display detailed information about the last commit.
Usage
Commit: This command does not require a commit.
Cluster Management: This command can be used in all three machine modes (cluster, group, machine).
Batch Command: This command does not support a batch format.
Example
mail3.example.com> commitdetail
Commit at Mon Apr 18 13:46:28 2005 PDT with comments: "Enabled loopback".
mail3.example.com>
clearchanges or clear
Description
The clear command clears any configuration changes made since the last commit or clear command
was issued.
Usage
Commit: This command does not require a commit.
Cluster Management: This command can be used in all three machine modes (cluster, group, machine).
Batch Command: This command does not support a batch format
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-19
Chapter 3
Example
mail3.example.com> clear
Are you sure you want to clear all changes since the last commit?
[Y]> y
help or h or ?
Description
The help command lists all available CLI commands and gives a brief description of each command.
The help command can be invoked by typing either help or a single question mark (?) at the command
prompt.
Usage
Commit: This command does not require a commit.
Cluster Management: This command can be used in all three machine modes (cluster, group, machine).
Batch Command: This command does not support a batch format
Example
mail3.example.com> help
Displays the list of all available commands.
rollbackconfig
The rollbackconfig command allows you to rollback to one of the previously committed 10
configurations.
Usage
Commit: This command requires a commit.
Cluster Management: This command is restricted to machine mode.
Batch Command: This command does not support a batch format.
Example
mail.example.com> rollbackconfig
Previous Commits:
Committed On
User
Description
--------------------------------------------------------------------------------1. Fri May 23 06:53:43 2014
admin
new user
2. Fri May 23 06:50:57 2014
admin
rollback
3. Fri May 23 05:47:26 2014
admin
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-20
Chapter 3
admin
edit user
rollback
quit or q or exit
Description
The quit command logs you out of the CLI application. Configuration changes that have not been
committed are cleared. The quit command has no effect on email operations. Logout is logged into the
log files. (Typing exit is the same as typing quit.)
Usage
Commit: This command does not require a commit.
Cluster Management: This command can be used in all three machine modes (cluster, group, machine).
Batch Command: This command does not support a batch format
Example
mail3.example.com> quit
Configuration changes entered but not committed. Exiting will lose changes.
Type 'commit' at the command prompt to commit changes.
Are you sure you wish to exit? [N]> Y
loadconfig
mailconfig
resetconfig
saveconfig
showconfig
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-21
Chapter 3
loadconfig
Description
Load a configuration file.
Note
Loading configuration on clustered machines is supported only using GUI. For instructions, see User
Guide for AsyncOS for Cisco Email Security Appliances.
Usage
Commit: This command requires a commit.
Cluster Management: This command can be used in all three machine modes (cluster, group, machine).
Batch Command: This command does not support a batch format
Example
In this example, a new configuration file is imported from a local location.
mail3.example.com> loadconfig
1. Paste via CLI
2. Load from file
[1]> 2
Enter the name of the file to import:
[]> changed.config.xml
Values have been loaded.
Be sure to run "commit" to make these settings active.
mail3.example.com> commit
Please enter some comments describing your changes:
[]> loaded new configuration file
Do you want to save the current configuration for rollback? [Y]> n
Changes committed: Fri May 23 11:42:12 2014 GMT
In this example, a new configuration file is pasted directly at the command line. (Remember to type
Control-D on a blank line to end the paste command.) Then, the system setup wizard is used to change
the default hostname, IP address, and default gateway information. Finally, the changes are committed.
mail3.example.com> loadconfig
1. Paste via CLI
2. Load from file
[1]> 1
Paste the configuration file now.
Press CTRL-D on a blank line when done.
[The configuration file is pasted until the end tag </config>. Control-D is entered on a
separate line.]
Values have been loaded.
Be sure to run "commit" to make these settings active.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-22
Chapter 3
mail3.example.com> systemsetup
[The system setup wizard is run.]
mail3.example.com> commit
Please enter some comments describing your changes:
[]> pasted new configuration file and changed default settings via
systemsetup
Do you want to save the current configuration for rollback? [Y]> n
Changes committed: Fri May 23 11:42:12 2014 GMT
mailconfig
Description
To test the configuration, you can use the mailconfig command immediately to send a test email
containing the system configuration data you just created with the systemsetup command.
Usage
Commit: This command does not require a commit.
Cluster Management: This command can be used in all three machine modes (cluster, group, machine).
Batch Command: This command does not support a batch format
Example
mail.example.com> mailconfig
Please enter the email address to which you want to send the configuration file.
Separate multiple addresses with commas.
[]> [email protected]
Choose the password option:
1. Mask passwords (Files with masked passwords cannot be loaded using loadconfig command)
2. Encrypt passwords
3. Plain passwords
[1]> 2
The configuration file has been sent to [email protected].
Send the configuration to a mailbox to which you have access to confirm that the system is able to send
email on your network.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-23
Chapter 3
resetconfig
Description
When physically transferring the appliance, you may want to start with factory defaults. The
resetconfig command resets all configuration values to factory defaults. This command is extremely
destructive, and it should only be used when you are transferring the unit or as a last resort to solving
configuration issues. It is recommended you run the systemsetup command after reconnecting to the
CLI after you have run the resetconfig command.
Note
The resetconfig command only works when the appliance is in the offline state. When the resetconfig
command completes, the appliance is automatically returned to the online state, even before you run the
systemsetup command again. If mail delivery was suspended before you issued the resetconfig
command, the mail will attempt to be delivered again when the resetconfig command completes.
Warning
The resetconfig command will return all network settings to factory defaults, potentially
disconnecting you from the CLI, disabling services that you used to connect to the appliance (FTP,
Telnet, SSH, HTTP, HTTPS), and even removing additional user accounts you created with the
userconfig command. Do not use this command if you are not able to reconnect to the CLI using the
Serial interface or the default settings on the Management port through the default Admin user
account.
Usage
Commit: This command does not require a commit.
Cluster Management: This command is restricted to machine mode. It is further restricted to the login
host (i.e., the specific machine you are logged onto). This command requires access to the local file
system.
Batch Command: This command does not support a batch format.
Example
mail3.example.com> suspend
Delay (seconds, minimum 30):
[30]> 45
Waiting for listeners to exit...
Receiving suspended.
Waiting for outgoing deliveries to finish...
Mail delivery suspended.
mail3.example.com> resetconfig
Are you sure you want to reset all configuration values? [N]> Y
All settings have been restored to the factory default.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-24
Chapter 3
saveconfig
Description
The saveconfig command saves the configuration file with a unique filename to the configuration
directory.
Note
If you are on a clustered environment, this command saves the complete cluster configuration. To run
this command on a clustered machine, change your configuration mode to cluster.
Usage
Commit: This command does not require a commit.
Cluster Management: This command can be used in all three machine modes (cluster, group, machine).
Batch Command: This command does not support a batch format
Example
In the following example, the passwords in the configuration file is encrypted and saved in the
configuration directory.
mail.example.com> saveconfig
Choose the password option:
1. Mask passwords (Files with masked passwords cannot be loaded using loadconfig command)
2. Encrypt passwords
3. Plain passwords
[1]> 2
File written on machine "mail.example.com" to the location
"/configuration/C100V-4232116C4E14C70C4C7F-7898DA3BD955-20140319T050635.xml".
Configuration saved.
showconfig
Description
The showconfig command prints the current configuration to the screen.
Usage
Commit: This command does not require a commit.
Cluster Management: This command can be used in all three machine modes (cluster, group, machine).
Batch Command: This command does not support a batch format
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-25
Chapter 3
Cluster Management
Example
In the following example, the configuration is displayed on CLI and the passwords in the configuration
are encrypted.
mail.example.com> showconfig
Choose the password display option:
1. Mask passwords (Files with masked passwords cannot be loaded using loadconfig command)
2. Encrypt passwords
3. Plain passwords
[1]> 2
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE config SYSTEM "config.dtd">
<!-Product: Cisco C100V Email Security Virtual Appliance
Model Number: C100V
Version: 9.0.0-038
Serial Number: 4232116C4E14C70C4C7F-7898DA3BD955
Number of CPUs: 2
Memory (MB): 6144
Current Time: Wed Mar 19 05:30:05 2014
-->
<config>
<!-******************************************************************************
*
Network Configuration
*
******************************************************************************
-->
[The remainder of the configuration file is printed to the screen.]
Cluster Management
This section contains the following CLI commands:
clusterconfig
clusterconfig
Description
The clusterconfig command is used to configure cluster-related settings. If this machine is not part of
a cluster, running clusterconfig will give you the option of joining a cluster or creating a new cluster.
The clusterconfig command provides additional subcommands:
Non-Cluster Commands
The following commands are available when you are not in a cluster.
clusterconfig new <name> This will create a new cluster with the given name. This machine
will be a member of this cluster and a member of a default cluster group called "Main Group".
<name>
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-26
Chapter 3
This will display the information needed to prepare the joining of this machine to a cluster over a CCS
port.
Cluster Commands
The following commands are available when you are in a cluster.
no members.
group.
<new_groupname>
clusterconfig list
clusterconfig connstatus Display all the machines currently in the cluster and add routing
details for disconnected machines.
cluster.
<machinename>
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-27
Chapter 3
<user_key>
- The SSH user key from the "prepjoin print" command from
clusterconfig prepjoin delete <serial_number|hostname> This will remove a host that was
previously indicated to be added from the "prepjoin new" command. This is only necessary to be
used if you later decide not to add the host. When a host is successfully added to the cluster, its
prepjoin information is automatically removed.
Usage
Commit: This command does not require a commit.
Cluster Management: This command is restricted to cluster mode.
Batch Command: This command does not support a batch format.
Example
For an explanation of the clusterconfig command and its uses, see User Guide for AsyncOS for Cisco
Email Security Appliances.
dlprollback
dlpstatus
dlpupdate
emconfig
emdiagnostic
dlprollback
Description
Rollback DLP engine and config to the previous version.
Note
DLP must already be configured via the DLP Global Settings page in the GUI before you can use the
dlprollback command.
Warning
This command will revert your appliance to older DLP policies. You must re-enable DLP policies in
Outbound Mail Policies so that DLP scanning can be resumed.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-28
Chapter 3
Usage
Commit: This command does not require a commit.
Cluster Management: This command is can be used at cluster, group or machine mode.
Batch Command: This command does not support a batch format.
Example
mail.example.com> dlprollback
dlpstatus
Request version information for DLP Engine.
Note
DLP must already be configured via the DLP Global Settings page in the GUI before you can use the
dlpstatus command.
Usage
Commit: This command does not require a commit.
Cluster Management: This command is can be used at cluster, group or machine mode.
Batch Command: This command does not support a batch format.
Example
mail.example.com> dlpstatus
Component
Version
Last Updated
3.0.2.31
Never updated
dlpupdate
Description
Update RSA DLP Engine.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-29
Chapter 3
Note
DLP must already be configured via the DLP Global Settings page in the GUI before you can use the
dlpupdate command.
Usage
Commit: This command does not require a commit.
Cluster Management: This command is can be used at cluster, group or machine mode.
Batch Command: This command supports a batch format.
Batch Format
The batch format of the dlpupdate command forces an update of the DLP engine even if no changes are
detected.
dlpupdate [force]
Example
mail.example.com> dlpupdate
Checking for available updates. This may take a few seconds..
Could not check for available updates. Please check your Network and Service Updates
settings and retry.
emconfig
Description
Configure the interoperability settings for RSA Enterprise Manager.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-30
Chapter 3
Note
RSA Enterprise Manager must already be configured via the DLP Global Settings page in the GUI before
you can use the emconfig command. You cannot enable this functionality using the CLI, only edit the
existing settings.
Usage
Commit: This command requires a commit.
Cluster Management: This command is can be used at cluster, group or machine mode.
Batch Command: This command does not support a batch format.
Batch Format
To set up a connection between the Email Security appliance and RSA Enterprise Manager:
emconfig setup [options]
Table 3-1
Option
Description
--remote_host
--remote_port
--local_port
--enable_ssl
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-31
Chapter 3
[20002]>
Enable SSL communication to EM [N]>
Advanced Settings:
RSA Enterprise Manager GUID: emlocalsite
Device Vendor name: Cisco Systems
Device Status Interval: 5 seconds
Polling Cycle Interval: 30 seconds
Connection Throttle Interval: 0 milliseconds
Max event archive size: 31457280 bytes
Max files in event archive: 50
Max file size in event archive: 10485760 MB
Max size of event.xml file: 1048576 MB
Interoperability subsystem heartbeat interval: 500 milliseconds
Heartbeat service attempts before failing: 3
Connection timeout duration: 30 seconds
Command status timeout duration: 30 seconds
Max chunk size: 1000
Msg exchange cycle: 1
Do you want to change advanced settings? [N]>
emdiagnostic
Description
Diagnostic tool for RSA EM on ESA.
Usage
Commit: This command does not require a commit.
Cluster Management: This command can be used in all three machine modes (cluster, group, machine).
Batch Command: This command does not support a batch format.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-32
Chapter 3
Usage
Commit: This command requires a commit.
Cluster Management: This command can be used in all three machine modes (cluster, group, machine).
Batch Command: This command does not support a batch format.
Examples
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-33
Chapter 3
3. Split
Enter S/MIME action:
[1]> 3
Choose the operation you want to perform:
- NEW - Create a new S/MIME sending profile.
- EDIT - Edit a S/MIME sending profile.
- RENAME - Rename a S/MIME sending profile.
- DELETE - Delete a S/MIME sending profile.
- IMPORT - Import a S/MIME sending profile from a file
- EXPORT - Export a S/MIME sending profile to a file
- PRINT - Display S/MIME sending profiles.
[]> print
S/MIME Sending Profiles
Name
Certificate
S/MIME Mode
--------- --------------- -----------hr_sign_a smime_signing
Sign/Encrypt
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-34
Chapter 3
.
C=IN,ST=KA,L=BN,O=Cisco,OU=stg,CN=cert_for_enc,[email protected]
Choose the operation you want to perform:
- NEW - Create a new S/MIME Public Key.
- EDIT - Edit a S/MIME Public Key.
- RENAME - Rename a S/MIME Public Key.
- DELETE - Delete a S/MIME Public Key.
- IMPORT - Import the list of S/MIME Public Keys from a file.
- EXPORT - Export the list of S/MIME Public Keys to a file.
- PRINT - Display S/MIME Public Keys.
[]> print
S/MIME Public Keys
Name
Emails
--------- ------------------------hr_signin [email protected]
Domains
------------------------dns.vm30bsd0008.ibqa
Remaining
--------145 days
Domain Keys
This section contains the following CLI commands:
domainkeysconfig
domainkeysconfig
Description
Configure DomainKeys/DKIM support.
Usage
Commit: This command requires a commit.
Cluster Management: This command can be used in all three machine modes (cluster, group, machine).
Batch Command: This command supports a batch format.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-35
Chapter 3
Domain Keys
Table 3-2
Argument
Description
<name>
<type>
<domain>
<selector>
<user-list>
[options]
--key_name
--canon
--body_canon
--header_canon
--body_length
--headers_select
--custom_headers
--i_tag
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-36
Chapter 3
Table 3-2
Argument
Description
--agent_identity
--q_tag
--t_tag
--x_tag
--expiration_time
--z_tag
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-37
Chapter 3
Domain Keys
qtag <q_tag>
ttag <t_tag>
xtag <x_tag> [<expiration_time>]
ztag <z_tag>
new <user-list>
delete <user-list>
print
clear
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-38
Chapter 3
Table 3-3
Argument
Description
--name
--min_key_size
--max_key_size
--max_signatures_num
--key_query_timeout
--max_systemtime_diverge
nce
--use_body_length
--tempfail_action
--tempfail_response_code
--tempfail_response_text
--permfail_action
--permfail_response_code
--permfail_response_text
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-39
Chapter 3
Domain Keys
Table 3-4
Argument
Description
--generate_key
--use_key
--public_key
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-40
Chapter 3
Delete a key:
domainkeysconfig keys delete <key_name>
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-41
Chapter 3
Domain Keys
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-42
Chapter 3
The domain field forms the basis of the public-key query. The value in
this field MUST match the domain of the sending email address or MUST
be one of the parent domains of the sending email address. This value
becomes the "d" tag of the Domain-Keys signature.
Enter the domain name of the signing domain:
[]> example.com
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-43
Chapter 3
Domain Keys
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-44
Chapter 3
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-45
Chapter 3
Domain Keys
[1]>
The answers to the following questions will be used to construct DKIM text
record for DNS. It can be used to publish information about this profile.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-46
Chapter 3
DMARC Verification
This section contains the following CLI commands:
dmarcconfig
dmarcconfig
Description
Configure DMARC settings.
Usage
Commit: This command requires a commit.
Cluster Management: This command can be used in all three machine modes (cluster, group, machine).
Batch Command: This command supports a batch format.
Argument
Description
<name>
[options]
--rejectpolicy_action
The message action that AsyncOS must take when the policy in
DMARC record is reject. Possible values are reject,
quarantine, or none.
--rejectpolicy_response_code
--rejectpolicy_response_text
--rejectpolicy_quarantine
--quarantinepolicy_action
The message action that AsyncOS must take when the policy in
DMARC record is quarantine. Possible values are quarantine
or none.
--quarantinepolicy_quarantine
--tempfail_action
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-47
Chapter 3
DMARC Verification
Argument
Description
--tempfail_response_code
--tempfail_response_text
--permfail_action
--permfail_response_code
--permfail_response_text
Options
Description
--report_schedule
--error_reports
--org_name
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-48
Chapter 3
Options
Description
--contact_info
--copy_reports
Send copy of all the DMARC aggregate reports to specific users, for
example, internal users who perform analysis on the aggregate reports.
Enter an email address or multiple addresses separated by commas.
--bypass_addresslist
--bypass_headers
You can choose only address lists created with full email
addresses.
Example
The following example shows how to setup a DMARC verification profile and edit the global settings of
DMARC verification profiles.
mail.example.com> dmarcconfig
Number of DMARC Verification Profiles: 1
Daily report generation time is: 00:00
Error reports enabled: No
Reports sent on behalf of:
Contact details for reports:
Send a copy of aggregate reports to: None Specified
Bypass DMARC verification for senders from addresslist: None Specified
Bypass DMARC verification for messages with header fields: None Specified
Choose the operation you want to perform:
- PROFILES - Manage DMARC verification profiles.
- SETUP - Change global settings.
[]> profiles
There are currently 1 DMARC verification profiles defined.
Choose the operation you want to perform:
- NEW - Create a new DMARC verification profile.
- EDIT - Modify a DMARC verification profile.
- DELETE - Delete a DMARC verification profile.
- PRINT - Display DMARC verification profiles.
- IMPORT - Import DMARC verification profiles from a file.
- EXPORT - Export DMARC verification profiles to a file.
- CLEAR - Clear all DMARC verification profiles.
[]> new
Enter the name of the new DMARC verification profile:
[]> dmarc_ver_profile_1
Select the message action when the policy in DMARC record is reject:
1. No Action
2. Quarantine the message
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-49
Chapter 3
DMARC Verification
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-50
Chapter 3
(Yes/No) [N]>
Would you like to bypass DMARC verification for an addresslist? (Yes/No) [N]>
Would you like to bypass DMARC verification for specific header fields? (Yes/No) [N]> y
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-51
Chapter 3
DNS
DNS
This section contains the following CLI commands:
dig
dnsconfig
dnsflush
dnshostprefs
dnslistconfig
dnslisttest
dnsstatus
dig
Description
Look up a record on a DNS server
Usage
Commit: This command does not require a commit.
Cluster Management: This command can be used in all three machine modes (cluster, group, machine).
Batch Command: This command supports a batch format.
Batch Format
The batch format of the dig command can be used to perform all the functions of the traditional CLI
command.
These are the options available for the dig commands batch format
-s <source_ip>
-t
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-52
Chapter 3
-u
Example
The following example explicitly specifies a DNS server for the lookup.
mail.com> dig @111.111.111.111 example.com MX
IN
10800
;; AUTHORITY SECTION:
example.com.
;; ADDITIONAL SECTION:
example.com. 10800 IN
example.com. 10800 IN
example.com.
300
IN
;;
;;
;;
;;
Note
IN
10800
A
AAAA
A
MX
MX
IN
10 mexample.com.
NS
test.example.com.
111.111.111.111
2620:101:2004:4201::bd
111.111.111.111
The dig command filters out the information in the Authority and Additional sections if you do not
explicitly specify the DNS server when using the command.
dnsconfig
Description
Configure DNS setup
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-53
Chapter 3
DNS
Usage
Commit: This command requires a commit.
Cluster Management: This command can be used in all three machine modes (cluster, group, machine).
Batch Command: This command supports a batch format.
Batch Format
The batch format of the dnsconfig command can be used to perform all the functions of the traditional
CLI command.
Command arguments:
<ns_ip> - The IP address of the nameserver. Separate multiple IP addresses with commas.
<priority> - The priority for this entry.
Note
Nameserver arguments:
<ns_domain> - The domain to override.
<ns_name> - The name of the nameserver.
<ns_ip> - The IP address of the nameserver.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-54
Chapter 3
Note
You can override certain domains by specifying an alternate name server for that domain.
Deleting nameservers:
dnsconfig roots delete <ns_domain> [ns_name]
Note
When deleting, if you do not specify an ns_name, then all nameservers for that domain will be removed.
Clearing all DNS settings and automatically configuring the system to use the Internet root servers:
dnsconfig roots
Example
Each user-specified DNS server requires the following information:
Hostname
IP address
Syntax
Description
new
Add a new alternate DNS server to use for specific domains or local
DNS server.
delete
edit
setup
mail3.example.com> dnsconfig
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-55
Chapter 3
DNS
Do you want the Gateway to use the Internet's root DNS servers or would you like
it to use your own DNS servers?
1. Use Internet root DNS servers
2. Use own DNS cache servers
[1]> 1
Choose the IP interface for DNS traffic.
1. Auto
2. Management (10.92.149.70/24: mail3.example.com)
[1]>
Enter the number of seconds to wait before timing out reverse DNS lookups.
[20]>
Enter the minimum TTL in seconds for DNS cache.
[1800]>
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-56
Chapter 3
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-57
Chapter 3
DNS
[]>
dnsflush
Description
Clear all entries from the DNS cache.
Usage
Commit: This command does not require a commit.
Cluster Management: This command is restricted to machine mode.
Batch Command: This command does not support a batch format
Example
mail3.example.com> dnsflush
Are you sure you want to clear out the DNS cache? [N]> Y
dnshostprefs
Description
Configure IPv4/IPv6 DNS preferences
Usage
Commit: This command requires a commit.
Cluster Management: This command is restricted to machine mode.
Batch Command: This command does not support a batch format
Example
mail3.example.com> dnshostprefs
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-58
Chapter 3
3. Require IPv4
4. Require IPv6
[2]> 3
dnslistconfig
Description
Configure DNS List services support
Usage
Commit: This command requires a commit.
Cluster Management: This command is restricted to machine mode.
Batch Command: This command does not support a batch format
Example
mail3.example.com> dnslistconfig
Current DNS List Settings:
Negative Response TTL: 1800 seconds
DNS List Query Timeout: 3 seconds
Choose the operation you want to perform:
- SETUP - Configure general settings.
[]> setup
Enter the cache TTL for negative responses in seconds:
[1800]> 1200
Enter the query timeout in seconds:
[3]>
Settings updated.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-59
Chapter 3
DNS
dnslisttest
Description
Test a DNS lookup for a DNS-based list service.
Usage
Commit: This command does not require a commit.
Cluster Management: This command is restricted to machine mode.
Batch Command: This command does not support a batch format
Example
mail3.example.com> dnslisttest
Enter the query server name:
[]> mail4.example.com
Enter the test IP address to query for:
[127.0.0.2]> 10.10.1.11
Querying: 10.10.1.11.mail4.example.com
Result: MATCHED
dnsstatus
Description
Display DNS statistics.
Usage
Commit: This command does not require a commit.
Cluster Management: This command is restricted to machine mode.
Batch Command: This command does not support a batch format.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-60
Chapter 3
Example
mail3.example.com> dnsstatus
Status as of: Mon Apr 18 10:58:07 2005 PDT
Counters:
DNS Requests
Network Requests
Cache Hits
Cache Misses
Cache Exceptions
Cache Expired
Reset
1,115
186
1,300
1
0
185
Uptime
1,115
186
1,300
1
0
185
Lifetime
1,115
186
1,300
1
0
185
General Management/Administration/Troubleshooting
This section contains the following CLI commands:
addressconfig
adminaccessconfig
certconfig
date
diagnostic
diskquotaconfig
ecconfig
ecstatus
ecupdate
encryptionconfig
encryptionstatus
encryptionupdate
featurekey
featurekeyconfig
generalconfig
healthcheck
healthconfig
ntpconfig
reboot
repengstatus
repengstatus
resume
resumedel
resumelistener
revert
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-61
Chapter 3
General Management/Administration/Troubleshooting
settime
settz
shutdown
sshconfig
status
supportrequest
supportrequeststatus
supportrequestupdate
suspend
suspenddel
suspendlistener
tcpservices
techsupport
tlsverify
trace
trackingconfig
updateconfig
updatenow
upgrade
version
wipedata
addressconfig
Description
The addressconfig command is used to configure the From: Address header. You can specify the
display, user, and domain names of the From: address. You can also choose to use the Virtual Gateway
domain for the domain name. Use the addressconfig command for mail generated by AsyncOS for the
following circumstances:
Anti-virus notifications
Bounces
Reports
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-62
Chapter 3
In the following example, the From: Address for notifications is changed from: Mail Delivery System
(the default) to Notifications [[email protected]]
[MAILER-DAEMON@domain]
Usage
Commit: This command requires a commit.
Cluster Management: This command can be used in all three machine modes (cluster, group, machine).
Batch Command: This command does not support a batch format.
Example
mail3.example.com> addressconfig
Current
Current
Current
Current
Current
Current
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-63
Chapter 3
General Management/Administration/Troubleshooting
adminaccessconfig
Description
Use the adminaccessconfig command to configure:
Usage
Commit: This command requires a commit.
Cluster Management: This command can be used in all three machine modes (cluster, group, machine).
Batch Command: This command supports a batch format.
Batch Format
The batch format of the adminaccessconfig command can be used to perform all the functions of the
traditional CLI command.
Select whether to allow access for all IP addresses or limit access to specific IP address/subnet/range
adminaccessconfig ipaccess <all/restrict/proxyonly/proxy>
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-64
Chapter 3
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-65
Chapter 3
General Management/Administration/Troubleshooting
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-66
Chapter 3
192.168.1.2-100
192.168.1.2-100
192.168.255.12
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-67
Chapter 3
General Management/Administration/Troubleshooting
the GUI. You can use the login banner to display internal security information or best practice
instructions for the appliance. For example, you can create a simple note that saying that unauthorized
use of the appliance is prohibited or a detailed warning concerning the organizations right to review
changes made by the user to the appliance.
The maximum length of the login banner is 2000 characters to fit 80x25 consoles. A login banner can
be imported from a file in the /data/pub/configuration directory on the appliance. After creating the
banner, commit your changes.
In the following example, the login banner Use of this system in an unauthorized manner is prohibited
is added to the appliance:
mail.example.com> adminaccessconfig
Choose the operation you want to perform:
- BANNER - Configure login message (banner) for appliance administrator login.
- WELCOME - Configure welcome message (post login message) for appliance administrator
login.
- IPACCESS - Configure IP-based access for appliance administrative interface.
- CSRF - Configure web UI Cross-Site Request Forgeries protection.
- HOSTHEADER - Configure option to use host header in HTTP requests.
- TIMEOUT - Configure GUI and CLI session inactivity timeout.
[]> banner
A banner has not been defined.
Choose the operation you want to perform:
- NEW - Create a banner to display at login.
- IMPORT - Import banner text from a file.
[]> new
Enter or paste the banner text here. Enter CTRL-D on a blank line to end.
Use of this system in an unauthorized manner is prohibited.
^D
Choose the operation you want to perform:
- BANNER - Configure login message (banner) for appliance administrator login.
- WELCOME - Configure welcome message (post login message) for appliance administrator
login.
- IPACCESS - Configure IP-based access for appliance administrative interface.
- CSRF - Configure web UI Cross-Site Request Forgeries protection.
- HOSTHEADER - Configure option to use host header in HTTP requests.
- TIMEOUT - Configure GUI and CLI session inactivity timeout.
[]> banner
Banner: Use of this system in an unauthorized manner is prohibited.
Choose the operation you want to perform:
- NEW - Create a banner to display at login.
- IMPORT - Import banner text from a file.
- DELETE - Remove the banner.
[]>
Note
The CLI session timeout applies only to the connections using Secure Shell (SSH), SCP, and direct serial
connection. Any uncommitted configuration changes at the time of CLI session timeout will be lost.
Make sure that you commit the configuration changes as soon as they are made.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-68
Chapter 3
mail.example.com> adminaccessconfig
Choose the operation you want to perform:
- BANNER - Configure login message (banner) for appliance administrator login.
- WELCOME - Configure welcome message (post login message) for appliance administrator
login.
- IPACCESS - Configure IP-based access for appliance administrative interface.
- CSRF - Configure web UI Cross-Site Request Forgeries protection.
- HOSTHEADER - Configure option to use host header in HTTP requests.
- TIMEOUT - Configure GUI and CLI session inactivity timeout.
[]> timeout
Enter WebUI inactivity timeout(in minutes):
[30]> 32
Enter CLI inactivity timeout(in minutes):
[30]> 32
Note
After committing the changes, the new CLI session timeout takes affect only during the subsequent
login.
certconfig
Description
Configure security certificates and keys.
Usage
Commit: This command requires a commit.
Cluster Management: This command can be used in all three machine modes (cluster, group, machine).
Batch Command: This command does not support a batch format.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-69
Chapter 3
General Management/Administration/Troubleshooting
Issued By
-------------------Cisco Appliance Demo
Status
------------Active
Remaining
--------3467 days
List of Certificates
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-70
Chapter 3
Name
Common Name
Issued By
Status
Remaining
-------- ------------------- -------------------- ------------- --------partner.c brutus.partner.com
brutus.partner
Active
30 days
Demo
Cisco Appliance Demo Cisco Appliance Demo Active
3467 days
Choose the operation you want to perform:
- IMPORT - Import a certificate from a local PKCS#12 file
- PASTE - Paste a certificate into the CLI
- NEW - Create a self-signed certificate and CSR
- EDIT - Update certificate or view the signing request
- EXPORT - Export a certificate
- DELETE - Remove a certificate
- PRINT - View certificates assigned to services
[]>
Issued By
-------------------brutus.neuronio.pt
Status
------------Expired
Remaining
---------4930
Active
3467 days
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-71
Chapter 3
General Management/Administration/Troubleshooting
[1]> 1
Enter a name for this certificate profile:
> example.com
Enter Common Name:
> example.com
Enter Organization:
> Example
Enter Organizational Unit:
> Org
Enter Locality or City:
> San Francisoc
Enter State or Province:
> CA
Enter Country (2 letter code):
> US
Duration before expiration (in days):
[3650]>
1. 1024
2. 2048
Enter size of private key:
[2]>
Do you want to view the CSR? [Y]> y
-----BEGIN CERTIFICATE REQUEST----MIICrTCCAZUCAQAwaDELMAkGA1UEBhMCVVMxFDASBgNVBAMTC2V4YW1wbGUuY29t
MRYwFAYDVQQHEw1TYW4gRnJhbmNpc29jMRAwDgYDVQQKEwdleGFtcGxlMQswCQYD
VQQIEwJDQTEMMAoGA1UECxMDb3JnMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIB
CgKCAQEA+NwamZyX7VgTZka/x1I5HHrN9V2MPKXoLq7FjzUtiIDwznElrKIuJovw
Svonle6GvFlUHfjv8B3WobOzk5Ny6btKjwPrBfaY+qr7rzM4lAQKHM+P6l+lZnPU
P05N9RCkLP4XsUuyY6Ca1WLTiPIgaq2fR8Y0JX/kesZcGOqlde66pN+xJIHHYadD
oopOgqi6SLNfAzJu/HEu/fnSujG4nhF0ZGlOpVUx4fg33NwZ4wVl0XBk3GrOjbbA
ih9ozAwfNzxb57amtxEJk+pW+co3uEHLJIOPdih9SHzn/UVU4hiu8rSQR19sDApp
kfdWcfaDLF9tnQJPWSYoCh0USgCc8QIDAQABoAAwDQYJKoZIhvcNAQEFBQADggEB
AGiVhyMAZuHSv9yA08kJCmrgO89yRlnDUXDDo6IrODVKx4hHTiOanOPu1nsThSvH
7xV4xR35T/QV0U3yPrL6bJbbwMySOLIRTjsUcwZNjOE1xMM5EkBM2BOI5rs4l59g
FhHVejhG1LyyUDL0U82wsSLMqLFH1IT63tzwVmRiIXmAu/lHYci3+vctb+sopnN1
lY1OIuj+EgqWNrRBNnKXLTdXkzhELOd8vZEqSAfBWyjZ2mECzC7SG3evqkw/OGLk
AilNXHayiGjeY+UfWzF/HBSekSJtQu6hIv6JpBSY/MnYU4tllExqD+GX3lru4xc4
zDas2rS/Pbpn73Lf503nmsw=
-----END CERTIFICATE REQUEST----List of Certificates
Name
Common Name
Issued By
Status
Remaining
--------- ------------------- -------------------- ------------- --------example.c example.com
example.com
Valid
3649 days
partner.c brutus.partner.com
brutus.partner.com Valid
30 days
Demo
Cisco Appliance Demo Cisco Appliance Demo Active
3467 days
Choose the operation you want to perform:
- IMPORT - Import a certificate from a local PKCS#12 file
- PASTE - Paste a certificate into the CLI
- NEW - Create a self-signed certificate and CSR
- EDIT - Update certificate or view the signing request
- EXPORT - Export a certificate
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-72
Chapter 3
Issued By
-------------------Cisco Appliance Demo
Status
------------Active
Remaining
--------3329 days
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-73
Chapter 3
General Management/Administration/Troubleshooting
[]> [email protected]
Add another member? [Y]> n
Begin entering domain entries for 'subjectAltName'.
Enter the DNS you want to add.
[]> domain.com
Add another member? [Y]> n
Do you want to view the CSR? [Y]> n
List of Certificates
Name
Common Name
--------- -------------------smime_sig CN
Demo
Cisco Appliance Demo
Issued By
-------------------CN
Cisco Appliance Demo
Status
------------Valid
Active
Remaining
--------3649 days
3329 days
date
Description
Displays the current date and time
Usage
Commit: This command does not require a commit.
Cluster Management: This command can be used in all three machine modes (cluster, group, machine).
Batch Command: This command does not support a batch format.
Example
mail.example.com> date
Tue Mar 10 11:30:21 2015 GMT
diagnostic
Description
Use the diagnostic command to:
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-74
Chapter 3
diagnostic Subcommands
Option
Sub Commands
Availability
RAID
No Sub Commands
FLUSH
(deprecated)
NETWORK
ARPSHOW
SMTPPING
TCPDUMP
REPORTING
DELETEDB
DISABLE
TRACKING
DELETEDB
DEBUG
RELOAD
No Sub Commands
Usage
Commit: This command does not require a commit.
Cluster Management: This command is restricted to machine mode. It is further restricted to the login
host (i.e., the specific machine you are logged onto). This command requires access to the local file
system.
Batch Command: This command supports a batch format.
Batch Format
The batch format of the diagnostic command can be used to check RAID status, clear caches and show
the contents of the ARP cache. To invoke as a batch command, use the following formats:
Use the batch format to perform the following operations:
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-75
Chapter 3
General Management/Administration/Troubleshooting
diagnostic raid
diagnostic reload
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-76
Chapter 3
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-77
Chapter 3
General Management/Administration/Troubleshooting
diskquotaconfig
View or configure disk space allocation for reporting and tracking, quarantines, log files, packet
captures, and configuration files.
See User Guide for AsyncOS for Cisco Email Security Appliances for complete information about this
feature.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-78
Chapter 3
Usage
Commit: This command requires a commit.
Cluster Management: This command is restricted to machine mode.
Batch Command: This command supports a batch format.
Batch Format
diskquotaconfig <feature> <quota> [<feature> <quota> [<feature> <quota>[<feature>
<quota>]]]
Example
mail.example.com> diskquotaconfig
Service
Disk Usage(GB)
Quota(GB)
--------------------------------------------------------------------------Spam Quarantine (EUQ)
1
1
Policy, Virus & Outbreak Quarantines
1
3
Reporting
5
10
Tracking
1
10
Miscellaneous Files
5
30
System Files Usage : 5 GB
User Files Usage : 0 GB
Total
13
54 of 143
Choose the operation you want to perform:
- EDIT - Edit disk quotas
[]> edit
Enter the number of the service for which you would like to edit disk quota:
1. Spam Quarantine (EUQ)
2. Policy, Virus & Outbreak Quarantines
3. Reporting
4. Tracking
5. Miscellaneous Files
[1]> 1
Enter the new disk quota [1]> 1
Disk quota for Spam Quarantine (EUQ) changed to 1
Service
Disk Usage(GB)
Quota(GB)
--------------------------------------------------------------------------Spam Quarantine (EUQ)
1
1
Policy, Virus & Outbreak Quarantines
1
3
Reporting
5
10
Tracking
1
10
Miscellaneous Files
5
30
System Files Usage : 5 GB
User Files Usage : 0 GB
Total
13
54 of 143
Choose the operation you want to perform:
- EDIT - Edit disk quotas
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-79
Chapter 3
General Management/Administration/Troubleshooting
[]>
ecconfig
Set or clear the enrollment client that is used to obtain certificates for use with the URL Filtering feature.
Do not use this command without guidance from Cisco support.
Entries must be in the format <hostname:port> or <IPv4 address:port>. Port is optional.
To specify the default server, enter ecconfig server default.
Usage
Commit: This command requires a commit.
Cluster Management: This command can be used at all levels in a cluster.
Batch Command: This command supports a batch format.
Batch Format
Example
mail.example.com> ecconfig
Enrollment Server: Not Configured (Use Default)
Choose the operation you want to perform:
- SETUP - Configure the Enrollment Server
[]> setup
Do you want to use non-default Enrollment server?
WARNING: Do not configure this option without the assistance of Cisco Support.
Incorrect configuration can impact the services using certificates from the Enrollment
server. [N]> y
[]> 192.0.2.1
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-80
Chapter 3
ecstatus
Display the current version of the enrollment client that is used to automatically obtain certificates for
use with the URL Filtering feature.
Usage
Commit: This command does not require a commit.
Cluster Management: This command is restricted to machine mode.
Batch Command: This command does not support a batch format.
Example
mail.example.com> ecstatus
Component
Version
Enrollment Client
1.0.2-046
Last Updated
Never updated
ecupdate
Manually update the enrollment client that is used to automatically obtain certificates for use with the
URL Filtering feature. Normally, these updates occur automatically. Do not use this command without
guidance from Cisco support.
If you use the force parameter (ecupdate [force]) the client is updated even if no changes are detected.
Usage
Commit: This command does not require a commit.
Cluster Management: This command is restricted to machine mode.
Batch Command: This command supports a batch format.
Batch Format
> ecupdate [force]
Example
mail.example.com> ecupdate
Requesting update of Enrollment Client.
encryptionconfig
Configure email encryption.
Usage
Commit: This command requires a commit.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-81
Chapter 3
General Management/Administration/Troubleshooting
Example
The following example shows modifications to an encryption profile:
mail.example.com> encryptionconfig
IronPort Email Encryption: Enabled
Choose the operation you want to perform:
- SETUP - Enable/Disable IronPort Email Encryption
- PROFILES - Configure email encryption profiles
- PROVISION - Provision with the Cisco Registered Envelope Service
[]> setup
PXE Email Encryption: Enabled
Would you like to use PXE Email Encryption? [Y]>
Key Service
----------Hosted Service
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-82
Proxied
------No
Provision Status
---------------Not Provisioned
Chapter 3
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-83
Chapter 3
General Management/Administration/Troubleshooting
Key Service
----------Hosted Service
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-84
Proxied
------No
Provision Status
---------------Not Provisioned
Chapter 3
encryptionstatus
Description
The encryptionstatus command shows the version of the PXE Engine and Domain Mappings file on
the Email Security appliance, as well as the date and time the components were last updated.
Usage
Commit: This command does not require a commit.
Cluster Management: This command is restricted to machine mode.
Batch Command: This command does not support a batch format.
Example
mail3.example.com> encryptionstatus
Component
PXE Engine
Domain Mappings File
Version
6.7.1
1.0.0
Last Updated
17 Nov 2009 00:09 (GMT)
Never updated
encryptionupdate
Description
The encryptionupdate command requests an update to the PXE Engine on the Email Security
appliance.
Usage
Commit: This command does not require a commit.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-85
Chapter 3
General Management/Administration/Troubleshooting
Cluster Management: This command is restricted to machine mode. It is further restricted to the login
host (i.e., the specific machine you are logged onto).
Batch Command: This command does not support a batch format.
Example
mail3.example.com> encryptionupdate
Requesting update of PXE Engine.
featurekey
Description
The featurekey command lists all functionality enabled by keys on the system and information related
to the keys. It also allows you to activate features using a key or check for new feature keys.
For virtual appliances, see also loadlicense and showlicense.
Usage
Commit: This command requires a commit.
Cluster Management: This command is restricted to machine mode.
Batch Command: This command does not support a batch format
Example
In this example, the featurekey command is used to check for new feature keys.
mail3.example.com> featurekey
Module
Quantity
Outbreak Filters
1
2014
IronPort Anti-Spam
1
2014
Sophos Anti-Virus
1
2014
Bounce Verification
1
2014
Incoming Mail Handling
1
2014
IronPort Email Encryption
1
2014
RSA Email Data Loss Prevention
1
2014
McAfee
1
2014
Choose the operation you want to perform:
- ACTIVATE - Activate a (pending) key.
- CHECKNOW - Check now for new feature keys.
[]> checknow
No new feature keys are available.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-86
Status
Active
Remaining
28 days
Expiration Date
Tue Feb 25 06:40:53
Dormant
30 days
Active
26 days
Dormant
30 days
Active
20 days
Dormant
30 days
Active
25 days
Dormant
30 days
Chapter 3
featurekeyconfig
Description
The featurekeyconfig command allows you to configure the machine to automatically download
available keys and update the keys on the machine.
Usage
Commit: This command requires a commit.
Cluster Management: This command can be used in all three machine modes (cluster, group, machine.
Batch Command: This command does not support a batch format.
Example
In this example, the featurekeyconfig command is used to enable the autoactivate and autocheck
features.
mail3.example.com> featurekeyconfig
Automatic activation of downloaded keys: Disabled
Automatic periodic checking for new feature keys: Disabled
Choose the operation you want to perform:
- SETUP - Edit feature key configuration.
[]> setup
Automatic activation of downloaded keys: Disabled
Automatic periodic checking for new feature keys: Disabled
Choose the operation you want to perform:
- AUTOACTIVATE - Toggle automatic activation of downloaded keys.
- AUTOCHECK - Toggle automatic checking for new feature keys.
[]> autoactivate
Do you want to automatically apply downloaded feature keys? [N]> y
Automatic activation of downloaded keys: Enabled
Automatic periodic checking for new feature keys: Disabled
Choose the operation you want to perform:
- AUTOACTIVATE - Toggle automatic activation of downloaded keys.
- AUTOCHECK - Toggle automatic checking for new feature keys.
[]> autocheck
Do you want to periodically query for new feature keys? [N]> y
Automatic activation of downloaded keys: Enabled
Automatic periodic checking for new feature keys: Enabled
generalconfig
Description
The generalconfig command allows you to configure browser settings.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-87
Chapter 3
General Management/Administration/Troubleshooting
Usage
Commit: This command requires commit.
Cluster Management: This command can be used in all three machine modes (cluster, group, machine).
Batch Command: This command supports a batch format. For details, see the inline help by typing the
command: help generalconfig.
healthcheck
Description
Checks the health of your Email Security appliance. Health check analyzes historical data (up to three
months) in the current Status Logs to determine the health of the appliance.
Usage
Commit: This command does not require a commit.
Cluster Management: This command can be used in all three machine modes (cluster, group, machine).
Batch Command: This command does not support a batch format.
Example
mail.example.com> healthcheck
Analyzing the system to determine current health of the system.
The analysis may take a while, depending on the size of the historical data.
System analysis is complete.
The analysis indicates that the system has experienced the following issue(s)recently:
Entered Resource conservation mode
Delay in mail processing
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-88
Chapter 3
healthconfig
Description
Configure the threshold of various health parameters of your appliance such as CPU usage, maximum
messages in work queue and so on
Usage
Commit: This command requires commit.
Cluster Management: This command can be used in all three machine modes (cluster, group, machine).
Batch Command: This command does not support a batch format.
Example
mail.example.com> healthconfig
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-89
Chapter 3
General Management/Administration/Troubleshooting
Do you want to receive alerts if the overall CPU usage exceeds threshold value?[N]> n
ntpconfig
Description
The ntpconfig command configures AsyncOS to use Network Time Protocol (NTP) to synchronize the
system clock with other computers. NTP can be turned off using the settime command.
Usage
Commit: This command requires commit.
Cluster Management: This command can be used in all three machine modes (cluster, group, machine).
Batch Command: This command does not support a batch format.
Example
mail3.example.com> ntpconfig
Currently configured NTP servers:
1. time.ironport.com
Choose the operation you want to perform:
- NEW - Add a server.
- DELETE - Remove a server.
- SOURCEINT - Set the interface from whose IP address NTP queries should originate.
[]> new
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-90
Chapter 3
Please enter the fully qualified hostname or IP address of your NTP server.
[]> ntp.example.com
Currently configured NTP servers:
1. time.ironport.com
2. bitsy.mit.edi
Choose the operation you want to perform:
- NEW - Add a server.
- DELETE - Remove a server.
- SOURCEINT - Set the interface from whose IP address NTP queries should
originate.
[]> sourceint
When initiating a connection to an NTP server, the outbound IP address
used is chosen automatically.
If you want to choose a specific outbound IP address,please select
its interface name now.
1. Auto
2. Management (172.19.0.11/24: elroy.run)
3. PrivateNet (172.19.1.11/24: elroy.run)
4. PublicNet (172.19.2.11/24: elroy.run)
[1]> 1
Currently configured NTP servers:
1. time.ironport.com
2. bitsy.mit.edi
Choose the operation you want to perform:
- NEW - Add a server.
- DELETE - Remove a server.
- SOURCEINT - Set the interface from whose IP address NTP queries should originate.
[]>
mail3.example.com> commit
Please enter some comments describing your changes:
[]> Added new NTP server
Do you want to save the current configuration for rollback? [Y]> n
Changes committed: Fri May 23 11:42:12 2014 GMT
reboot
Description
Restart the appliance.
Usage
Commit: This command does not require a commit.
Cluster Management: This command is restricted to machine mode.
Batch Command: This command does not support a batch format.
Example
mail3.example.com> reboot
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-91
Chapter 3
General Management/Administration/Troubleshooting
repengstatus
Description
Request version information of Reputation Engine.
Usage
Commit: This command does not require a commit.
Cluster Management: This command is restricted to machine mode.
Batch Command: This command does not support a batch format.
Example
mail.example.com> repengstatus
Component
Reputation Engine
Reputation Engine Tools
Last Update
28 Jan 2014 23:47 (GMT +00:00)
28 Jan 2014 23:47 (GMT +00:00)
Version
1
1
resume
Description
Resume receiving and deliveries
Usage
Commit: This command does not require a commit.
Cluster Management: This command is restricted to machine mode.
Batch Command: This command does not support a batch format.
Example
mail3.example.com> resume
Receiving resumed for Listener 1.
Mail delivery resumed.
Mail delivery for individually suspended domains must be resumed individually.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-92
Chapter 3
resumedel
Description
Resume deliveries.
Usage
Commit: This command does not require a commit.
Cluster Management: This command is restricted to machine mode.
Batch Command: This command does not support a batch format.
Example
mail.example.com> resumedel
Currently suspended domains:
1. domain1.com
2. domain2.com
3. domain3.com
Enter one or more domains [comma-separated] to which you want to resume delivery.
[ALL]> domain1.com, domain2.com
Mail delivery resumed.
resumelistener
Description
Resume receiving on a listener.
Usage
Commit: This command does not require a commit.
Cluster Management: This command is restricted to machine mode.
Batch Command: This command does not support a batch format.
Example
mail3.example.com> resumelistener
Choose the listener(s) you wish to resume.
Separate multiple entries with commas.
1. All
2. InboundMail
3. OutboundMail
[1]> 1
Receiving resumed.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-93
Chapter 3
General Management/Administration/Troubleshooting
mail3.example.com>
revert
Description
Revert to a previous release.
Usage
Commit: This command does not require a commit.
Cluster Management: This command can be used in all three machine modes (cluster, group, machine).
Batch Command: This command does not support a batch format.
Example
mail.example.com> revert
This command will revert the appliance to a previous version of AsyncOS.
WARNING: Reverting the appliance is extremely destructive.
The following data will be destroyed in the process:
- all configuration settings (including listeners)
- all log files
- all databases (including messages in Virus Outbreak and Policy quarantines)
- all reporting data (including saved scheduled reports)
- all message tracking data
- all IronPort Spam Quarantine message and end-user safelist/blocklist data
Available versions
=================
1. 9.1.0-019
Please select an AsyncOS version [1]:
Do you want to continue? [N]>
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-94
Chapter 3
settime
Description
The settime command allows you to manually set the time if you are not using an NTP server. The
command asks you if you want to stop NTP and manually set the system clock. Enter the time is using
this format: MM/DD/YYYY HH:MM:SS.
Usage
Commit: This command does not require a commit.
Cluster Management: This command is restricted to machine mode.
Batch Command: This command does not support a batch format.
Example
mail3.example.com> settime
WARNING: Changes to system time will take place immediately
and do not require the user to run the commit command.
Current time 09/23/2001 21:03:53.
This machine is currently running NTP.
In order to manually set the time, NTP must be disabled.
Do you want to stop NTP and manually set the time? [N]> Y
Please enter the time in MM/DD/YYYY HH:MM:SS format.
[]> 09/23/2001 21:03:53
Time set to 09/23/2001 21:03:53.
settz
Description
Set the local time zone.
Usage
Commit: This command requires a commit.
Cluster Management: This command can be used in all three machine modes (cluster, group, machine).
Batch Command: This command does not support a batch format.
Example
mail3.example.com> settz
Current time zone: Etc/GMT
Current time zone version: 2010.02.0
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-95
Chapter 3
General Management/Administration/Troubleshooting
shutdown
Description
Shut down the system to power off
Usage
Commit: This command does not require a commit.
Cluster Management: This command is restricted to machine mode.
Batch Command: This command does not support a batch format.
Example
mail3.example.com> shutdown
Enter the number of seconds to wait before abruptly closing connections.
[30]>
System shutting down.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-96
Chapter 3
Use the power button (in 30 seconds) to turn off the machine.
sshconfig
Description
Configure SSH server and user key settings.
Usage
Commit: This command requires a commit.
Cluster Management: This command is restricted to cluster mode.
Batch Command: This command does not support a batch format.
Reboot. Reboot is required for changes to take effect.
Example
In the following example, a new public key is installed for the administrator account:
mail.example.com> sshconfig
Choose the operation you want to perform:
- SSHD - Edit SSH server settings.
- USERKEY - Edit SSH User Key settings
[]> userkey
Currently installed keys for admin:
Choose the operation you want to perform:
- NEW - Add a new key.
- USER - Switch to a different user to edit.
[]> new
Please enter the public SSH key for authorization.
Press enter on a blank line to finish.
[-paste public key for user authentication here-]
Choose the operation you want to perform:
- SSHD - Edit SSH server settings.
- USERKEY - Edit SSH User Key settings
[]>
The following example shows how to edit the SSH server configuration.
mail.example.com> sshconfig
Choose the operation you want to perform:
- SSHD - Edit SSH server settings.
- USERKEY - Edit SSH User Key settings
[]> sshd
ssh server config settings:
Public Key Authentication Algorithms:
rsa1
ssh-dss
ssh-rsa
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-97
Chapter 3
General Management/Administration/Troubleshooting
Cipher Algorithms:
aes128-ctr
aes192-ctr
aes256-ctr
arcfour256
arcfour128
aes128-cbc
3des-cbc
blowfish-cbc
cast128-cbc
aes192-cbc
aes256-cbc
arcfour
[email protected]
MAC Methods:
hmac-md5
hmac-sha1
[email protected]
hmac-ripemd160
[email protected]
hmac-sha1-96
hmac-md5-96
Minimum Server Key Size:
1024
KEX Algorithms:
diffie-hellman-group-exchange-sha256
diffie-hellman-group-exchange-sha1
diffie-hellman-group14-sha1
diffie-hellman-group1-sha1
Choose the operation you want to perform:
- SETUP - Setup SSH server configuration settings
[]> setup
Enter the Public Key Authentication Algorithms do you want to use
[rsa1,ssh-dss,ssh-rsa]>
Enter the Cipher Algorithms do you want to use
[aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,c
ast128-cbc,aes192-cbc,aes256-cbc,arcfour,[email protected]]>
Enter the MAC Methods do you want to use
[hmac-md5,hmac-sha1,[email protected],hmac-ripemd160,[email protected],hmac-sha
1-96,hmac-md5-96]>
Enter the Minimum Server Key Size do you want to use
[1024]>
Enter the KEX Algorithms do you want to use
[diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-gr
oup14-sha1,diffie-hellman-group1-sha1]>
ssh server config settings:
Public Key Authentication Algorithms:
rsa1
ssh-dss
ssh-rsa
Cipher Algorithms:
aes128-ctr
aes192-ctr
aes256-ctr
arcfour256
arcfour128
aes128-cbc
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-98
Chapter 3
3des-cbc
blowfish-cbc
cast128-cbc
aes192-cbc
aes256-cbc
arcfour
[email protected]
MAC Methods:
hmac-md5
hmac-sha1
[email protected]
hmac-ripemd160
[email protected]
hmac-sha1-96
hmac-md5-96
Minimum Server Key Size:
1024
KEX Algorithms:
diffie-hellman-group-exchange-sha256
diffie-hellman-group-exchange-sha1
diffie-hellman-group14-sha1
diffie-hellman-group1-sha1
Choose the operation you want to perform:
- SETUP - Setup SSH server configuration settings
[]>
status
Description
Show system status.
Usage
Commit: This command does not require a commit.
Cluster Management: This command is restricted to machine mode.
Batch Command: This command does not support a batch format.
Example
mail3.example.com> status
Status as of:
Up since:
Last counter reset:
System status:
Oldest Message:
Feature - McAfee:
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-99
Chapter 3
General Management/Administration/Troubleshooting
[....]
Feature - Outbreak Filters:
161 days
Counters:
Receiving
Messages Received
Recipients Received
Rejection
Rejected Recipients
Dropped Messages
Queue
Soft Bounced Events
Completion
Completed Recipients
Current IDs
Message ID (MID)
Injection Conn. ID (ICID)
Delivery Conn. ID (DCID)
Gauges:
Connections
Current Inbound Conn.
Current Outbound Conn.
Queue
Active Recipients
Messages In Work Queue
Kilobytes Used
Kilobytes Free
Quarantine
Messages In Quarantine
Policy, Virus and Outbreak
Kilobytes In Quarantine
Policy, Virus and Outbreak
Reset
Uptime
Lifetime
62,049,822
62,049,823
290,920
290,920
62,049,822
62,049,823
3,949,663
11,606,037
11,921
219
3,949,663
11,606,037
2,334,552
13,598
2,334,552
50,441,741
332,625
50,441,741
99524480
51180368
17550674
Current
0
14
1
0
92
8,388,516
0
0
supportrequest
Description
Send a message to Cisco customer support. This command requires that the appliance is able to send
mail to the Internet. A trouble ticket is automatically created, or you can associate the support request
with an existing trouble ticket.
To access Cisco technical support directly from the appliance, your Cisco.com user ID must be
associated with your service agreement contract for this appliance. To view a list of service contracts
that are currently associated with your Cisco.com profile, visit the Cisco.com Profile Manager at
https://sso.cisco.com/autho/forms/CDClogin.html. If you do not have a Cisco.com user ID, register to
get one. See information about registering for an account in the online help or user guide for your release.
Usage
Commit: This command does not require a commit.
Cluster Management: This command is restricted to machine mode. It is further restricted to the login
host (i.e., the specific machine you are logged onto). This command requires access to the local file
system.
Batch Command: This command does not support a batch format.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-100
Chapter 3
Example
The following example shows a support request that is not related to an existing support ticket.
mail.example.com> supportrequest
Please Note:
If you have an urgent issue, please call one of our worldwide Support Centers
(www.cisco.com/support). Use this command to open a technical support request
for issues that are not urgent, such as:
- Request for information.
- Problem for which you have a work-around, but would like an alternative
solution.
Do you want to send the support request to [email protected]?
[Y]>
Do you want to send the support request to additional recipient(s)?
[N]>
Is this support request associated with an existing support ticket?
[N]>
Please select a technology related to this support request:
1. Security - Email and Web
2. Security - Management
[1]> 1
Please select a subtechnology related to this
1. Cisco Email Security Appliance (C1x0,C3x0,
Messages
2. Cisco Email Security Appliance (C1x0,C3x0,
3. Cisco Email Security Appliance (C1x0,C3x0,
4. Email Security Appliance - Virtual
[1]> 3
support request:
C6x0, X10x0) - Misclassified
C6x0, X10x0) - SBRS
C6x0, X10x0) - Other
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-101
Chapter 3
General Management/Administration/Troubleshooting
It is important to associate all your service contracts with your Cisco.com profile (CCO
ID) in order for you to receive complete access to support and
services from Cisco. Please follow the URLs below to associate your contract coverage on
your Cisco.com profile. If you do not have a CCO ID, please follow
the URL below to create a CCO ID.
How to create a CCO ID:
https://tools.cisco.com/RPF/register/register.do
How to associate your CCO ID with contract:
https://tools.cisco.com/RPFA/profile/profile_management.do
Frequently Asked Question:
http://www.cisco.com/web/ordering/cs_info/faqs/index.html
Select the CCOID
1. New CCOID
[1]>
Please enter the CCOID of the contact person :
[]> your name
The CCO ID may contain alphabets, numbers and '@', '.', '-' and '_' symbols.
Please enter the CCOID of the contact person :
[]> [email protected]
Please enter the name of the contact person :
[]> yourname
Please enter your email address:
[]> [email protected]
Please enter the contract ID:
[]> 1234
Please enter any additional contact information (e.g. phone number):
[]>
Please wait while configuration information is generated...
Do you want to print the support request to the screen?
[N]>
supportrequeststatus
Description
Display Support Request Keywords version information for requesting support from Cisco TAC.
Usage
Commit: This command does not require a commit.
Cluster Management: This command can be used in all three machine modes (cluster, group, machine).
Batch Command: This command does not support a batch format.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-102
Chapter 3
Example
mail.example.com> supportrequeststatus
Component
Support Request
Version
1.0
Last Updated
Never updated
supportrequestupdate
Description
Request manual update of Support Request Keywords for requesting support from Cisco TAC.
Usage
Commit: This command does not require a commit.
Cluster Management: This command can be used in all three machine modes (cluster, group, machine).
Batch Command: This command does not support a batch format.
Example
mail.example.com> supportrequestupdate
Requesting update of Support Request Keywords.
suspend
Description
Suspend receiving and deliveries
Usage
Commit: This command does not require a commit.
Cluster Management: This command is restricted to machine mode.
Batch Command: This command does not support a batch format.
Example
mail3.example.com> suspend
Enter the number of seconds to wait before abruptly closing connections.
[30]> 45
Waiting for listeners to exit...
Receiving suspended for Listener 1.
Waiting for outgoing deliveries to finish...
Mail delivery suspended.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-103
Chapter 3
General Management/Administration/Troubleshooting
mail3.example.com>
suspenddel
Description
Suspend deliveries
Usage
Commit: This command does not require a commit.
Cluster Management: This command is restricted to machine mode.
Batch Command: This command does not support a batch format.
Example
mail.example.com> suspenddel
Enter the number of seconds to wait before abruptly closing connections.
[30]>
Enter one or more domains [comma-separated] to which you want to suspend delivery.
[ALL]> domain1.com, domain2.com, domain3.com
Waiting for outgoing deliveries to finish...
Mail delivery suspended.
suspendlistener
Description
Suspend receiving.
Usage
Commit: This command does not require a commit.
Cluster Management: This command is restricted to machine mode.
Batch Command: This command does not support a batch format.
Example
mail3.example.com> suspendlistener
Choose the listener(s) you wish to suspend.
Separate multiple entries with commas.
1. All
2. InboundMail
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-104
Chapter 3
3. OutboundMail
[1]> 1
Enter the number of seconds to wait before abruptly closing connections.
[30]>
Waiting for listeners to exit...
Receiving suspended.
mail3.example.com>
tcpservices
Description
Display information about files opened by processes.
Usage
Commit: This command does not require a commit.
Cluster Management: This command is restricted to machine mode.
Batch Command: This command does not support a batch format.
Example
mail.cisco.com> tcpservices
System Processes
ftpd.main
ginetd
interface
ipfw
slapd
sntpd
sshd
syslogd
winbindd
-
Feature Processes
euq_webui
- GUI for ISQ
gui
- GUI process
hermes
- MGA mail server
postgres
- Process for storing and querying quarantine data
splunkd
- Processes for storing and querying Email Tracking data
COMMAND
interface
postgres
qabackdoo
ftpd.main
euq_webui
euq_webui
gui
gui
gui
gui
gui
USER
root
pgsql
root
root
root
root
root
root
root
root
root
TYPE
IPv4
IPv4
IPv4
IPv4
IPv4
IPv6
IPv4
IPv4
IPv6
IPv4
IPv4
NODE
TCP
TCP
TCP
TCP
TCP
TCP
TCP
TCP
TCP
TCP
TCP
NAME
127.0.0.1:53
127.0.0.1:5432
*:8123
10.1.1.0:21
10.1.1.0:83
[2001:db8::]:83
172.29.181.70:80
10.1.1.0:80
[2001:db8::]:80
172.29.181.70:443
10.1.1.0:443
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-105
Chapter 3
General Management/Administration/Troubleshooting
gui
ginetd
ginetd
ginetd
ginetd
ginetd
hermes
splunkd
splunkd
api_serve
api_serve
api_serve
api_serve
java
root
root
root
root
root
root
root
root
root
root
root
root
root
root
IPv6
IPv4
IPv4
IPv6
IPv4
IPv6
IPv4
IPv4
IPv4
IPv4
IPv6
IPv4
IPv6
IPv6
TCP
TCP
TCP
TCP
TCP
TCP
TCP
TCP
TCP
TCP
TCP
TCP
TCP
TCP
[2001:db8::]:443
172.29.181.70:22
10.1.1.0:22
[2001:db8::]:22
10.1.1.0:2222
[2001:db8::]:2222
172.29.181.70:25
127.0.0.1:8089
127.0.0.1:9997
10.1.1.0:6080
[2001:db8::]:6080
10.1.1.0:6443
[2001:db8::]:6443
[::127.0.0.1]:9999
techsupport
Description
Allow Cisco TAC to access your system.
Usage
Commit: This command does not require a commit.
Cluster Management: This command is restricted to machine mode.
Batch Command: This command does not support a batch format.
Example
mail3.example.com> techsupport
Service Access currently disabled.
Serial Number: XXXXXXXXXXXX-XXXXXXX
Choose the operation you want to perform:
- SSHACCESS - Allow a Cisco IronPort Customer Support representative to remotely access
your system, without establishing a tunnel.
- TUNNEL - Allow a Cisco IronPort Customer Support representative to remotely access your
system, and establish a secure tunnel for communication.
- STATUS - Display the current techsupport status.
[]> sshaccess
A random seed string is required for this operation
1. Generate a random string to initialize secure communication (recommended)
2. Enter a random string
[1]> 1
Are you sure you want to enable service access? [N]> y
Service access has been ENABLED.
QT22-JQZF-YAQL-TL8L-8@2L-95
to your Cisco IronPort Customer Support representative.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-106
Chapter 3
tlsverify
Description
Establish an outbound TLS connection on demand and debug any TLS connection issues concerning a
destination domain. To create the connection, specify the domain to verify against and the destination
host. AsyncOS checks the TLS connection based on the Required (Verify) TLS setting
Usage
Commit: This command does not require a commit.
Cluster Management: This command is restricted to machine mode.
Batch Command: This command supports a batch format.
Batch Format
The batch format of the tlsverify command can be used to perform all the fuctions of the traditional
CLI command to check the TLS connection to the given hostname.
tlsverify <domain> <hostname>[:<port>]
Example
mail3.example.com> tlsverify
Enter the TLS domain to verify against:
[]> example.com
Enter the destination host to connect to.
connecting on port 25:
[example.com]> mxe.example.com:25
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-107
Chapter 3
General Management/Administration/Troubleshooting
trace
Description
Trace the flow of a message through the system
Usage
Commit: This command does not require a commit.
Cluster Management: This command is restricted to machine mode.
Batch Command: This command does not support a batch format.
Example
mail3.example.com> trace
Enter the source IP
[]> 192.168.1.1
Enter the fully qualified domain name of the source IP
[]> example.com
Select the listener to trace behavior on:
1. InboundMail
2. OutboundMail
[1]> 1
Fetching default SenderBase values...
Enter the SenderBase Org ID of the source IP.
[N/A]>
[Y]> n
Enter or paste the message body here. Enter '.' on a blank line to end.
Subject: Hello
This is a test message.
.
HAT matched on unnamed sender group, host ALL
- Applying $ACCEPTED policy (ACCEPT behavior).
- Maximum Message Size: 100M (Default)
- Maximum Number Of Connections From A Single IP: 1000 (Default)
- Maximum Number Of Messages Per Connection: 1,000 (Default)
- Maximum Number Of Recipients Per Message: 1,000 (Default)
- Maximum Recipients Per Hour: 100 (Default)
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-108
Chapter 3
No Change
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-109
Chapter 3
General Management/Administration/Troubleshooting
Subject: hello
This is a test message.
Run through another debug session? [N]>
Note
When using trace, you must include both the header and the body of the message pasted into the CLI.
trackingconfig
Description
Configure the tracking system.
Usage
Commit: This command requires a commit.
Cluster Management: This command can be used in all three machine modes (cluster, group, machine).
Batch Command: This command does not support a batch format.
Example
mail.example.com> trackingconfig
Message Tracking service status: Message Tracking is enabled.
Choose the operation you want to perform:
- SETUP - Enable Message Tracking for this appliance.
[]> setup
Would you like to use the Message Tracking Service? [Y]>
Do you want to use Centralized Message Tracking for this appliance? [N]>
Would you like to track rejected connections? [N]>
Message Tracking service status: Local Message Tracking is enabled.
Rejected connections are currently not being tracked.
Choose the operation you want to perform:
- SETUP - Enable Message Tracking for this appliance.
[]>
tzupdate
Description
Update timezone rules
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-110
Chapter 3
Usage
Commit: This command does not require a commit.
Cluster Management: This command is restricted to machine mode. It is further restricted to the login
host (i.e., the specific machine you are logged onto).
Batch Command: This command supports a batch format.
Batch Format
The batch format of the tzupdate command forces an update off all time zone rules even if no changes
are detected.
tzupdate [force]
Example
mail.example.com> tzupdate
Requesting update of Timezone Rules
updateconfig
Description
Configure system update parameters.
Usage
Commit: This command requires a commit.
Cluster Management: This command can be used in all three machine modes (cluster, group, machine).
Batch Command: This command does not support a batch format.
Examples
Configure the Appliance to Download Updates from Updater Servers, page 3-111
Configure the Appliance to Verify the Validity of Updater Server Certificate, page 3-114
Update URL:
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-111
Chapter 3
General Management/Administration/Troubleshooting
Update URL:
-----------------------------------------------------------------------------------------Timezone rules
Cisco IronPort Servers
Enrollment Client Updates
Cisco IronPort Servers
Support Request updates
Cisco IronPort Servers
Service (list):
Update URL:
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-112
Chapter 3
[N]>
Do you want to set up an HTTPS proxy server for HTTPS updates for ALL of the following
services:
-
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-113
Chapter 3
General Management/Administration/Troubleshooting
[N]>
Service (images):
Update URL:
Update URL:
-----------------------------------------------------------------------------------------Timezone rules
Cisco IronPort Servers
Enrollment Client Updates Cisco IronPort Servers
Support Request updates
Cisco IronPort Servers
Service (list):
Update URL:
Update URL:
Update URL:
-----------------------------------------------------------------------------------------Timezone rules
Cisco IronPort Servers
Enrollment Client Updates
Cisco IronPort Servers
Support Request updates
Cisco IronPort Servers
Service (list):
Update URL:
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-114
Chapter 3
Update interval: 5m
Proxy server: not enabled
HTTPS Proxy server: not enabled
Choose the operation you want to perform:
- SETUP - Edit update configuration.
- VALIDATE_CERTIFICATES - Validate update server certificates
- TRUSTED_CERTIFICATES - Manage trusted certificates for updates
[]> validate_certificates
Should server certificates from Cisco update servers be validated?
[Yes]>
Service (images):
Update URL:
-----------------------------------------------------------------------------------------Feature Key updates
http://downloads.ironport.com/asyncos
Timezone rules
Cisco IronPort Servers
Enrollment Client Updates
Cisco IronPort Servers
Support Request updates
Cisco IronPort Servers
Cisco IronPort AsyncOS upgrades
Cisco IronPort Servers
Service (list):
Update URL:
-----------------------------------------------------------------------------------------Timezone rules
Cisco IronPort Servers
Enrollment Client Updates
Cisco IronPort Servers
Support Request updates
Cisco IronPort Servers
Service (list):
Update URL:
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-115
Chapter 3
General Management/Administration/Troubleshooting
updatenow
Description
Requests an update to all system service components.
Usage
Commit: This command does not require a commit.
Cluster Management: This command is restricted to machine mode. It is further restricted to the login
host (i.e., the specific machine you are logged onto).
Batch Command: This command does support a batch format.
Batch Format
The batch format of the updatenow command can be used to update all components on the appliance even
if no changes are detected.
updatenow [force]
Example
mail3.example.com> updatenow
Success - All component updates requested
version
Description
View system version information
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-116
Chapter 3
Usage
Commit: This command does not require a commit.
Cluster Management: This command is restricted to machine mode.
Batch Command: This command does not support a batch format.
Example
mail3.example.com> version
Current Version
===============
Product: Cisco C100V Email Security Virtual Appliance
Model: C100V
Version: 9.1.0-019
Build Date: 2015-02-17
Install Date: 2015-02-19 05:17:56
Serial #: 421C73B18CFB05784A83-B03A99E71ED8
BIOS: 6.00
CPUs: 2 expected, 2 allocated
Memory: 6144 MB expected, 6144 MB allocated
RAID: NA
RAID Status: Unknown
RAID Type: NA
BMC: NA
wipedata
Description
Use the wipedata command to wipe the core files on the disk and check the status of the last coredump
operation.
Note
Depending on the size of the data, wipe action may take a while and can affect the system performance
until the action is complete.
Usage
Commit: This command does not require a commit.
Cluster Management: This command is restricted to machine mode.
Batch Command: This command does not support a batch format.
Example
mail.example.com> wipedata
Wiping data may take a while and can affect system performance till it completes.
Choose the operation you want to perform:
- STATUS - Display status of last command run
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-117
Chapter 3
LDAP
upgrade
Description
The upgrade CLI command displays a list of available upgrades and upgrades the AsyncOS system to
the version specified by the user.
Usage
Commit: This command does not require a commit.
Cluster Management: This command is restricted to machine mode.
Batch Command: This command does not support a batch format.
Example
mail3.example.com> upgrade
Upgrades available:
1. AsyncOS (***DON'T TOUCH!***) 4.0.8 upgrade, 2005-05-09 Build 900
2. AsyncOS 4.0.8 upgrade, 2005-08-12 Build 030
.......
45. SenderBase Network Participation Patch
[45]>
Performing an upgrade will require a reboot of the system after the upgrade is applied.
Do you wish to proceed with the upgrade? [Y]> Y
LDAP
This section contains the following CLI commands:
ldapconfig
ldapflush
ldaptest
sievechar
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-118
Chapter 3
ldapconfig
Description
Configure LDAP servers
Usage
Commit: This command requires a commit.
Cluster Management: This command can be used in all three machine modes (cluster, group, machine).
Batch Command: This command does not support a batch format.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-119
Chapter 3
LDAP
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-120
Chapter 3
[]> ldaprouting
Please create a name for this query:
[PublicLDAP.routing]> PublicLDAP.routing
Enter the LDAP query string:
[(mailLocalAddress={a})]> (mailLocalAddress={a})
The query requires one of the attributes below. Please make a selection.
[1] Configure MAILROUTINGADDRESS only - Rewrite the Envelope Recipient (and
leave MAILHOST unconfigured)?
[2] Configure MAILHOST only - Send the messages to an alternate mail host
(and leave MAILROUTINGADDRESS unconfigured)?
[3] Configure both attributes
[]> 1
Enter the attribute which contains the full rfc822 email address for the
recipients.
[mailRoutingAddress]> mailRoutingAddress
Do you want to test this query? [Y]> n
Name: PublicLDAP
Hostname: myldapserver.example.com Port 3268
Server Type: Active Directory
Authentication Type: password
Base: dc=example,dc=com
LDAPACCEPT: PublicLDAP.ldapaccept
LDAPROUTING: PublicLDAP.routing
Choose the operation you want to perform:
- SERVER - Change the server for the query.
- LDAPACCEPT - Configure whether a recipient address should be accepted or
bounced/dropped.
- LDAPROUTING - Configure message routing.
- MASQUERADE - Configure domain masquerading.
- LDAPGROUP - Configure whether a sender or recipient is in a specified group.
- SMTPAUTH - Configure SMTP authentication.
- EXTERNALAUTH - Configure external authentication queries.
- ISQAUTH - Configure Spam Quarantine End-User Authentication Query.
- ISQALIAS - Configure Spam Quarantine Alias Consolidation Query.
[]> masquerade
Please create a name for this query:
[PublicLDAP.masquerade]> PublicLDAP.masquerade
Enter the LDAP query string:
[(mailRoutingAddress={a})]> (mailRoutingAddress={a})
Enter the attribute which contains the externally visible full rfc822 email address.
[]> mailLocalAddress
Do you want the results of the returned attribute to replace the entire friendly portion
of the original recipient? [N]> n
Do you want to test this query? [Y]> n
Name: PublicLDAP
Hostname: myldapserver.example.com Port 3268
Server Type: Active Directory
Authentication Type: password
Base: dc=example,dc=com
LDAPACCEPT: PublicLDAP.ldapaccept
LDAPROUTING: PublicLDAP.routing
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-121
Chapter 3
LDAP
MASQUERADE: PublicLDAP.masquerade
Choose the operation you want to perform:
- SERVER - Change the server for the query.
- LDAPACCEPT - Configure whether a recipient address should be accepted or
bounced/dropped.
- LDAPROUTING - Configure message routing.
- MASQUERADE - Configure domain masquerading.
- LDAPGROUP - Configure whether a sender or recipient is in a specified group.
- SMTPAUTH - Configure SMTP authentication.
- EXTERNALAUTH - Configure external authentication queries.
- ISQAUTH - Configure Spam Quarantine End-User Authentication Query.
- ISQALIAS - Configure Spam Quarantine Alias Consolidation Query.
[]> isqauth
Please create a name for this query:
[PublicLDAP.isqauth]> PublicLDAP.isqauth
Enter the LDAP query string:
[(sAMAccountName={u})]> (sAMAccountName={u})
Enter the list of email attributes.
[]> mail,proxyAddresses
Do you want to activate this query? [Y]> y
Do you want to test this query? [Y]> y
User identity to use in query:
[]> [email protected]
Password to use in query:
[]> password
LDAP query test results:
LDAP Server: myldapserver.example.com
Query: PublicLDAP.isqauth
User: [email protected]
Action: match positive
LDAP query test finished.
Name: PublicLDAP
Hostname: myldapserver.example.com Port 3268
Server Type: Active Directory
Authentication Type: password
Base: dc=example,dc=com
LDAPACCEPT: PublicLDAP.ldapaccept
LDAPROUTING: PublicLDAP.routing
MASQUERADE: PublicLDAP.masquerade
ISQAUTH: PublicLDAP.isqauth [active]
Choose the operation you want to perform:
- SERVER - Change the server for the query.
- LDAPACCEPT - Configure whether a recipient address should be accepted or
bounced/dropped.
- LDAPROUTING - Configure message routing.
- MASQUERADE - Configure domain masquerading.
- LDAPGROUP - Configure whether a sender or recipient is in a specified group.
- SMTPAUTH - Configure SMTP authentication.
- EXTERNALAUTH - Configure external authentication queries.
- ISQAUTH - Configure Spam Quarantine End-User Authentication Query.
- ISQALIAS - Configure Spam Quarantine Alias Consolidation Query.
[]>
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-122
Chapter 3
1. partner.com
2. Demo
Please choose the certificate to apply:
[1]> 1
No LDAP server configurations.
ldapflush
Description
Flush any cached LDAP results.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-123
Chapter 3
LDAP
Usage
Commit: This command does not require a commit.
Cluster Management: This command is restricted to machine mode.
Batch Command: This command does not support a batch format
Example
mail3.example.com> ldapflush
Are you sure you want to flush any cached LDAP results? [N]> y
Flushing cache
mail3.example.com>
ldaptest
Description
Perform a single LDAP query test
Usage
Commit: This command does not require a commit.
Cluster Management: This command is restricted to machine mode.
Batch Command: This command does not support a batch format
Example
In this example, the ldaptest command is used to test the only recipient acceptance query for the
configured LDAP server configuration. The recipient address [email protected] passes the test,
while the recipient address [email protected] fails.
mail3.example.com> ldaptest
Select which LDAP query to test:
1. PublicLDAP.ldapaccep
[1]> 1
Address to use in query:
[]> [email protected]
LDAP query test results:
Query: PublicLDAP.ldapaccept
Argument: [email protected]
Action: pass
LDAP query test finished.
mail3.example.com> ldaptest
Select which LDAP query to test:
1. PublicLDAP.ldapaccep
[1]> 1
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-124
Chapter 3
sievechar
Description
Sets or disables the character used for Sieve Email Filtering, as described in RFC 3598. Note that the
Sieve Character is ONLY recognized in LDAP Accept and LDAP Reroute queries. Other parts of the
system will operate on the complete email address.
Allowable characters are: -_=+/^#
Usage
Commit: This command does not require a commit.
Cluster Management: This command can be used in all three machine modes (cluster, group, machine).
Batch Command: This command does not support a batch format
Example
In this example, the sievechar command is used to define + as the sieve character recognized in Accept
and LDAP Reroute queries.
mail3.example.com> sievechar
Sieve Email Filtering is currently disabled.
Choose the operation you want to perform:
- SETUP - Set the separator character.
[]> setup
Enter the Sieve Filter Character, or a space to disable Sieve Filtering.
[]> +
Sieve Email Filter is enabled, using the '+' character as separator.
This applies only to LDAP Accept and LDAP Reroute Queries.
Choose the operation you want to perform:
- SETUP - Set the separator character.
[]>
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-125
Chapter 3
Mail Delivery Configuration/Monitoring
addresslistconfig
aliasconfig
archivemessage
altsrchost
bounceconfig
bouncerecipients
bvconfig
deleterecipients
deliveryconfig
delivernow
destconfig
hostrate
hoststatus
imageanalysisconfig
oldmessage
rate
redirectrecipients
resetcounters
removemessage
showmessage
showrecipients
status
tophosts
topin
unsubscribe
workqueue
addresslistconfig
Description
Configure address lists.
Usage
Commit: This command requires a commit.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-126
Chapter 3
Cluster Management: This command can be used in all three machine modes (cluster, group, machine).
Batch Command: This command supports a batch format.
Batch Format
The batch format for the addresslistconfig command can be used to create a new address list, edit an
existing address list, print a list of address lists, delete an address list, or find conflicting addresses within
an address list.
Example
mail.example.com> addresslistconfig
No address lists configured.
Choose the operation you want to perform:
- NEW - Create a new address list.
[]> new
Enter a name for the address list:
> add-list1
Enter a description for the address list:
> This is a sample address list.
Do you want to enter only full Email Addresses? [N]> Y
Enter a comma separated list of addresses:
(e.g.: [email protected])
> [email protected], [email protected]
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-127
Chapter 3
aliasconfig
Description
Configure email aliases.
Usage
Commit: This command requires a commit.
Cluster Management: This command can be used in all three machine modes (cluster, group, machine).
Batch Command: This command supports a batch format.
Batch Format
The batch format of the aliasconfig command can be used to add a new alias table, edit an existing table,
print a list of email aliases, and import/export alias table. To invoke as a batch command, use the
following format of the aliasconfig command with the variables listed below:
Note
Using the aliasconfig new command with a non-existant domain causes the domain to be created.
aliasconfig print
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-128
Chapter 3
Example
mail3.example.com> aliasconfig
Enter address(es) for "customercare".
Separate multiple addresses with commas.
[]> [email protected], [email protected], [email protected]
Adding alias customercare: [email protected],[email protected],[email protected]
Do you want to add another alias? [N]> n
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-129
Chapter 3
[]> print
admin: [email protected]
[ example.com ]
customercare: [email protected], [email protected], [email protected]
There are currently 2 mappings defined.
Choose the operation you want to perform:
- NEW - Create a new entry.
- EDIT - Modify an entry.
- DELETE - Remove an entry.
- PRINT - Display the table.
- IMPORT - Import aliases from a file.
- EXPORT - Export table to a file.
- CLEAR - Clear the table.
[]>
Table 3-7
Argument
Description
<domain>
<alias>
<email_address>
The email address that an alias mapps to. A single alias can
map to multiple email addresses.
<filename>
archivemessage
Description
Archive older messages in your queue.
Usage
Commit: This command does not require a commit.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-130
Chapter 3
Example
In the following example, an older message is archived:
mail3.example.com> archivemessage
Enter the MID to archive.
[0]> 47
MID 47 has been saved in file oldmessage_47.mbox in the configuration
altsrchost
Description
Configure Virtual Gateway(tm) mappings.
Usage
Commit: This command requires a commit.
Cluster Management: This command can be used in all three machine modes (cluster, group, machine).
Batch Command: This command does not support a batch format.
Example
In the following example, the altsrchost table is printed to show that there are no existing mappings.
Two entries are then created:
Mail from the groupware server host named @exchange.example.com is mapped to the PublicNet
interface.
Mail from the sender IP address of 192.168.35.35 is mapped to the AnotherPublicNet interface.
Finally, the altsrchost mappings are printed to confirm and the changes are committed.
mail3.example.com> altsrchost
There are currently no mappings configured.
Choose the operation you want to perform:
- NEW - Create a new mapping.
- IMPORT - Load new mappings from a file.
[]> new
Enter the Envelope From address or client IP address for which you want to set up a
Virtual Gateway mapping. Partial addresses such as "@example.com" or "user@" are allowed.
[]> @exchange.example.com
Which interface do you want to send messages for @exchange.example.com from?
1. AnotherPublicNet (192.168.2.2/24: mail4.example.com)
2. Management (192.168.42.42/24: mail3.example.com)
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-131
Chapter 3
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-132
Chapter 3
bounceconfig
Description
Configure the behavior of bounces.
Usage
Commit: This command requires a commit.
Cluster Management: This command can be used in all three machine modes (cluster, group, machine).
Batch Command: This command does not support a batch format.
Example
In the following example, a bounce profile named bounceprofile is created using the bounceconfig
command. In this profile, all hard bounced messages are sent to the alternate address
[email protected]. Delay warnings messages are enabled. One warning message will be
sent per recipient, and the default value of 4 hours (14400 seconds) between warning messages is
accepted
mail3.example.com> bounceconfig
Current bounce profiles:
1. Default
Choose the operation you want to perform:
- NEW - Create a new profile.
- EDIT - Modify a profile.
[]> new
Please create a name for the profile:
[]> bounceprofile
Please enter the maximum number of retries.
[100]> 100
Please enter the maximum number of seconds a message may stay in the queue before being
hard bounced.
[259200]> 259200
Please enter the initial number of seconds to wait before retrying a message.
[60]> 60
Please enter the maximum number of seconds to wait before retrying a message.
[3600]> 3600
Do you want a message sent for each hard bounce? (Yes/No/Default) [Y]> y
Do you want bounce messages to use the DSN message format? (Yes/No/Default) [Y]> y
If a message is undeliverable after some interval, do you want to send a delay warning
message? (Yes/No/Default) [N]> y
Please enter the minimum interval in seconds between delay warning messages.
[14400]> 14400
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-133
Chapter 3
Please enter the maximum number of delay warning messages to send per
recipient.
[1]> 1
Do you want hard bounce and delay warning messages sent to an alternate address, instead
of the sender? [N]> y
Please enter the email address to send hard bounce and delay warning.
[]> [email protected]
Current bounce profiles:
1. Default
2. bounceprofile
Choose the operation you want to perform:
- NEW - Create a new profile.
- EDIT - Modify a profile.
- DELETE - Remove a profile.
[]>
mail3.example.com>
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-134
Chapter 3
Do you want hard bounce messages sent to an alternate address, instead of the sender? [Y]>
Please enter the email address to send hard bounce.
[[email protected]]>
Current bounce profiles:
1. Default
2. bounceprofile
Choose the operation you want to perform:
- NEW - Create a new profile.
- EDIT - Modify a profile.
- DELETE - Remove a profile.
Note
Bounce profiles can be applied based upon the listener that a message was received on. However, this
listener has nothing to do with how the message is ultimately delivered.
In this example, the OutboundMail private listener is edited and the bounce profile named bouncepr1 is
applied to it.
mail3.example.com> listenerconfig
Currently configured listeners:
1. InboundMail (on PublicNet, 192.168.2.1) SMTP Port 25 Public
2. OutboundMail (on PrivateNet, 192.168.1.1) SMTP Port 25 Private
Choose the operation you want to perform:
- NEW - Create a new listener.
- EDIT - Modify a listener.
- DELETE - Remove a listener.
- SETUP - Change global settings.
[]> edit
Enter the name or number of the listener you wish to edit.
[]> 2
Name: OutboundMail
Type: Private
Interface: PrivateNet (192.168.1.1/24) TCP Port 25
Protocol: SMTP
Default Domain:
Max Concurrency: 600 (TCP Queue: 50)
Domain Map: Disabled
TLS: No
SMTP Authentication: Disabled
Bounce Profile: Default
Footer: None
LDAP: Off
Choose the operation you want to perform:
- NAME - Change the name of the listener.
- INTERFACE - Change the interface.
- LIMITS - Change the injection limits.
- SETUP - Configure general options.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-135
Chapter 3
bouncerecipients
Description
Bounce messages from the queue.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-136
Chapter 3
Usage
Commit: This command does not require a commit.
Cluster Management: This command is restricted to machine mode.
Batch Command: This command does not support a batch format
Example
Recipients to be bounced are identified by either the destination recipient host or the message sender
identified by the specific address given in the Envelope From line of the message envelope. Alternately,
all messages in the delivery queue can be bounced at once.
Bounce All
mail3.example.com> bouncerecipients
Please select how you would like to bounce messages:
1. By recipient host.
2. By Envelope From address.
3. All.
[1]>
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-137
Chapter 3
Are you sure you want to bounce all messages in the queue? [N]> Y
Bouncing messages, please wait.
1000 messages bounced.
bvconfig
Description
Configure settings for Bounce Verification. Use this command to configure keys and invalid bounced
emails.
Usage
Commit: This command requires a commit.
Cluster Management: This command can be used in all three machine modes (cluster, group, machine).
Batch Command: This command does not support a batch format.
Example
The following exampe shows key configuration and settings configured for invalid bounced emails.
mail3.example.com> bvconfig
Behavior on invalid bounces: reject
Key for tagging outgoing mail: key
Previously-used keys for verifying incoming mail:
1. key (current outgoing key)
2. goodneighbor (last in use Wed May 31 23:21:01 2006 GMT)
Choose the operation you want to perform:
- KEY - Assign a new key for tagging outgoing mail.
- PURGE - Purge keys no longer needed for verifying incoming mail.
- CLEAR - Clear all keys including current key.
- SETUP - Set how invalid bounces will be handled.
[]> key
Enter the key to tag outgoing mail with (when tagging is enabled in the Good
Neighbor Table)
[]> basic_key
Behavior on invalid bounces: reject
Key for tagging outgoing mail: basic_key
Previously-used keys for verifying incoming mail:
1. basic_key (current outgoing key)
2. key (last in use Wed May 31 23:22:49 2006 GMT)
3. goodneighbor (last in use Wed May 31 23:21:01 2006 GMT)
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-138
Chapter 3
deleterecipients
Description
Delete messages from the queue
Usage
Commit: This command does not require a commit.
Cluster Management: This command is restricted to machine mode.
Batch Command: This command does not support a batch format
Example
The appliance gives you various options to delete recipients depending upon the need. The following
example show deleting recipients by recipient host, deleting by Envelope From Address, and deleting all
recipients in the queue.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-139
Chapter 3
Delete All
mail3.example.com> deleterecipients
Please select how you would like to delete messages:
1. By recipient host.
2. By Envelope From address.
3. All.
[1]> 1
Are you sure you want to delete all messages in the queue? [N]> Y
Deleting messages, please wait.
1000 messages deleted.
deliveryconfig
Description
Configure mail delivery
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-140
Chapter 3
Usage
Commit: This command requires a commit.
Cluster Management: This command can be used in all three machine modes (cluster, group, machine).
Batch Command: This command does not support a batch format.
Example
In the following example, the deliveryconfig command is used to set the default interface to Auto
with Possible Delivery enabled. The system-wide maximum outbound message delivery is set to 9000
connections.
mail3.example.com> deliveryconfig
Choose the operation you want to perform:
- SETUP - Configure mail delivery.
[]> setup
Choose the default interface to deliver mail.
1. Auto
2. AnotherPublicNet (192.168.3.1/24: mail4.example.com)
3. Management (192.168.42.42/24: mail3.example.com)
4. PrivateNet (192.168.1.1/24: mail3.example.com)
5. PublicNet (192.168.2.1/24: mail3.example.com)
[1]> 1
Enable "Possible Delivery" (recommended)?
[Y]> y
Please enter the default system wide maximum outbound message delivery
concurrency
[10000]> 9000
mail3.example.com>
delivernow
Description
Reschedule messages for immediate delivery. Users have the option of selecting a single recipient host,
or all messages currently scheduled for delivery.
Usage
Commit: This command does not require a commit.
Cluster Management: This command is restricted to machine mode.
Batch Command: This command does not support a batch format
Example
mail3.example.com> delivernow
Please choose an option for scheduling immediate delivery.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-141
Chapter 3
1. By recipient domain
2. All messages
[1]> 1
Please enter the recipient domain to schedule for delivery.
[]>foo.com
Scheduling all messages to foo.com for delivery.
destconfig
Formerly the setgoodtable command. The table is now called the Destination Control Table. Use this
table to configure delivery limits for a specified domain.
destconfig Subcommands
Syntax
Description
SETUP
NEW
EDIT
DELETE
DEFAULT
LIST
DETAIL
CLEAR
IMPORT
EXPORT
The destconfig command requires the following information for each row in the Destination Controls
table.
Messages-per-connection limit
Recipient limit
Bounce Verification
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-142
Chapter 3
Domain
Conn. Limit
Rcpt. Limit
Min. Prd.
Enforce MX/DOM
(default)
500
None
Domain
Unlisted domains get their own set of 500 connections with unlimited rcpts/hr
(default)
500
None
MXIP
Mail gateways at unlisted domains get up to 500 connections, with unlimited rcpts/hr
partner.com
10
500
60
Domain
500
None
MXIP
Specifying an IP address
Batch Format
The batch format of the destconfig command can be used to perform all the fuctions of the traditional
CLI command.
destconfig list
destconfig clear
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-143
Chapter 3
For the edit and new batch commands, any or all of the following options may be provided by identifying
the value with the variable name and an equals sign. Options not specified will not be modified (if using
edit) or will be set to default values (if using new).
concurrency_limit=<int> - The maximum concurrency for a specific host.
concurrency_limit_type=<host|MXIP> - Maximum concurrency is per host or
per MX IP.
concurrency_limit_apply=<system|VG> - Apply maximum concurrency is system
wide or by Virtual Gateway(tm).
max_messages_per_connection=<int> - The maximum number of messages that
will be sent per connection.
recipient_limit_minutes=<int> - The time frame to check for recipient
limits in minutes.
recipient_limit=<int> - The number of recipients to limit per unit of
time.
use_tls=<off|on|require|on_verify|require_verify> - Whether TLS should be
on, off, or required for a given host.
bounce_profile=<default|profile> - The bounce profile name to use.
bounce_verification=<off|on> - Bounce Verification option.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-144
Chapter 3
Rate
Limiting
========
On
TLS
=======
Off
Bounce
Verification
============
Off
Bounce
Profile
=========
(Default)
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-145
Chapter 3
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-146
Chapter 3
Domain
==============
newpartner.com
(Default)
Rate
Limiting
========
Default
On
TLS
=======
Req
Off
Bounce
Verification
============
On
Off
Bounce
Profile
=========
Default
(Default)
Enter the domain name to view, or enter DEFAULT to view details for the
default, or enter ALL to view details for all:
[]> all
newpartner.com
Maximum messages per connection: Default
Rate Limiting: Default
TLS: Required
Bounce Verification Tagging: On
Bounce Profile: Default
Default
Rate Limiting:
500 concurrent connections
No recipient limit
Limits applied to entire domain, across all virtual gateways
TLS: Off
Bounce Verification Tagging: Off
There are currently 2 entries configured.
[]>
mail3.example.com> commit
Please enter some comments describing your changes:
[]> enabled TLS for delivery to newpartner.com using demo certificate
Do you want to save the current configuration for rollback? [Y]> n
Changes committed: Fri May 23 11:42:12 2014 GMT
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-147
Chapter 3
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-148
Chapter 3
hostrate
Description
Monitor activity for a particular host
Usage
Commit: This command does not require a commit.
Cluster Management: This command is restricted to machine mode.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-149
Chapter 3
Example
mail3.example.com> hostrate
Recipient host:
[]> aol.com
Enter the number of seconds between displays.
[10]> 1
Time
23:38:23
23:38:24
23:38:25
^C
Host
Status
up
up
up
CrtCncOut
1
1
1
ActvRcp ActvRcp
Delta
0
0
0
0
0
0
hoststatus
Description
Get the status of the given hostname.
Usage
Commit: This command does not require a commit.
Cluster Management: This command is restricted to machine mode.
Batch Command: This command does not support a batch format
Example
mail3.example.com> hoststatus
Recipient host:
[]> aol.com
Host mail status for: 'aol.com'
Status as of:
Fri Aug 8 11:12:00 2003
Host up/down:
up
Counters:
Queue
Soft Bounced Events
Completion
Completed Recipients
Hard Bounced Recipients
DNS Hard Bounces
5XX Hard Bounces
Filter Hard Bounces
Expired Hard Bounces
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-150
0
1
1
0
1
0
0
Chapter 3
0
0
0
Gauges:
Queue
Active Recipients
Unattempted Recipients
Attempted Recipients
Connections
Current Outbound Connections
Pending Outbound Connections
0
0
0
0
0
Oldest Message
No Messages
Last Activity
Fri Aug 8 11:04:24 2003
Ordered IP addresses: (expiring at Fri Aug 8 11:34:24 2003)
Preference
IPs
15
64.12.137.121
64.12.138.89
64.12.138.120
15
64.12.137.89
64.12.138.152
152.163.224.122
15
64.12.137.184
64.12.137.89
64.12.136.57
15
64.12.138.57
64.12.136.153
205.188.156.122
15
64.12.138.57
64.12.137.152
64.12.136.89
15
64.12.138.89
205.188.156.154 64.12.138.152
15
64.12.136.121
152.163.224.26
64.12.137.184
15
64.12.138.120
64.12.137.152
64.12.137.121
MX Records:
Preference
TTL
Hostname
15
52m24s
mailin-01.mx.aol.com
15
52m24s
mailin-02.mx.aol.com
15
52m24s
mailin-03.mx.aol.com
15
52m24s
mailin-04.mx.aol.com
Last 5XX Error:
---------550 REQUESTED ACTION NOT TAKEN: DNS FAILURE
(at Fri Aug 8 11:04:25 2003)
---------Virtual gateway information:
============================================================
example.com (PublicNet_017):
Host up/down:up
Last ActivityWed Nov 13 13:47:02 2003
Recipients0
============================================================
example.com (PublicNet_023):
Host up/down:up
Last ActivityWed Nov 13 13:45:01 2003
Recipients
imageanalysisconfig
Description
Configure the IronPort Image Analysis settings
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-151
Chapter 3
Usage
Commit: This command requires a commit.
Cluster Management: This command can be used in all three machine modes (cluster, group, machine).
Batch Command: This command does not support a batch format
Example
mail.example.com>imageanalysisconfig
IronPort Image Analysis: Enabled
Image Analysis Sensitivity: 65
Verdict Ranges: Clean (0-49), Suspect(50-74), Inappropriate (75+)
Skip small images with size less than 100 pixels (width or height)
(First time users see the license agreement displayed here.)
Choose the operation you want to perform:
- SETUP - Configure IronPort Image Analysis.
[]> setup
IronPort Image Analysis: Enabled
Would you like to use IronPort Image Analysis? [Y]>
Define the image analysis sensitivity. Enter a value between 0 (least sensitive) and 100
(most sensitive). As sensitivity increases, so does the false
positive rate. The default setting of 65 is recommended.
[65]>
Define the range for a CLEAN verdict. Enter the upper bound of the CLEAN range by entering
a value between 0 and 98. The default setting of 49 is
recommended.
[49]>
Define the range for a SUSPECT verdict. Enter the upper bound of the SUSPECT range by
entering a value between 50 and 99. The default setting of 74 is
recommended.
[74]>
Would you like to skip scanning of images smaller than a specific size? [Y]>
Please enter minimum image size to scan in pixels, representing either height or width of
a given image.
[100]>
IronPort Image Analysis: Enabled
Image Analysis Sensitivity: 65
Verdict Ranges: Clean (0-49), Suspect(50-74), Inappropriate (75+)
Skip small images with size less than 100 pixels (width or height)
Choose the operation you want to perform:
- SETUP - Configure IronPort Image Analysis.
[]>
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-152
Chapter 3
oldmessage
Description
Displays the mid and headers of the oldest non-quarantine message on the system.
Usage
Commit: This command does not require a commit.
Cluster Management: This command is restricted to machine mode..
Batch Command: This command does not support a batch format.
Example
In the following example, an older messages are displayed:
mail3.example.com> oldmessage
MID 9: 1 hour 5 mins 35 secs old
Received: from test02.com ([172.19.0.109])
by test02.com with SMTP; 14 Feb 2007 22:11:37 -0800
From: [email protected]
To: [email protected]
Subject: Testing
Message-Id: <[email protected]
rate
Description
Monitor message throughput
Usage
Commit: This command does not require a commit.
Cluster Management: This command is restricted to machine mode.
Batch Command: This command does not support a batch format.
Example
mail3.example.com> rate
Enter the number of seconds between displays.
[10]> 1
Hit Ctrl-C to return to the main prompt.
Time
Connections Recipients
In
Out
Received
Delta
Recipients
Completed
Delta
Queue
K-Used
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-153
Chapter 3
23:37:13
23:37:14
23:37:15
23:37:16
23:37:17
23:37:18
23:37:19
23:37:21
^C
10
8
9
7
5
9
7
11
2
2
2
3
3
3
3
3
41708833
41708841
41708848
41708852
41708858
41708871
41708881
41708893
0
8
7
4
6
13
10
12
40842686
40842692
40842700
40842705
40842711
40842722
40842734
40842744
0
6
8
5
6
11
12
10
64
105
76
64
64
67
64
79
redirectrecipients
Description
Redirect all messages to another relay host.
Warning
Redirecting messages to a receiving domain that has /dev/null as its destination results in the loss of
messages. The CLI does not display a warning if you redirect mail to such a domain. Check the SMTP
route for the receiving domain before redirecting messages.
Warning
Redirecting recipients to a host or IP address that is not prepared to accept large volumes of SMTP
mail from this host will cause messages to bounce and possibly result in the loss of mail.
Usage
Commit: This command does not require a commit.
Cluster Management: This command is restricted to machine mode.
Batch Command: This command supports a batch format.
Batch Format
The batch format of the redirectrecipients command can be used to perform all the fuctions of the
traditional CLI command.
Example
The following example redirects all mail to the example2.com host.
mail3.example.com> redirectrecipients
Please enter the hostname or IP address of the machine you want to send all mail to.
[]> example2.com
WARNING: redirecting recipients to a host or IP address that is not prepared to accept
large volumes of SMTP mail from this host will cause messages to bounce and possibly
result in the loss of mail.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-154
Chapter 3
Are you sure you want to redirect all mail in the queue to "example2.com"? [N]> y
Redirecting messages, please wait.
246 recipients redirected.
resetcounters
Description
Reset all of the counters in the system
Usage
Commit: This command does not require a commit.
Cluster Management: This command is restricted to machine mode.
Batch Command: This command does not support a batch format.
Example
mail3.example.com> resetcounters
Counters reset: Mon Jan 01 12:00:01 2003
removemessage
Description
Attempts to safely remove a message for a given message ID.
The removemessage command can only remove messages that are in the work queue, retry queue, or a
destination queue. Note that depending on the state of the system, valid and active messages may not be
in any of those queues.
Usage
Commit: This command does not require a commit.
Cluster Management: This command is restricted to machine mode.
Batch Command: This command does not support a batch format.
Example
example.com> removemessage
Enter the MID to remove.
[]> 1
MID 1: 19 secs old
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-155
Chapter 3
showmessage
Description
Shows the message and message body for a specified message ID.
Usage
Commit: This command does not require a commit.
Cluster Management: This command is restricted to machine mode.
Batch Command: This command does not support a batch format.
Example
example.com> showmessage
MID 9: 1 hour 5 mins 35 secs old
Received: from example2.com([172.19.0.109])
by test02.com with SMTP; 14 Feb 2007 22:11:37 -0800
From: [email protected]
To: [email protected]
Subject: Testing
Message-Id: <[email protected]>
This is the message body.
showrecipients
Description
Show messages from the queue by recipient host, Envelope From address, or all messages.
Usage
Commit: This command does not require a commit.
Cluster Management: This command is restricted to machine mode.
Batch Command: This command does support a batch format.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-156
Chapter 3
Batch Format
The batch format of the showrecipients command can be used to perform all the fuctions of the
traditional CLI command.
Example
The following example shows messages in the queue for all recipient hosts.
mail3.example.com> showrecipients
Please select how you would like to show messages:
1. By recipient host.
2. By Envelope From address.
3. All.
[1]> 3
Showing messages, please wait.
MID/
[RID]
1527
[0]
Bytes/
[Atmps]
1230
[0]
Sender/
Subject
Recipient
[email protected] Testing
[email protected]
1522
[0]
1230
[0]
[email protected] Testing
[email protected]
1529
[0]
1230
[0]
[email protected] Testing
[email protected]
1530
[0]
1230
[0]
[email protected] Testing
[email protected]
1532
[0]
1230
[0]
[email protected] Testing
[email protected]
1531
[0]
1230
[0]
[email protected] Testing
[email protected]
1518
[0]
1230
[0]
[email protected] Testing
[email protected]
1535
1230
[email protected] Testing
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-157
Chapter 3
[0]
[0]
1533
[0]
1230
[0]
[email protected] Testing
[email protected]
1536
[0]
1230
[0]
[email protected] Testing
[email protected]
status
The status command is used to display the system status of your appliance. Using the detail option
(status detail) displays additional information.
Usage
Commit: This command does not require a commit.
Cluster Management: This command can be used in all three machine modes (cluster, group, machine).
Batch Command: This command does not support a batch format.
Example
mail.example.com> status detail
Status as of:
Up since:
Reset
Uptime
Lifetime
2
2
2
2
2
2
0
0
0
0
0
0
Gauges:
Connections
Current Inbound Conn.
Current Outbound Conn.
Queue
Active Recipients
Messages In Work Queue
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-158
2
0
13
Current
0
0
2
0
Chapter 3
Kilobytes Used
Kilobytes Free
Quarantine
Messages In Quarantine
Policy, Virus and Outbreak
Kilobytes In Quarantine
Policy, Virus and Outbreak
184
8,388,424
0
0
tophosts
Description
To get immediate information about the email queue and determine if a particular recipient host has
delivery problems such as a queue buildup use the tophosts command. The tophosts command
returns a list of the top 20 recipient hosts in the queue. The list can be sorted by a number of different
statistics, including active recipients, connections out, delivered recipients, soft bounced events, and
hard bounced recipients.
Usage
Commit: This command does not require a commit.
Cluster Management: This command is restricted to machine mode.
Batch Command: This command does not support a batch format.
Example
mail3.example.com> tophosts
Sort results by:
1. Active Recipients
2. Connections Out
3. Delivered Recipients
4. Hard Bounced Recipients
5. Soft Bounced Events
[1]> 1
Status as of:
Fri Mar 13 06:09:18 2015 GMT
Hosts marked with '*' were down as of the last delivery attempt.
Recipient Host
1*
2
3
4
example.com
the.encryption.queue
the.euq.queue
the.euq.release.queue
Active
Recip.
Conn.
Out
Deliv.
Recip.
Soft
Bounced
Hard
Bounced
2
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-159
Chapter 3
topin
Description
Display the top hosts by number of incoming connections
Usage
Commit: This command does not require a commit.
Cluster Management: This command is restricted to machine mode.
Batch Command: This command does not support a batch format.
Example
mail3.example.com> topin
Status as of:
#
Remote hostname
Remote IP addr.
listener
1mail.remotedomain01.com
172.16.0.2
Incoming01
2
mail.remotedomain01.com
172.16.0.2
Incoming02
3
mail.remotedomain03.com
172.16.0.4
Incoming01
4
mail.remotedomain04.com
172.16.0.5
Incoming02
5
mail.remotedomain05.com
172.16.0.6
Incoming01
6
7
8
9
10
mail.remotedomain06.com
mail.remotedomain07.com
mail.remotedomain08.com
mail.remotedomain09.com
mail.remotedomain10.com
172.16.0.7
172.16.0.8
172.16.0.9
172.16.0.10
172.16.0.11
Incoming02
Incoming01
Incoming01
Incoming01
Incoming01
3
3
3
3
2
11
12
13
14
15
mail.remotedomain11.com
mail.remotedomain12.com
mail.remotedomain13.com
mail.remotedomain14.com
mail.remotedomain15.com
172.16.0.12
172.16.0.13
172.16.0.14
172.16.0.15
172.16.0.16
Incoming01
Incoming02
Incoming01
Incoming01
Incoming01
2
2
2
2
2
16
17
18
19
20
mail.remotedomain16.com
mail.remotedomain17.com
mail.remotedomain18.com
mail.remotedomain19.com
mail.remotedomain20.com
172.16.0.17
172.16.0.18
172.16.0.19
172.16.0.20
172.16.0.21
Incoming01
Incoming01
Incoming02
Incoming01
Incoming01
2
1
1
1
1
unsubscribe
Description
Update the global unsubscribe list
Usage
Commit: This command requires a commit.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-160
Conn. In
10
10
5
4
3
Chapter 3
Cluster Management: This command can be used in all three machine modes (cluster, group, machine).
Batch Command: This command does not support a batch format.
Example
In this example, the address [email protected] is added to the Global Unsubscribe list, and the feature
is configured to hard bounce messages. Messages sent to this address will be bounced; the appliance will
bounce the message immediately prior to delivery.
mail3.example.com> unsubscribe
Global Unsubscribe is enabled. Action: drop.
Choose the operation you want to perform:
- NEW - Create a new entry.
- IMPORT - Import entries from a file.
- SETUP - Configure general settings.
[]> new
Enter the unsubscribe key to add. Partial addresses such as "@example.com"
or "user@" are allowed, as are IP addresses. Partial hostnames such as "@.example.com" are
allowed.
[]> [email protected]
Email Address '[email protected]' added.
Global Unsubscribe is enabled. Action: drop.
Choose the operation you want to perform:
- NEW - Create a new entry.
- DELETE - Remove an entry.
- PRINT - Display all entries.
- IMPORT - Import entries from a file.
- EXPORT - Export all entries to a file.
- SETUP - Configure general settings.
- CLEAR - Remove all entries.
[]> setup
Do you want to enable the Global Unsubscribe feature? [Y]> y
Would you like matching messages to be dropped or bounced?
1. Drop
2. Bounce
[1]> 2
Global Unsubscribe is enabled. Action: bounce.
Choose the operation you want to perform:
- NEW - Create a new entry.
- DELETE - Remove an entry.
- PRINT - Display all entries.
- IMPORT - Import entries from a file.
- EXPORT - Export all entries to a file.
- SETUP - Configure general settings.
- CLEAR - Remove all entries.
[]>
mail3.example.com> commit
Please enter some comments describing your changes:
[]> Added username [email protected] to global unsubscribe
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-161
Chapter 3
workqueue
Description
Display and/or alter work queue pause status
Usage
Commit: This command does not require a commit.
Cluster Management: This command is restricted to machine mode.
Batch Command: This command does not support a batch format.
Example
mail3.example.com> workqueue
Status:
Operational
Messages: 1243
Manually pause work queue?
[N]> y
Note
Entering a reason is optional. If you do not enter a reason, the system logs the reason as operator
paused.
In this example, the work queue is resumed:
mail3.example.com> workqueue
Status:
Paused by admin: checking LDAP server
Messages: 1243
Resume the work queue?
[Y]> y
Status:
Operational
Messages: 1243
etherconfig
interfaceconfig
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-162
Chapter 3
netstat
nslookup
packetcapture
ping
ping6
routeconfig
setgateway
sethostname
smtproutes
sslconfig
sslv3config
telnet
traceroute
traceroute6
etherconfig
Description
Configure Ethernet settings, including media settings, NIC pairing, VLAN configuration, and DSR
configuration.
Usage
Commit: This command requires a commit.
Cluster Management: This command is restricted to machine mode.
Batch Command: This command does not support a batch format.
Example
mail3.example.com> etherconfig
Choose the operation you want to perform:
- MEDIA - View and edit ethernet media settings.
- VLAN - View and configure VLANs.
- LOOPBACK - View and configure Loopback.
- MTU - View and configure MTU.
[]> vlan
VLAN interfaces:
Choose the operation you want to perform:
- NEW - Create a new VLAN.
[]> new
VLAN tag ID for the interface (Ex: "34"):
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-163
Chapter 3
[]> 12
Enter the name or number of the ethernet interface you wish bind to:
1. Data 1
2. Data 2
3. Management
[1]> 1
VLAN interfaces:
1. VLAN
12 (Data 1)
Choose the operation you want to perform:
- NEW - Create a new VLAN.
- EDIT - Edit a VLAN.
- DELETE - Delete a VLAN.
[]>
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-164
Chapter 3
Ethernet interfaces:
1. Data 1 default mtu 1500
2. Data 2 mtu 1200
3. Management default mtu 1500
4. VLAN
12 default mtu 1500
Choose the operation you want to perform:
- EDIT - Edit an ethernet interface.
[]>
interfaceconfig
Description
Configure the interface. You can create, edit, or delete interfaces. You can enable FTP, change an IP
address, and configure Ethernet IP addresses.
Usage
Commit: This command requires a commit.
Cluster Management: This command is restricted to machine mode.
Batch Command: This command supports a batch format.
Batch Format
The batch format of the interfaceconfig command can be used to perform all the fuctions of the
traditional CLI command.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-165
Chapter 3
[--euq_https][=<port>]
[--ccs[=<port>]].
FTP is available only on IPv4.
Deleting an interface
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-166
Chapter 3
nslookup
Description
Use the nslookup command to check the DNS functionality.
The nslookup command can confirm that the appliance is able to reach and resolve hostnames and IP
addresses from a working DNS (domain name service) server.
Table 3-10
Query Type
Description
CNAME
MX
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-167
Chapter 3
Table 3-10
Query Type
Description
NS
PTR
SOA
TXT
Usage
Commit: This command does not require a commit.
Cluster Management: This command can be used in all three machine modes (cluster, group, machine).
Batch Command: This command does not support a batch format
Example
mail.example.com> nslookup
Please enter the host or IP address to resolve.
[]> vm30esa0086.ibqa
Choose the
1. A
2. AAAA
3. CNAME
4. MX
5. NS
6. PTR
query type:
the host's IP address
the host's IPv6 address
the canonical name for an alias
the mail exchanger
the name server for the named zone
the hostname if the query is an Internet address,
netstat
Description
Use the netstat command to displays network connections (both incoming and outgoing), routing
tables, and a number of network interface statistics. Note that this version will not support all arguments.
Specifically, you cannot use -a, -A, -g, -m, -M, -N, -s. The command was designed to be run in interactive
mode, so that you may enter netstat, then choose from five options to report on. You can also specify the
interface to listen on and the interval for display.
Usage
Commit: This command does not require a commit.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-168
Chapter 3
Example
example.com> netstat
Choose the information you want to display:
1. List of active sockets.
2. State of network interfaces.
3. Contents of routing tables.
4. Size of the listen queues.
5. Packet traffic information.
[1]> 2
Select the ethernet interface whose state you wish to display:
1. Data 1
2. Data 2
3. Management
4. ALL
[]> 1
Show the number of bytes in and out? [N]>
Show the number of dropped packets? [N]> y
Name
Mtu Network
Address
Ipkts Ierrs
Opkts
Oerrs Coll Drop
Data 1 1500 197.19.1/24
example.com
30536
5
example.com>
packetcapture
Description
Use the netstat command to displays network connections (both incoming and outgoing), routing
tables, and a number of network interface statistics. Note that this version will not support all arguments.
Specifically, you cannot use -a, -A, -g, -m, -M, -N, -s. The command was designed to be run in interactive
mode, so that you may enter netstat, then choose from five options to report on. You can also specify the
interface to listen on and the interval for display.
Usage
Commit: This command does not require a commit.
Cluster Management: This command can be used in all three machine modes (cluster, group, machine).
Batch Command: This command does not support a batch format
Example
mail.example.com> packetcapture
Capture Information:
Status:
No capture running
Current Settings:
Maximum File Size:
Limit:
200 MB
None (Run Indefinitely)
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-169
Chapter 3
Interface(s):
Filter:
ALL
(tcp port 25)
C100V-421C73B18CFB05784A83-B03A99E71ED8-20150312-105256.cap
0 of 200M
0s
None (Run Indefinitely)
ALL
(tcp port 25)
C100V-421C73B18CFB05784A83-B03A99E71ED8-20150312-105256.cap
24 of 200M
10s
None (Run Indefinitely)
ALL
(tcp port 25)
200 MB
None (Run Indefinitely)
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-170
Chapter 3
Interface(s):
Filter:
ALL
(tcp port 25)
ping
Description
The ping command allows you to test connectivity to a network host from the appliance.
Usage
Commit: This command does not require a commit.
Cluster Management: This command is restricted to machine mode. It is further restricted to the login
host (i.e., the specific machine you are logged onto). This command requires access to the local file
system.
Batch Command: This command does not support a batch format.
Example
mail3.example.com> ping
Which interface do you want to send the pings from?
1. Auto
2. Management (192.168.42.42/24: mail3.example.com)
3. PrivateNet (192.168.1.1/24: mail3.example.com)
4. PublicNet (192.168.2.1/24: mail3.example.com)
[1]> 1
Please enter the host you wish to ping.
[]> anotherhost.example.com
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-171
Chapter 3
Note
ping6
Description
Ping a network host using IPv6
Usage
Commit: This command does not require a commit.
Cluster Management: This command is restricted to machine mode. It is further restricted to the login
host (i.e., the specific machine you are logged onto). This command requires access to the local file
system.
Batch Command: This command does not support a batch format.
Example
mail.example.com> ping6
Which interface do you want to send the pings from?
1. Auto
2. Management (192.168.42.42/24: mail3.example.com)
[1]> 1
Please enter the host you wish to ping.
[]> anotherhost.example.com
Note
routeconfig
Description
The routeconfig command allows you to create, edit, and delete static routes for TCP/IP traffic. By
default, traffic is routed through the default gateway set with the setgateway command. However,
AsyncOS allows specific routing based on destination.
Routes consist of a nickname (for future reference), a destination, and a gateway. A gateway (the next
hop) is an IP address such as 10.1.1.2. The destination can be one of two things:
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-172
Chapter 3
a subnet using CIDR notation. For example, 192.168.5.0/24 means the entire class C network from
192.168.5.0 to 192.168.5.255.
2620:101:2004:4202::0-2620:101:2004:4202::ff
2620:101:2004:4202::
2620:101:2004:4202::23
2620:101:2004:4202::/64
The command presents a list of all currently configured TCP/IP routes for you to select from using the
edit and delete subcommands.
Usage
Commit: This command requires a commit.
Cluster Management: This command is restricted to machine mode.
Batch Command: This command supports a batch format.
Batch Format
The batch format of the smtproutes command can be used to perform all the fuctions of the traditional
CLI command. You can choose whether to use IPv4 or IPv6 addresses for the route.
Table 3-11
routeconfig Arguments
Argument
Description
4|6
name
destination_address
gateway_ip
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-173
Chapter 3
Example
mail3.example.com> routeconfig
Configure routes for:
1. IPv4
2. IPv6
[1]>
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-174
Chapter 3
setgateway
Description
The setgateway command configures the default next-hop intermediary through which packets should
be routed. Alternate (non-default) gateways are configured using the routeconfig command.
Usage
Commit: This command requires a commit.
Cluster Management: This command can be used in all three machine modes (cluster, group, machine).
Batch Command: This command does not support a batch format.
Example
mail3.example.com> setgateway
Warning: setting an incorrect default gateway may cause the current connection to be
interrupted when the changes are committed.
Enter new default gateway:
[10.1.1.1]> 192.168.20.1
mail3.example.com> commit
Please enter some comments describing your changes:
[]> changed default gateway to 192.168.20.1
Do you want to save the current configuration for rollback? [Y]> n
Changes committed: Fri May 23 11:42:12 2014 GMT
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-175
Chapter 3
sethostname
Description
The hostname is used to identify the system at the CLI prompt. You must enter a fully-qualified
hostname. The sethostname command sets the name of the Email Security appliance. The new hostname
does not take effect until you issue the commit command.
Usage
Commit: This command requires a commit.
Cluster Management: This command can be used in all three machine modes (cluster, group, machine).
Batch Command: This command does not support a batch format.
Example
oldname.example.com> sethostname
[oldname.example.com]> mail3.example.com
oldname.example.com>
For the hostname change to take effect, you must enter the commit command. After you have successfully
committed the hostname change, the new name appears in the CLI prompt:
oldname.example.com> commit
Please enter some comments describing your changes:
[]> Changed System Hostname
Do you want to save the current configuration for rollback? [Y]> n
Changes committed: Fri May 23 11:42:12 2014 GMT
smtproutes
Description
Set up permanent domain redirections.
Usage
Commit: This command requires a commit.
Cluster Management: This command can be used in all three machine modes (cluster, group, machine).
Batch Command: This command supports a batch format.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-176
Chapter 3
Batch Format
The batch format of the smtproutes command can be used to perform all the fuctions of the traditional
CLI command.
Example
In the following example, the smptroutes command is used to construct a route (mapping) for the
domain example.com to relay1.example.com, relay2.example.com, and backup-relay.example.com.
Use /pri=# to specify a destination priority. THE # should be from 0-65535, with larger numbers
indicating decreasing priority. If unspecified, the priority defaults to 0.
(Note that you may have constructed the same mapping during the systemsetup command when you
configured the InboundMail public listener.)
mail3.example.com> smtproutes
There are no routes configured.
Choose the operation you want to perform:
- NEW - Create a new route.
- IMPORT - Import new routes from a file.
[]> new
Enter the domain for which you want to set up a permanent route.
Partial hostnames such as ".example.com" are allowed.
Use "ALL" for the default route.
[]> example.com
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-177
Chapter 3
Enter the destination hosts, separated by commas, which you want mail
for example.com to be delivered.
Enter USEDNS by itself to use normal DNS resolution for this route.
Enter /dev/null by itself if you wish to discard the mail.
Enclose in square brackets to force resolution via address (A)
records, ignoring any MX records.
[]> relay1.example.com/pri=10, relay2.example.com, backup-relay.example.com
Mapping for example.com to relay1.example.com, relay2.example.com,
backup-relay.example.com/pri=10 created.
There are currently 1 routes configured.
Choose the operation you want to perform:
- NEW - Create a new route.
- EDIT - Edit destinations of an existing route.
- DELETE - Remove a route.
- PRINT - Display all routes.
- IMPORT - Import new routes from a file.
- EXPORT - Export all routes to a file.
- CLEAR - Remove all routes.
[]>
sslconfig
Description
Configure SSL settings for the appliance.
Usage
Commit: This command requires a commit.
Cluster Management:This command can be used in all three machine modes (cluster, group, machine).
Batch Command: This command does not support a batch format.
Example
mail.example.com> sslconfig
sslconfig settings:
GUI HTTPS method: sslv3tlsv1
GUI HTTPS ciphers:
RC4-SHA
RC4-MD5
ALL
Inbound SMTP method: sslv3tlsv1
Inbound SMTP ciphers:
RC4-SHA
RC4-MD5
ALL
Outbound SMTP method: sslv3tlsv1
Outbound SMTP ciphers:
RC4-SHA
RC4-MD5
ALL
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-178
Chapter 3
v3
TLS v1
and TLS v1
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-179
Chapter 3
RC4-SHA
RC4-MD5
ALL
Outbound SMTP method: sslv3tlsv1
Outbound SMTP ciphers:
RC4-SHA
RC4-MD5
ALL
Choose the operation you want to perform:
- GUI - Edit GUI HTTPS ssl settings.
- INBOUND - Edit Inbound SMTP ssl settings.
- OUTBOUND - Edit Outbound SMTP ssl settings.
- VERIFY - Verify and show ssl cipher list.
[]>
sslv3config
Description
Enable or disable SSLv3 settings for the appliance.
Usage
Commit: This command requires a commit.
Cluster Management:This command can be used in all three machine modes (cluster, group, machine).
Batch Command: This command does not support a batch format.
Example
The following example shows how to disable SSLv3 for End User Quarantine.
mail.example.com> sslv3config
Current SSLv3 Settings:
-------------------------------------------------UPDATER
:
Enabled
WEBSECURITY
:
Enabled
EUQ
:
Enabled
LDAP
:
Enabled
-------------------------------------------------Choose the operation you want to perform:
- SETUP - Toggle SSLv3 settings.
[]> setup
Choose the service to toggle SSLv3 settings:
1. EUQ Service
2. LDAP Service
3. Updater Service
4. Web Security Service
[1]>
Do you want to enable SSLv3 for EUQ Service ? [Y]>n
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-180
Chapter 3
telnet
Description
Connect to a remote host
Usage
Commit: This command does not require a commit.
Cluster Management: This command is restricted to machine mode. It is further restricted to the login
host (i.e., the specific machine you are logged onto). This command requires access to the local file
system.
Batch Command: This command does not support a batch format.
Example
mail3.example.com> telnet
Please select which interface you want to telnet from.
1. Auto
2. Management (192.168.42.42/24: mail3.example.com)
3. PrivateNet (192.168.1.1/24: mail3.example.com)
4. PublicNet (192.168.2.1/24: mail3.example.com)
[1]> 3
Enter the remote hostname or IP.
[]> 193.168.1.1
Enter the remote port.
[25]> 25
Trying 193.168.1.1...
Connected to 193.168.1.1.
Escape character is '^]'.
traceroute
Description
Use the traceroute command to test connectivity to a network host using IPV4 from the appliance and
debug routing issues with network hops.
Usage
Commit: This command does not require a commit.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-181
Chapter 3
Cluster Management: This command is restricted to machine mode. It is further restricted to the login
host (i.e., the specific machine you are logged onto). This command requires access to the local file
system.
Batch Command: This command does not support a batch format.
Example
mail3.example.com> traceroute
Which interface do you want to trace from?
1. Auto
2. Management (192.168.42.42/24: mail3.example.com)
3. PrivateNet (192.168.1.1/24: mail3.example.com)
4. PublicNet (192.168.2.1/24: mail3.example.com)
[1]> 1
Please enter the host to which you want to trace the route.
[]> 10.1.1.1
Press Ctrl-C to stop.
traceroute to 10.1.1.1 (10.1.1.1), 64 hops max, 44 byte packets
1 gateway (192.168.0.1) 0.202 ms 0.173 ms 0.161 ms
2 hostname (10.1.1.1) 0.298 ms 0.302 ms 0.291 ms
mail3.example.com>
traceroute6
Description
Use the traceroute6 command to test connectivity to a network host using IPV6 from the appliance
and debug routing issues with network hops.
Usage
Commit: This command does not require a commit.
Cluster Management: This command is restricted to machine mode. It is further restricted to the login
host (i.e., the specific machine you are logged onto). This command requires access to the local file
system.
Batch Command: This command does not support a batch format.
Example
mail.example.com> traceroute6
Which interface do you want to trace from?
1. Auto
2. D1 (2001:db8::/32: example.com)
[1]> 1
Please enter the host to which you want to trace the route.
[]> example.com
Press Ctrl-C to stop.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-182
Chapter 3
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-183
Chapter 3
Outbreak Filters
Outbreak Filters
This section contains the following CLI commands:
outbreakconfig
outbreakflush
outbreakstatus
outbreakupdate
outbreakconfig
Description
Use the outbreakconfig command to configure the Outbreak Filter feature. You perform the following
actions using this command:
Set a maximum size for files to scan (note that you are entering the size in bytes)
Usage
Commit: This command requires a commit.
Cluster Management: This command can be used in all three machine modes (cluster, group, machine).
Batch Command: This command does not support a batch format.
Example
mail.example.com> outbreakconfig
Outbreak Filters: Enabled
Choose the operation you want to perform:
- SETUP - Change Outbreak Filters settings.
[]> setup
Outbreak Filters: Enabled
Would you like to use Outbreak Filters? [Y]>
Outbreak Filters enabled.
Outbreak Filter alerts are sent when outbreak rules cross the threshold (go above or back
down below), meaning that new messages of
certain types could be quarantined or will no longer be quarantined, respectively.
Would you like to receive Outbreak Filter alerts? [N]>
What is the largest size message Outbreak Filters should scan?
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-184
Chapter 3
[524288]>
Do you want to use adaptive rules to compute the threat level of messages? [Y]>
Logging of URLs is currently disabled.
Do you wish to enable logging of URL's? [N]> Y
Logging of URLs has been enabled.
The Outbreak Filters feature is now globally enabled on the system. You must use the
'policyconfig' command in the CLI or the Email
Security Manager in the GUI to enable Outbreak Filters for the desired Incoming and
Outgoing Mail Policies.
Choose the operation you want to perform:
- SETUP - Change Outbreak Filters settings.
[]>
outbreakflush
Description
Clear the cached Outbreak Rules.
Usage
Commit: This command does not require a commit.
Cluster Management: This command is restricted to machine mode.
Batch Command: This command does not support a batch format.
Example
mail3.example.com> outbreakflush
Warning - This command removes the current set of Outbreak Filter Rules, leaving your
network exposed until the next rule download. Run "outbreakupdate force" command to
immediately download Outbreak Filter Rules.
Are you sure that you want to clear the current rules? [N]> y
Cleared the current rules.
mail3.example.com>
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-185
Chapter 3
Outbreak Filters
outbreakstatus
Description
The outbreakstatus command shows the current Outbreak Filters feature settings, including whether
the Outbreak Filters feature is enabled, any Outbreak Rules, and the current threshold.
Usage
Commit: This command does not require a commit.
Cluster Management: This command is restricted to machine mode.
Batch Command: This command does not support a batch format.
Example
mail3.example.com> outbreakstatus
Outbreak Filters: Enabled
Component
CASE Core Files
CASE Utilities
Outbreak Rules
Last Update
26 Jan 2014 06:45 (GMT +00:00)
26 Jan 2014 06:45 (GMT +00:00)
26 Jan 2014 07:00 (GMT +00:00)
Version
3.3.1-005
3.3.1-005
20140126_063240
Threat Outbreak
Outbreak
Level Rule Name
Rule Description
--------------------------------------------------------------------5
OUTBREAK_0002187_03 A reported a MyDoom.BB outbreak.
5
OUTBREAK_0005678_00 This configuration file was generated by...
3
OUTBREAK_0000578_00 This virus is distributed in pictures of...
Outbreak Filter Rules with higher threat levels pose greater risks.
(5 = highest threat, 1 = lowest threat)
Last update: Mon Jan 27 04:36:27 2014
mail3.example.com>
outbreakupdate
Description
Requests an immediate update of CASE rules and engine core.
Usage
Commit: This command does not require a commit.
Cluster Management: This command is restricted to machine mode. It is further restricted to the login
host (i.e., the specific machine you are logged onto).
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-186
Chapter 3
Example
elroy.run> outbreakupdate
Requesting updates for Outbreak Filter Rules.
Policy Enforcement
This section contains the following CLI commands:
dictionaryconfig
exceptionconfig
filters
policyconfig
quarantineconfig
scanconfig
stripheaders
textconfig
dictionaryconfig
Description
Configure content dictionaries
Usage
Commit: This command requires a commit.
Cluster Management: This command can be used in all three machine modes (cluster, group, machine).
Batch Command: This command does not support a batch format.
Example
Use dictionaryconfig -> new to create dictionaries, and dictionaryconfig -> delete to remove
dictionaries.
Creating a Dictionary
example.com> dictionaryconfig
No content dictionaries have been defined.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-187
Chapter 3
Policy Enforcement
Creating a Dictionary 2
In this example, a new dictionary named secret_words is created to contain the term codename. Once
the dictionary has been entered, the edit -> settings subcommand is used to define the case-sensitivity
and word boundary detection for words in the dictionary.
mail3.example.com> dictionaryconfig
No content dictionaries have been defined.
Choose the operation you want to perform:
- NEW - Create a new content dictionary.
[]> new
Enter a name for this content dictionary.
[]> secret_words
Do you wish to specify a file for import? [N]>
Enter new words or regular expressions, enter a blank line to finish.
codename
Currently configured content dictionaries:
1. secret_words
Choose the operation you want to perform:
- NEW - Create a new content dictionary.
- EDIT - Modify a content dictionary.
- DELETE - Remove a content dictionary.
- RENAME - Change the name of a content dictionary.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-188
Chapter 3
[]> edit
Enter the number of the dictionary you want to edit:
1. secret_words
[]> 1
Choose the operation you want to perform on dictionary 'secret_words':
- NEW - Create new entries in this dictionary.
- IMPORT - Replace all of the words in this dictionary.
- EXPORT - Export the words in this dictionary.
- DELETE - Remove an entry in this dictionary.
- PRINT - List the entries in this dictionary.
- SETTINGS - Change settings for this dictionary.
[]> settings
Do you want to ignore case when matching using this dictionary? [Y]>
Do you want strings in this dictionary to only match complete words? [Y]>
Enter the default encoding to be used for exporting this dictionary:
1. US-ASCII
2. Unicode (UTF-8)
3. Unicode (UTF-16)
4. Western European/Latin-1 (ISO 8859-1)
5. Western European/Latin-1 (Windows CP1252)
6. Traditional Chinese (Big 5)
7. Simplified Chinese (GB 2312)
8. Simplified Chinese (HZ GB 2312)
9. Korean (ISO 2022-KR)
10. Korean (KS-C-5601/EUC-KR)
11. Japanese (Shift-JIS (X0123))
12. Japanese (ISO-2022-JP)
13. Japanese (EUC)
[2]>
Choose the operation you want to perform on dictionary 'secret_words':
- NEW - Create new entries in this dictionary.
- IMPORT - Replace all of the words in this dictionary.
- EXPORT - Export the words in this dictionary.
- DELETE - Remove an entry in this dictionary.
- PRINT - List the entries in this dictionary.
- SETTINGS - Change settings for this dictionary.
[]>
Currently configured content dictionaries:
1. secret_words
Choose the operation you want to perform:
- NEW - Create a new content dictionary.
- EDIT - Modify a content dictionary.
- DELETE - Remove a content dictionary.
- RENAME - Change the name of a content dictionary.
[]>
mail3.example.com> commit
Please enter some comments describing your changes:
[]> Added new dictionary: secret_words
Do you want to save the current configuration for rollback? [Y]> n
Changes committed: Fri May 23 11:42:12 2014 GMT
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-189
Chapter 3
Policy Enforcement
Importing Dictionaries
In the example below, using the dictionaryconfig command, 84 terms in the profanity.txt text file
are imported as Unicode (UTF-8) into a dictionary named profanity.
mail3.example.com> dictionaryconfig
No content dictionaries have been defined.
Choose the operation you want to perform:
- NEW - Create a new content dictionary.
[]> new
Enter a name for this content dictionary.
[]> profanity
Do you wish to specify a file for import?
[N]> y
Exporting Dictionaries
In the example below, using the dictionaryconfig command, the secret_words dictionary is exported
to a text file named secret_words_export.txt
mail3.example.com> dictionaryconfig
Currently configured content dictionaries:
1. secret_words
Choose the operation you want to perform:
- NEW - Create a new content dictionary.
- EDIT - Modify a content dictionary.
- DELETE - Remove a content dictionary.
- RENAME - Change the name of a content dictionary.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-190
Chapter 3
[]> edit
Enter the number of the dictionary you want to edit:
1. secret_words
[]> 1
Choose the operation you want to perform on dictionary 'secret_words':
- NEW - Create new entries in this dictionary.
- IMPORT - Replace all of the words in this dictionary.
- EXPORT - Export the words in this dictionary.
- DELETE - Remove an entry in this dictionary.
- PRINT - List the entries in this dictionary.
- SETTINGS - Change settings for this dictionary.
[]> export
Enter a name for the exported file:
[]> secret_words_export.txt
mail3.example.com> dictionaryconfig
Currently configured content dictionaries:
1. secret_words
Choose the operation you want to perform:
- NEW - Create a new content dictionary.
- EDIT - Modify a content dictionary.
- DELETE - Remove a content dictionary.
- RENAME - Change the name of a content dictionary.
[]> edit
Enter the number of the dictionary you want to edit:
1. secret_words
[]> 1
Choose the operation you want to perform on dictionary 'secret_words':
- NEW - Create new entries in this dictionary.
- IMPORT - Replace all of the words in this dictionary.
- EXPORT - Export the words in this dictionary.
- DELETE - Remove an entry in this dictionary.
- PRINT - List the entries in this dictionary.
- SETTINGS - Change settings for this dictionary.
[]> export
Enter a name for the exported file:
[]> secret_words_export.txt
exceptionconfig
Description
Use the exceptionconfig command in the CLI to create the domain exception table. In this example,
the email address [email protected] is added to the domain exception table with a policy of
Allow.
Usage
Commit: This command requires a commit.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-191
Chapter 3
Policy Enforcement
Cluster Management: This command can be used in all three machine modes (cluster, group,
machine)..
Batch Command: This command does not support a batch format.
Example
mail3.example.com> exceptionconfig
Choose the operation you want to perform:
- NEW - Create a new domain exception table entry
[]> new
Enter a domain, sub-domain, user, or email address for which you wish to
provide an exception:
[]> mail.partner.com
Any of the following passes:
- @[IP address]
Matches any email address with this IP address.
- @domain
Matches any email address with this domain.
- @.partial.domain
Matches any email address domain ending in this domain.
- user@
Matches any email address beginning with user@.
- user@domain
Matches entire email address.
Enter a domain, sub-domain, user, or email address for which you wish to
provide an exception:
[]> [email protected]
Choose a policy for this domain exception:
1. Allow
2. Reject
[1]> 1
Choose the operation you want to perform:
- NEW - Create a new domain exception table entry
- EDIT - Edit a domain exception table entry
- DELETE - Delete a domain exception table entry
- PRINT - Print all domain exception table entries
- SEARCH - Search domain exception table
- CLEAR - Clear all domain exception entries
[]>
filters
Description
Configure message processing options.
Usage
Commit: This command requires a commit.
Cluster Management: This command is restricted to machine mode.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-192
Chapter 3
Example
In this example, the filter command is used to create three new filters:
The first filter is named big_messages. It uses the body-size rule to drop messages larger than 10
megabytes.
The second filter is named no_mp3s. It uses the attachment-filename rule to drop messages that
contain attachments with the filename extension of .mp3.
The third filter is named mailfrompm. It uses mail-from rule examines all mail from
[email protected] and blind-carbon copies [email protected].
Using the filter -> list subcommand, the filters are listed to confirm that they are active and valid,
and then the first and last filters are switched in position using the move subcommand. Finally, the
changes are committed so that the filters take effect.
mail3.example.com> filters
Choose the operation you want to perform:
- NEW - Create a new filter.
- IMPORT - Import a filter script from a file.
[]> new
Enter filter script. Enter '.' on its own line to end.
big_messages:
if (body-size >= 10M) {
drop();
}
.
1 filters added.
Choose the operation you want to perform:
- NEW - Create a new filter.
- DELETE - Remove a filter.
- IMPORT - Import a filter script from a file.
- EXPORT - Export filters to a file
- MOVE - Move a filter to a different position.
- SET - Set a filter attribute.
- LIST - List the filters.
- DETAIL - Get detailed information on the filters.
- LOGCONFIG - Configure log subscriptions used by filters.
- ROLLOVERNOW - Roll over a filter log file.
[]> new
Enter filter script. Enter '.' on its own line to end.
no_mp3s:
if (attachment-filename == '\\.mp3$') {
drop();
}
.
1 filters added.
Choose the operation you want to perform:
- NEW - Create a new filter.
- DELETE - Remove a filter.
- IMPORT - Import a filter script from a file.
- EXPORT - Export filters to a file
- MOVE - Move a filter to a different position.
- SET - Set a filter attribute.
- LIST - List the filters.
- DETAIL - Get detailed information on the filters.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-193
Chapter 3
Policy Enforcement
policyconfig
Description
Configure per recipient or sender based policies.
Usage
Commit: This command requires a commit.
Cluster Management: This command can be used in all three machine modes (cluster, group, machine).
Batch Command: This command does not support a batch format.
Examples
Creating an Incoming Mail Policy to Drop Spam Messages and Archive Suspected Spam Messages,
page 3-195
Create an Incoming Policy to Drop the Messages Identified as Bulk Email or Social Network Email,
page 3-215
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-194
Chapter 3
Creating an Incoming Mail Policy to Drop Spam Messages and Archive Suspected Spam Messages
In this example, the policyconfig -> edit -> antispam subcommand is used to edit the Anti-Spam
settings for the default incoming mail policy. (Note that this same configuration is available in the GUI
from the Email Security Manager feature.)
First, messages positively identified as spam are chosen not to be archived; they will be dropped.
Messages that are suspected to be spam are chosen to be archived. They will also be sent to the Spam
Quarantine installed on the server named quarantine.example.com. The text [quarantined:
possible spam] is prepended to the subject line and a special header of X-quarantined: true is
configured to be added to these suspect messages. In this scenario, Administrators and end-users can
check the quarantine for false positives, and an administrator can adjust, if necessary, the suspected
spam threshold.
DEFAULT
Ironport
Mcafee
Advanced
Malware
Protection:
----------
Graymail:
----------
Content
Filter:
----------
Outbreak
Filters:
-----------
N/A
Off
Off
Enabled
1. DEFAULT
Anti-Spam:
----------
Graymail:
Anti-Virus: Advanced
------------------- Malware
Protection:
----------
Content
Filter:
----------
Outbreak
Filters:
-----------
Ironport
Mcafee
Off
Enabled
N/A
N/A
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-195
Chapter 3
Policy Enforcement
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-196
Chapter 3
Anti-Spam:
----------
Anti-Virus:
----------
Advanced
Malware
Protection:
----------
Graymail:
----------
Content
Filter:
----------
Outbreak
Filters:
-----------
DEFAULT
Ironport
Mcafee
N/A
N/A
Off
Enabled
Anti-Spam:
----------
Anti-Virus:
----------
Advanced
Malware
Protection:
----------
Graymail:
----------
Content
Filter:
----------
Outbreak
Filters:
-----------
DEFAULT
Ironport
Mcafee
N/A
N/A
Off
Enabled
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-197
Chapter 3
Policy Enforcement
[]> ldap(sales)
Please select an LDAP group query:
1. PublicLDAP.ldapgroup
[1]> 1
Is this entry a recipient or a sender?
1. Recipient
2. Sender
[1]> 1
Add another member? [Y]> n
Would you like to enable Anti-Spam support? [Y]> y
Use the policy table default? [Y]> n
Begin Anti-Spam configuration
Some messages will be positively identified as spam. Some messages will be
identified as suspected spam. You can set the IronPort Anti-Spam Suspected Spam Threshold
below.
The following configuration options apply to messages POSITIVELY identified as spam:
What score would you like to set for the IronPort Anti-Spam spam threshold?
[90]> 90
1. DELIVER
2. DROP
3. BOUNCE
4. IRONPORT QUARANTINE
What do you want to do with messages identified as spam?
[1]> 2
Do you want to archive messages identified as spam? [N]> n
Do you want to enable special treatment of suspected spam? [Y]> y
What score would you like to set for the IronPort Anti-Spam suspect spam
threshold?
[50]> 50
The following configuration options apply to messages identified as SUSPECTED
spam:
1. DELIVER
2. DROP
3. BOUNCE
4. IRONPORT QUARANTINE
What do you want to do with messages identified as SUSPECTED spam?
[1]> 4
Do you want to archive messages identified as SUSPECTED spam? [N]> n
1. PREPEND
2. APPEND
3. NONE
Do you want to add text to the subject of messages identified as SUSPECTED
spam?
[1]> 3
Do you want to add a custom header to messages identified as SUSPECTED spam? [N]> n
Anti-Spam configuration complete
Would you like to enable Anti-Virus support? [Y]> y
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-198
Chapter 3
Advanced
Malware
Protection:
----------
Graymail:
----------
Content
Filter:
----------
Outbreak
Filters:
-----------
sales_team
IronPort
Default
Default
Default
Default
Default
DEFAULT
Ironport
Mcafee
N/A
Off
Off
Enabled
Then, create the policy for the engineering team (three individual email recipients), specifying that .dwg
files are exempt from Outbreak Filter scanning.
Advanced
Malware
Protection:
----------
Graymail:
----------
Content
Filter:
----------
Outbreak
Filters:
-----------
sales_team
IronPort
Default
Default
Default
Default
Default
DEFAULT
Ironport
Mcafee
N/A
Off
Off
Enabled
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-199
Chapter 3
Policy Enforcement
[]> [email protected]
Is this entry a recipient or a sender?
1. Recipient
2. Sender
[1]> 1
Add another member? [Y]> y
Enter a member for this policy:
[]> [email protected]
Is this entry a recipient or a sender?
1. Recipient
2. Sender
[1]> 1
Add another member? [Y]> y
Enter a member for this policy:
[]> [email protected]
Is this entry a recipient or a sender?
1. Recipient
2. Sender
[1]> 1
Add another member? [Y]> n
Would you like to enable Anti-Spam support? [Y]> y
Use the policy table default? [Y]> y
Would you like to enable Anti-Virus support? [Y]> y
Use the policy table default? [Y]> y
Would you like to enable Outbreak Filters for this policy? [Y]> y
Use the policy table default? [Y]> n
Would you like to modify the list of file extensions that bypass
Outbreak Filters? [N]> y
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-200
Chapter 3
Advanced
Malware
Protection:
----------
Graymail:
----------
Content
Filter:
----------
Outbreak
Filters:
-----------
sales_team
IronPort
Default
Default
Default
Default
Default
engineering
Default
Default
Default
Default
Default
Enabled
DEFAULT
Ironport
Mcafee
N/A
Off
Off
Enabled
Next, create three new content filters to be used in the Incoming Mail Overview policy table.
In the CLI, the filters subcommand of the policyconfig command is the equivalent of the Incoming
Content Filters GUI page. When you create content filters in the CLI, you must use the save
subcommand to save the filter and return to the policyconfig command.
First, create the scan_for_confidential content filter:
Advanced
Malware
Protection:
----------
Graymail:
----------
Content
Filter:
----------
Outbreak
Filters:
-----------
sales_team
IronPort
Default
Default
Default
Default
Default
engineering
Default
Default
Default
Default
Default
Enabled
DEFAULT
Ironport
Mcafee
N/A
Off
Off
Enabled
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-201
Chapter 3
Policy Enforcement
[]> filters
No filters defined.
Choose the operation you want to perform:
- NEW - Create a new filter
[]> new
Enter a name for this filter:
[]> scan_for_confidential
Enter a description or comment for this filter (optional):
[]> scan all incoming mail for the string 'confidential'
Filter Name:
scan_for_confidential
Conditions:
Always Run
Actions:
No actions defined yet.
Description:
scan all incoming mail for the string 'confidential'
Choose the operation you want to perform:
- RENAME - Rename this filter
- DESC - Edit filter description
- ADD - Add condition or action
[]> add
1. Condition
2. Action
[1]> 1
1. Message Body Contains
2. Only Body Contains (Attachments are not scanned)
3. Message Body Size
4. Subject Header
5. Other Header
6. Attachment Contains
7. Attachment File Type
8. Attachment Name
9. Attachment MIME Type
10. Attachment Protected
11. Attachment Unprotected
12. Attachment Corrupt
13. Envelope Recipient Address
14. Envelope Recipient in LDAP Group
15. Envelope Sender Address
16. Envelope Sender in LDAP Group
17. Reputation Score
18. Remote IP
19. DKIM authentication result
20. SPF verification result
[1]> 1
Enter regular expression or smart identifier to search message contents for:
[]> confidential
Threshold required for match:
[1]> 1
Filter Name:
scan_for_confidential
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-202
Chapter 3
Conditions:
body-contains("confidential", 1)
Actions:
No actions defined yet.
Description:
scan all incoming mail for the string 'confidential'
Choose the operation you want to perform:
- RENAME - Rename this filter
- DESC - Edit filter description
- ADD - Add condition or action
- DELETE - Delete condition or action
[]> add
1. Condition
2. Action
[1]> 2
1. Bcc
2. Notify
3. Redirect To Alternate Email Address
4. Redirect To Alternate Host
5. Insert A Custom Header
6. Insert A Message Tag
7. Strip A Header
8. Send From Specific IP Interface
9. Drop Attachments By Content
10. Drop Attachments By Name
11. Drop Attachments By MIME Type
12. Drop Attachments By File Type
13. Drop Attachments By Size
14. Send To System Quarantine
15. Duplicate And Send To System Quarantine
16. Add Log Entry
17. Drop (Final Action)
18. Bounce (Final Action)
19. Skip Remaining Content Filters (Final Action)
20. Encrypt (Final Action)
21. Encrypt on Delivery
22. Skip Outbreak Filters check
[1]> 1
Enter the email address(es) to send the Bcc message to:
[]> [email protected]
Do you want to edit the subject line used on the Bcc message? [N]> y
Enter the subject to use:
[$Subject]> [message matched confidential filter]
Do you want to edit the return path of the Bcc message? [N]> n
Filter Name:
scan_for_confidential
Conditions:
body-contains("confidential", 1)
Actions:
bcc ("[email protected]", "[message matched confidential filter]")
Description:
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-203
Chapter 3
Policy Enforcement
scan_for_confidential
Conditions:
body-contains("confidential", 1)
Actions:
bcc ("[email protected]", "[message matched confidential filter]")
quarantine ("Policy")
Description:
scan all incoming mail for the string 'confidential'
Choose the operation you want to perform:
- RENAME - Rename this filter
- DESC - Edit filter description
- ADD - Add condition or action
- DELETE - Delete condition or action
- MOVE - Reorder the conditions or actions
- SAVE - Save filter
[]> save
Defined filters:
1. scan_for_confidential: scan all incoming mail for the string 'confidential'
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-204
Chapter 3
no_mp3s
Conditions:
Always Run
Actions:
No actions defined yet.
Description:
strip all MP3 attachments
Choose the operation you want to perform:
- RENAME - Rename this filter
- DESC - Edit filter description
- ADD - Add condition or action
[]> add
1. Condition
2. Action
[1]> 2
1. Bcc
2. Notify
3. Redirect To Alternate Email Address
4. Redirect To Alternate Host
5. Insert A Custom Header
6. Insert A Message Tag
7. Strip A Header
8. Send From Specific IP Interface
9. Drop Attachments By Content
10. Drop Attachments By Name
11. Drop Attachments By MIME Type
12. Drop Attachments By File Type
13. Drop Attachments By Size
14. Send To System Quarantine
15. Duplicate And Send To System Quarantine
16. Add Log Entry
17. Drop (Final Action)
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-205
Chapter 3
Policy Enforcement
no_mp3s
Conditions:
Always Run
Actions:
drop-attachments-by-filetype("mp3")
Description:
strip all MP3 attachments
Choose the operation you want to perform:
- RENAME - Rename this filter
- DESC - Edit filter description
- ADD - Add condition or action
- SAVE - Save filter
[]> save
Defined filters:
1. scan_for_confidential: scan all incoming mail for the string 'confidential'
2. no_mp3s: strip all MP3 attachments
Choose the operation you want to perform:
- NEW - Create a new filter
- EDIT - Edit an existing filter
- DELETE - Delete a filter
- PRINT - Print all filters
- MOVE - Reorder a filter
- RENAME - Rename a filter
[]> new
Enter a name for this filter:
[]> ex_employee
Enter a description or comment for this filter (optional):
[]> bounce messages intended for Doug
Filter Name:
ex_employee
Conditions:
Always Run
Actions:
No actions defined yet.
Description:
bounce messages intended for Doug
Choose the operation you want to perform:
- RENAME - Rename this filter
- DESC - Edit filter description
- ADD - Add condition or action
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-206
Chapter 3
[]> add
1. Condition
2. Action
[1]> 1
1. Message Body Contains
2. Only Body Contains (Attachments are not scanned)
3. Message Body Size
4. Subject Header
5. Other Header
6. Attachment Contains
7. Attachment File Type
8. Attachment Name
9. Attachment MIME Type
10. Attachment Protected
11. Attachment Unprotected
12. Attachment Corrupt
13. Envelope Recipient Address
14. Envelope Recipient in LDAP Group
15. Envelope Sender Address
16. Envelope Sender in LDAP Group
17. Reputation Score
18. Remote IP
19. DKIM authentication result
20. SPF verification result
[1]> 13
Enter regular expression to search Recipient address for:
[]> doug
Filter Name:
ex_employee
Conditions:
rcpt-to == "doug"
Actions:
No actions defined yet.
Description:
bounce messages intended for Doug
Choose the operation you want to perform:
- RENAME - Rename this filter
- DESC - Edit filter description
- ADD - Add condition or action
- DELETE - Delete condition or action
[]> add
1. Condition
2. Action
[1]> 2
1. Bcc
2. Notify
3. Redirect To Alternate Email Address
4. Redirect To Alternate Host
5. Insert A Custom Header
6. Insert A Message Tag
7. Strip A Header
8. Send From Specific IP Interface
9. Drop Attachments By Content
10. Drop Attachments By Name
11. Drop Attachments By MIME Type
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-207
Chapter 3
Policy Enforcement
ex_employee
Conditions:
rcpt-to == "doug"
Actions:
notify-copy ("[email protected]", "message bounced for ex-employee of
example.com")
Description:
bounce messages intended for Doug
Choose the operation you want to perform:
- RENAME - Rename this filter
- DESC - Edit filter description
- ADD - Add condition or action
- DELETE - Delete condition or action
- SAVE - Save filter
[]> add
1. Condition
2. Action
[1]> 2
1. Bcc
2. Notify
3. Redirect To Alternate Email Address
4. Redirect To Alternate Host
5. Insert A Custom Header
6. Insert A Message Tag
7. Strip A Header
8. Send From Specific IP Interface
9. Drop Attachments By Content
10. Drop Attachments By Name
11. Drop Attachments By MIME Type
12. Drop Attachments By File Type
13. Drop Attachments By Size
14. Send To System Quarantine
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-208
Chapter 3
ex_employee
Conditions:
rcpt-to == "doug"
Actions:
notify-copy ("[email protected]", "message bounced for ex-employee of
example.com")
bounce()
Description:
bounce messages intended for Doug
Choose the operation you want to perform:
- RENAME - Rename this filter
- DESC - Edit filter description
- ADD - Add condition or action
- DELETE - Delete condition or action
- SAVE - Save filter
[]> save
Defined filters:
1. scan_for_confidential: scan all incoming mail for the string 'confidential'
2. no_mp3s: strip all MP3 attachments
3. ex_employee: bounce messages intended for Doug
Choose the operation you want to perform:
- NEW - Create a new filter
- EDIT - Edit an existing filter
- DELETE - Delete a filter
- PRINT - Print all filters
- MOVE - Reorder a filter
- RENAME - Rename a filter
[]>
Incoming Mail Policy Configuration
Name:
Anti-Spam:
Anti-Virus:
-----------------------
Advanced
Malware
Protection:
----------
Graymail:
----------
Content
Filter:
----------
Outbreak
Filters:
-----------
sales_team
IronPort
Default
Default
Default
Default
Default
engineering
Default
Default
Default
Default
Default
Enabled
DEFAULT
Ironport
Mcafee
N/A
Off
Off
Enabled
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-209
Chapter 3
Policy Enforcement
Advanced
Malware
Protection:
----------
Graymail:
----------
Content
Filter:
----------
Outbreak
Filters:
-----------
sales_team
IronPort
Default
Default
Default
Default
Default
engineering
Default
Default
Default
Default
Default
Enabled
DEFAULT
Ironport
Mcafee
N/A
Off
Off
Enabled
Graymail:
Anti-Virus: Advanced
------------------- Malware
Protection:
----------
Content
Filter:
----------
Outbreak
Filters:
-----------
IronPort
Default
Default
Default
Default
Default
2. engineering Default
Default
Default
Default
Default
Enabled
3. DEFAULT
Mcafee
N/A
Off
Off
Enabled
Name:
-----
1. sales_team
Ironport
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-210
Chapter 3
scan_for_confidential
no_mp3s
ex_employee
filter to toggle on/off, or press enter to finish:
1. Active
2.
3.
Enter the
[]> 2
scan_for_confidential
no_mp3s
ex_employee
filter to toggle on/off, or press enter to finish:
1. Active
2. Active
3.
Enter the
[]> 3
scan_for_confidential
no_mp3s
ex_employee
filter to toggle on/off, or press enter to finish:
1. Active
2. Active
3. Active
Enter the
[]>
scan_for_confidential
no_mp3s
ex_employee
filter to toggle on/off, or press enter to finish:
Policy Summaries:
Anti-Spam: IronPort - Drop
Suspect-Spam: IronPort - Quarantine - Archiving copies of the original message.
Anti-Virus: McAfee - Scan and Clean
Graymail Detection: Unsubscribe - Disabled
Content Filters: Enabled. Filters: scan_for_confidential, no_mp3s, ex_employee
Outbreak Filters: Enabled. No bypass extensions.
Choose the operation you want to perform:
- ANTISPAM - Modify Anti-Spam policy
- ANTIVIRUS - Modify Anti-Virus policy
- GRAYMAIL - Modify Graymail policy
- OUTBREAK - Modify Outbreak Filters policy
- FILTERS - Modify filters
[]>
Incoming Mail Policy Configuration
Name:
Anti-Spam:
Anti-Virus:
-----------------------
Advanced
Malware
Protection:
----------
Graymail:
----------
Content
Filter:
----------
Outbreak
Filters:
-----------
sales_team
IronPort
Default
Default
Default
Default
Default
engineering
Default
Default
Default
Default
Default
Enabled
DEFAULT
Ironport
Mcafee
N/A
Off
Enabled
Enabled
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-211
Chapter 3
Policy Enforcement
Graymail:
Anti-Virus: Advanced
------------------- Malware
Protection:
----------
Content
Filter:
----------
Outbreak
Filters:
-----------
IronPort
Default
Default
Default
Default
Default
2. engineering Default
Default
Default
Default
Default
Enabled
3. DEFAULT
Mcafee
N/A
Off
Off
Enabled
Name:
-----
1. sales_team
Ironport
scan_for_confidential
no_mp3s
ex_employee
filter to toggle on/off, or press enter to finish:
1. Active
2.
3.
Enter the
[]> 3
scan_for_confidential
no_mp3s
ex_employee
filter to toggle on/off, or press enter to finish:
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-212
Chapter 3
1. Active
2.
3. Active
Enter the
[]>
scan_for_confidential
no_mp3s
ex_employee
filter to toggle on/off, or press enter to finish:
Policy Summaries:
Anti-Spam: Default
Anti-Virus: Default
Graymail Detection: Unsubscribe - Default
Content Filters: Enabled. Filters: scan_for_confidential, ex_employee
Outbreak Filters: Enabled. Bypass extensions: dwg
Choose the operation you want to perform:
- NAME - Change name of policy
- NEW - Add a new member
- DELETE - Remove a member
- PRINT - Print policy members
- ANTISPAM - Modify Anti-Spam policy
- ANTIVIRUS - Modify Anti-Virus policy
- GRAYMAIL - Modify Graymail policy
- OUTBREAK - Modify Outbreak Filters policy
- FILTERS - Modify filters
[]>
Incoming Mail Policy Configuration
Name:
Anti-Spam:
Anti-Virus:
-----------------------
Advanced
Malware
Protection:
----------
Graymail:
----------
Content
Filter:
----------
Outbreak
Filters:
-----------
sales_team
IronPort
Default
Default
Default
Default
Default
engineering
Default
Default
Default
Default
Enabled
Enabled
DEFAULT
Ironport
Mcafee
N/A
Off
Enabled
Enabled
Note
The CLI does not contain the notion of adding a new content filter within an individual policy. Rather,
the filters subcommand forces you to manage all content filters from within one subsection of the
policyconfig command. For that reason, adding the drop_large_attachments has been omitted from
this example.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-213
Chapter 3
Policy Enforcement
N/A
N/A
N/A
Graymail:
----------
Outbreak
Content
Filters:
Filter:
---------- -----------
DLP:
----
Off
Off
Off
Off
1. DEFAULT N/A
N/A
N/A
Outbreak
Graymail:
Content
Filters:
---------- Filter:
---------- -----------
DLP:
----
Off
Off
California AB-1298
Suspicious Transmission - Zip Files
Restricted Files
policy to toggle on/off, or press enter to finish:
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-214
Off
Off
Chapter 3
California AB-1298
Suspicious Transmission - Zip Files
Restricted Files
policy to toggle on/off, or press enter to finish:
1. Active
2. Active
3. Active
Enter the
[]>
California AB-1298
Suspicious Transmission - Zip Files
Restricted Files
policy to toggle on/off, or press enter to finish:
Policy Summaries:
Anti-Spam: Off
Anti-Virus: Off
Graymail Detection: Unsubscribe - Disabled
Content Filters: Off (No content filters have been created)
Outbreak Filters: Off
DLP: Enabled. Policies: California AB-1298, Suspicious Transmission - Zip
Files, Restricted Files
Choose the operation you want to perform:
- ANTISPAM - Modify Anti-Spam policy
- ANTIVIRUS - Modify Anti-Virus policy
- GRAYMAIL - Modify Graymail policy
- OUTBREAK - Modify Outbreak Filters policy
- DLP - Modify DLP policy
[]>
Create an Incoming Policy to Drop the Messages Identified as Bulk Email or Social Network Email
mail.example.com> policyconfig
Would you like to configure Incoming or Outgoing Mail Policies?
1. Incoming
2. Outgoing
[1]> 1
DEFAULT
Off
N/A
Advanced
Malware
Protection:
----------
Graymail:
----------
Content
Filter:
----------
Outbreak
Filters:
-----------
N/A
Off
Off
N/A
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-215
Chapter 3
Policy Enforcement
1.
Name:
-----
Anti-Spam:
----------
Anti-Virus:
----------
Advanced
Malware
Protection:
----------
Graymail:
----------
Content
Filter:
----------
Outbreak
Filters:
-----------
DEFAULT
Off
N/A
N/A
Off
Off
N/A
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-216
Chapter 3
quarantineconfig
Description
Configure system quarantines.
Usage
Commit: This command requires a commit.
Cluster Management: This command is restricted to machine mode.
Batch Command: This command does not support a batch format.
Example
mail3.example.com> quarantineconfig
Currently configured quarantines:
#
1
2
3
Quarantine Name
Outbreak
Policy
Virus
Size (MB)
3,072
1,024
2,048
% full
0.0
0.1
empty
Messages
1
497
0
Retention
12h
10d
30d
Policy
Release
Delete
Delete
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-217
Chapter 3
Policy Enforcement
Policy
Release
Release
Delete
Delete
Note
You will only be prompted to give users access to the quarantine if guest or operator users have already
been created on the system.
A quarantine's user list only contains users belonging to the Operators or Guests groups. Users in the
Administrators group always have full access to the quarantine. When managing the user list, the NEW
command is suppressed if all the Operator/Guest users are already on the quarantine's user list. Similarly,
DELETE is suppressed if there are no users to delete.
scanconfig
Description
Configure attachment scanning policy
Usage
Commit: This command requires a commit.
Cluster Management: This command can be used in all three machine modes (cluster, group, machine).
Batch Command: This command supports a batch format.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-218
Chapter 3
Example
In this example, the scanconfig command sets these parameters:
Note
MIME types of video/*, audio/*, image/* are skipped (not scanned for content).
Nested (recursive) archive attachments up to 10 levels are scanned. (The default is 5 levels.)
The maximum size for attachments to be scanned is 25 megabytes; anything larger will be skipped.
(The default is 5 megabytes.)
Attachments that were not scanned are assumed to not match the search pattern. (This is the default
behavior.)
ASCII encoding is configured for use when none is specified for plain body text or anything with
MIME type plain/text or plain/html.
When setting the assume the attachment matches the search pattern to Y, messages that cannot be
scanned will cause the message filter rule to evaluate to true. This could result in unexpected behavior,
such as the quarantining of messages that do not match a dictionary, but were quarantined because their
content could not be correctly scanned. This setting does not apply to RSA Email DLP scanning.
mail3.example.com> scanconfig
There are currently 5 attachment type mappings configured to be SKIPPED.
Choose the operation you want to perform:
- NEW - Add a new entry.
- DELETE - Remove an entry.
- SETUP - Configure scanning behavior.
- IMPORT - Load mappings from a file.
- EXPORT - Save mappings to a file.
- PRINT - Display the list.
- CLEAR - Remove all entries.
- SMIME - Configure S/MIME unpacking.
[]> setup
1. Scan only attachments with MIME types or fingerprints in the list.
2. Skip attachments with MIME types or fingerprints in the list.
Choose one:
[2]> 2
Enter the maximum depth of attachment recursion to scan:
[5]> 10
Enter the maximum size of attachment to scan:
[5242880]> 10m
Do you want to scan attachment metadata? [Y]> y
Enter the attachment scanning timeout (in seconds):
[30]> 180
If a message has attachments that were not scanned for any reason (e.g.
because of size, depth limits, or scanning timeout), assume the attachment matches the
search pattern? [N]> n
If a message could not be deconstructed into its component parts in order to remove
specified attachments, the system should:
1. Deliver
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-219
Chapter 3
Policy Enforcement
2. Bounce
3. Drop
[1]>
Configure encoding to use when none is specified for plain body text or
anything with MIME type plain/text or plain/html.
1. US-ASCII
2. Unicode (UTF-8)
3. Unicode (UTF-16)
4. Western European/Latin-1 (ISO 8859-1)
5. Western European/Latin-1 (Windows CP1252)
6. Traditional Chinese (Big 5)
7. Simplified Chinese (GB 2312)
8. Simplified Chinese (HZ GB 2312)
9. Korean (ISO 2022-KR)
10. Korean (KS-C-5601/EUC-KR)
11. Japanese (Shift-JIS (X0123))
12. Japanese (ISO-2022-JP)
13. Japanese (EUC)
[1]> 1
Scan behavior changed.
There are currently 5 attachment type mappings configured to be SKIPPED.
Choose the operation you want to perform:
- NEW - Add a new entry.
- DELETE - Remove an entry.
- SETUP - Configure scanning behavior.
- IMPORT - Load mappings from a file.
- EXPORT - Save mappings to a file.
- PRINT - Display the list.
- CLEAR - Remove all entries.
- SMIME - Configure S/MIME unpacking.
[]> print
1. Fingerprint
2. Fingerprint
3. MIME Type
4. MIME Type
5. MIME Type
Image
Media
audio/*
image/*
video/*
stripheaders
Description
Define a list of message headers to remove.
Usage
Commit: This command requires a commit.
Cluster Management: This command can be used in all three machine modes (cluster, group, machine).
Batch Command: This command does not support a batch format.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-220
Chapter 3
Example
mail3.example.com> stripheaders
Not currently stripping any headers.
Choose the operation you want to perform:
- SETUP - Set message headers to remove.
[]> setup
Enter the list of headers you wish to strip from the messages before they are delivered.
Separate multiple headers with commas.
[]> Delivered-To
Currently stripping headers: Delivered-To
textconfig
Description
Configure text resources such as anti-virus alert templates, message disclaimers, and notification
templates, including DLP, bounce, and encryption notifications.
Usage
Commit: This command requires a commit.
Cluster Management: This command can be used in all three machine modes (cluster, group, machine).
Batch Command: This command does not support a batch format.
Example
Use textconfig -> NEW to create text resources, and textconfig > delete to remove them.
mail3.example.com> textconfig
Choose the operation you want to perform:
- NEW - Create a new text resource.
- IMPORT - Import a text resource from a file.
[]> new
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-221
Chapter 3
Policy Enforcement
Use textconfig -> EDIT to modify an existing text resource. You can change the encoding or replace
the text of the selected text resource.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-222
Chapter 3
mail3.example.com> textconfig
Current Text Resources:
1. footer.2.message (Message Footer)
Choose the operation you want to perform:
- NEW - Create a new text resource.
- IMPORT - Import a text resource from a file.
- EXPORT - Export text resource to a file.
- PRINT - Display the content of a resource.
- EDIT - Modify a resource.
- DELETE - Remove a resource from the system.
- LIST - List configured resources.
[]> import
What kind of text resource would you like to create?
1. Anti-Virus Container Template
2. Anti-Virus Notification Template
3. DLP Notification Template
4. Bounce and Encryption Failure Notification Template
5. Message Disclaimer
6. Encryption Notification Template (HTML)
7. Encryption Notification Template (text)
8. Notification Template
[1]> 8
Please create a name for the notification template:
[]> strip.mp3files
Enter the name of the file to import:
[]> strip.mp3.txt
Enter the encoding to use for the imported file:
1. US-ASCII
[ list of encodings ]
[1]>
Notification template "strip.mp3files" created.
Current Text Resources:
1. disclaimer.2.message (Message Disclaimer)
2. strip.mp3files (Notification Template)
Choose the operation you want to perform:
- NEW - Create a new text resource.
- IMPORT - Import a text resource from a file.
- EXPORT - Export text resource to a file.
- PRINT - Display the content of a resource.
- EDIT - Modify a resource.
- DELETE - Remove a resource from the system.
- LIST - List configured resources.
[]>
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-223
Chapter 3
alertconfig
displayalerts
findevent
grep
logconfig
rollovernow
snmpconfig
tail
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-224
Chapter 3
alertconfig
Description
Configure email alerts.
Usage
Commit: This command requires a commit.
Cluster Management: This command can be used in all three machine modes (cluster, group, machine).
Batch Command: This command does not support a batch format.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-225
Chapter 3
displayalerts
Description
Display the last n alerts sent by the appliance
Usage
Commit: This command does not require a commit.
Cluster Management: This command can be used in all three machine modes (cluster, group, machine).
Batch Command: This command does not support a batch format.
Example
> displayalerts
Date and Time Stamp
Description
Last message occurred 8 times between Tue Mar 10 10:29:57 2015 and Tue Mar 10 11:18:24
2015.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-226
Chapter 3
Last message occurred 9 times between Tue Mar 10 09:26:54 2015 and Tue Mar 10 10:22:56
2015.
findevent
Description
Find events in mail log files
Usage
Commit: This command does not require a commit.
Cluster Management: This command can be used in all three machine modes (cluster, group, machine).
Batch Command: This command does not support a batch format.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-227
Chapter 3
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-228
Chapter 3
grep
Description
Searches for text in a log file.
Usage
Commit: This command does not require a commit.
Cluster Management: This command is restricted to machine mode. It is further restricted to the login
host (i.e., the specific machine you are logged onto). This command requires access to the local file
system.
Batch Command: This command does not support a batch format.
The grep command can be used to search for text strings within logs. Use the following syntax when
you run the grep command:
grep [-C count] [-e regex] [-i] [-p] [-t] [regex] log_name
Note
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-229
Chapter 3
Use the following options when you run the grep command:
Table 3-12
Option
Description
-C
-e
-i
-p
-t
regex
Example of grep
The following example shows a search for the text string clean or viral within the antivirus logs. The
grep command includes a regex expression:
mail3.example.com> grep "CLEAN\\|VIRAL" antivirus
Fri Jun 9 21:50:25
Fri Jun 9 21:53:15
Fri Jun 9 22:47:41
Fri Jun 9 22:47:41
Fri Jun 9 22:47:41
Fri Jun 9 22:47:41
Fri Jun 9 22:47:42
Fri Jun 9 22:53:04
Fri Jun 9 22:53:05
Fri Jun 9 22:53:06
Fri Jun 9 22:53:07
Fri Jun 9 22:53:08
Fri Jun 9 22:53:08
mail3.example.com>
2006
2006
2006
2006
2006
2006
2006
2006
2006
2006
2006
2006
2006
Info:
Info:
Info:
Info:
Info:
Info:
Info:
Info:
Info:
Info:
Info:
Info:
Info:
sophos
sophos
sophos
sophos
sophos
sophos
sophos
sophos
sophos
sophos
sophos
sophos
sophos
antivirus
antivirus
antivirus
antivirus
antivirus
antivirus
antivirus
antivirus
antivirus
antivirus
antivirus
antivirus
antivirus
MID
MID
MID
MID
MID
MID
MID
MID
MID
MID
MID
MID
MID
1 - Result 'CLEAN' ()
2 - Result 'CLEAN' ()
3 - Result 'CLEAN' ()
4 - Result 'CLEAN' ()
5 - Result 'CLEAN' ()
6 - Result 'CLEAN' ()
12 - Result 'CLEAN' ()
18 - Result 'VIRAL' ()
16 - Result 'VIRAL' ()
19 - Result 'VIRAL' ()
21 - Result 'VIRAL' ()
20 - Result 'VIRAL' ()
22 - Result 'VIRAL' ()
logconfig
Description
Configure access to log files.
Usage
Commit: This command requires a commit.
Cluster Management: This command can be used in all three machine modes (cluster, group, machine).
Batch Command: This command does not support a batch format.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-230
Chapter 3
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-231
Chapter 3
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-232
Chapter 3
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-233
Chapter 3
[N]> y
Do you want to automatically scan the host for its SSH key, or enter it
manually?
1. Automatically scan.
2. Enter manually.
[1]> 1
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-234
Chapter 3
SSH2:dsa
10.1.1.1 ssh-dss
AAAAB3NzaC1kc3MAAACBALwGi4IlWLDVndbIwEsArt9LVE2ts5yE9JBTSdUwLvoq0G3FRqifrce92zgyHtc/ZWyXav
UTIM3Xd1bpiEcscMp2XKpSnPPx21y8bqkpJsSCQcM8zZMDjnOPm8ghiwHXYh7oNEUJCCPnPxAy44rlJ5Yz4x9eIoAL
p0dHU0GR+j1NAAAAFQDQi5GY/X9PlDM3fPMvEx7wc0edlwAAAIB9cgMTEFP1WTAGrlRtbowZP5zWZtVDTxLhdXzjlo
4+bB4hBR7DKuc80+naAFnThyH/J8R3WlJVF79M5geKJbXzuJGDK3Zwl3UYefPqBqXp2O1zLRQSJYx1WhwYz/rooopN
1BnF4sh12mtq3tde1176bQgtwaQA4wKO15k3zOWsPwAAAIAicRYat3y+Blv/V6wdE6BBk+oULv3eK38gafuip4WMBx
kG9GO6EQi8nss82oznwWBy/pITRQfh4MBmlxTF4VEY00sARrlZtuUJC1QGQvCgh7Nd3YNais2CSbEKBEaIOTF6+SX2
RNpcUF3Wg5ygw92xtqQPKMcZeLtK2ZJRkhC+Vw==
Add the preceding host key(s) for 10.1.1.1?
[Y]> y
[N]> y
SSH1:rsa
10.1.1.1 1024 35
122606420764474441178474079962066753259278682648965870690129496065430424463013457294798980
627829828033793152226448694514316218272814453986931612508282328008815740072109975632356478
532128816187806830746328234327778100131128176672666244511191783747965898000855947022484692
079466697707373948871554575173520565607
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-235
Chapter 3
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-236
Chapter 3
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-237
Chapter 3
rollovernow
Description
Roll over a log file.
Usage
Commit: This command does not require a commit.
Cluster Management: This command is restricted to machine mode.
Batch Command: This command does not support a batch format.
Example
mail3.example.com> rollovernow
snmpconfig
Description
Configure SNMP.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-238
Chapter 3
Usage
Commit: This command requires a commit.
Cluster Management: This command can be used in all three machine modes (cluster, group, machine).
Batch Command: This command does not support a batch format.
Example
In the following example, the snmpconfig command is used to enable SNMP on the PublicNet
interface on port 161. A passphrase for version 3 is entered and then re-entered for confirmation. The
system is configured to service version 1 and 2 requests, and the community string public is entered for
GET requests from those versions 1 and 2. The trap target of snmp-monitor.example.com is entered.
Finally, system location and contact information is entered.
mail3.example.com> snmpconfig
Current SNMP settings:
SNMP Disabled.
Choose the operation you want to perform:
- SETUP - Configure SNMP.
[]> setup
Do you want to enable SNMP? [N]> y
Please choose an IP interface for SNMP requests.
1. Data 1 (192.168.1.1/24: buttercup.run)
2. Data 2 (192.168.2.1/24: buttercup.run)
3. Management (192.168.44.44/24: buttercup.run)
[1]>
Enter the SNMPv3 passphrase.
>
Please enter the SNMPv3 passphrase again to confirm.
>
Which port shall the SNMP daemon listen on?
[161]>
Service SNMP V1/V2c requests? [N]> y
Enter the SNMP V1/V2c community string.
[]> public
From which network shall SNMP V1/V2c requests be allowed?
[192.168.2.0/24]>
Enter the Trap target (IP address). Enter "None" to disable traps.
[None]> snmp-monitor.example.com
Enterprise Trap Status
1. RAIDStatusChange
Enabled
2. fanFailure
Enabled
3. highTemperature
Enabled
4. keyExpiration
Enabled
5. linkDown
Enabled
6. linkUp
Enabled
7. powerSupplyStatusChange
Enabled
8. resourceConservationMode
Enabled
9. updateFailure
Enabled
Do you want to change any of these settings? [N]> y
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-239
Chapter 3
tail
Description
Continuously display the end of a log file. The tail command also accepts the name or number of a log
to view as a parameter: tail 9 or tail mail_logs.
Usage
Commit: This command does not require a commit.
Cluster Management: This command is restricted to machine mode. It is further restricted to the login
host (i.e., the specific machine you are logged onto). This command requires access to the local file
system.
Batch Command: This command does not support a batch format.
Example
mail3.example.com> tail
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-240
Chapter 3
Info: PID 274: User system commit changes: Automated Update for
Info: PID 19626: User admin commit changes:
Info: PID 274: User system commit changes: Updated filter logs
Info:
Info:
Info:
Info:
Info:
Info:
suspended.
receiving.
resumed.
resumed.
00:00:00
Reporting
This section contains the following CLI commands:
reportingconfig
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-241
Chapter 3
Reporting
reportingconfig
Using the reportingconfig command
The following subcommands are available within the reportingconfig submenu:
Table 3-13
reportingconfig Subcommands
Syntax
Description
Availability
filters
M-Series only
alert_timeout
domain
mode
C-, M-Series
Enable centralized reporting on the
Security Management appliance.
Enable centralized or local reporting for
the Email Security appliance.
mailsetup
M-Series only
C-Series only
Usage
Commit: This command requires a commit.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-242
Chapter 3
reporting data
- DOMAIN - Configure domain report settings.
- MODE - Enable/disable centralized reporting.
[]>
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-243
Chapter 3
Reporting
While in centralized mode the C-series will store reporting data for the M-series to
collect. If the M-series does not collect that data then eventually the C-series will
begin to overwrite the oldest data with new data.
A maximum of 24 hours of reporting data will be stored.
How many hours of reporting data should be stored before data loss?
[24]> 48
SenderBase timeout used by the web interface: 5 seconds
Sender Reputation Multiplier: 3
The current level of reporting data recording is: unlimited
No custom second level domains are defined.
Legacy mailflow report: Disabled
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-244
Chapter 3
Senderbase
This section contains the following CLI commands:
sbstatus
senderbaseconfig
sbstatus
Description
Display status of SenderBase queries.
Usage
Commit: This command requires a commit.
Cluster Management: This command can be used in all three machine modes (cluster, group, machine).
Batch Command: This command does not support a batch format.
Example
mail3.example.com> sbstatus
SenderBase host status
Status as of:
Tue Oct 21 10:55:04 2003
Host up/down:
up
If the appliance is unable to contact the SenderBase Reputation Service, or the service has never been
contacted, the following is displayed:
mail3.example.com> sbstatus
SenderBase host status
Host up/down:
Unknown (never contacted)
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-245
Chapter 3
senderbaseconfig
Description
Configure SenderBase connection settings.
Usage
Commit: This command requires a commit.
Cluster Management: This command can be used in all three machine modes (cluster, group, machine).
Batch Command: This command does not support a batch format.
Example
mail3.example.com> senderbaseconfig
Share statistics with SenderBase Information Service: Enabled
Choose the operation you want to perform:
- SETUP - Configure SenderBase Network Participation settings
[]> setup
Do you want to share statistical data with the SenderBase Information Service
(recommended)? [Y]>
Share statistics with SenderBase Information Service: Enabled
Choose the operation you want to perform:
- SETUP - Configure SenderBase Network Participation settings
[]>
callaheadconfig
listenerconfig
localeconfig
smtpauthconfig
callaheadconfig
Description
Add, edit, and remove SMTP Call-Ahead profiles
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-246
Chapter 3
Usage
Commit: This command requires a commit.
Cluster Management: This command can be used in all three machine modes (cluster, group, machine).
Batch Command: This command does not support a batch format.
Example
In the following example you can create a new SMTP call-ahead profile for delivery host.
> callaheadconfig
No SMTP Call-Ahead profiles are configured on the system.
Choose the operation you want to perform:
- NEW - Create a new profile.
[]> new
Select the type of profile you want to create:
1. Delivery Host
2. Static Call-Ahead Servers
[1]> 1
Please enter a name for the profile:
[]> delhost01
Advanced Settings:
MAIL FROM Address: <>
Interface: Auto
Timeout Value: 30
Validation Failure Action: ACCEPT
Temporary Failure Action: REJECT with same code
Maximum number of connections: 5
Maximum number of validation queries: 1000
Cache size: 10000
Cache TTL: 900
Do you want to change advanced settings? [N]> n
Currently configured SMTP Call-Ahead profiles:
1. delhost01 (Delivery Host)
Choose the operation you want to perform:
- NEW - Create a new profile.
- EDIT - Modify a profile.
- DELETE - Delete a profile.
- PRINT - Display profile information.
- TEST - Test profile.
- FLUSHCACHE - Flush SMTP Call-Ahead cache.
[]>
In the following example you can create a new SMTP call-ahead profile for call ahead server.
> callaheadconfig
Currently configured SMTP Call-Ahead profiles:
1. delhost01 (Delivery Host)
Choose the operation you want to perform:
- NEW - Create a new profile.
- EDIT - Modify a profile.
- DELETE - Delete a profile.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-247
Chapter 3
listenerconfig
Description
The listenerconfig command allows you to create, edit, and delete a listener. AsyncOS requires that you
specify criteria that messages must meet in order to be accepted and then relayed to recipient hosts
either internal to your network or to external recipients on the Internet.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-248
Chapter 3
These qualifying criteria are defined in listeners; collectively, they define and enforce your mail flow
policies. Listeners also define how the appliance communicates with the system that is injecting email.
Table 3-14
listenerconfig Commands
Name
Unique nickname you supply for the listener, for future reference.
The names you define for listeners are case-sensitive. AsyncOS does
not allow you to create two identical listener names.
IP Interface
Mail protocol
IP Port
The specific IP
port used for
connections to the
listener. by default
SMTP uses port
25 and QMQP
uses port 628.
Public
Private
Blackhole
Listener Type:
Usage
Commit: This command requires a commit.
Cluster Management: This command can be used in all three machine modes (cluster, group, machine).
Batch Command: This command supports a batch format.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-249
Chapter 3
Deleting a listener:
listenerconfig delete <name>
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-250
Chapter 3
Rename a sendergroup
listenerconfig edit sendergroup <name> hostaccess edit sendergroup
<name> rename <name>
Deleting a policy
listenerconfig edit <name> hostaccess delete policy <name>
Deleting all user defined sendergroups and policies from the HAT
listenerconfig edit <name> hostaccess clear
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-251
Chapter 3
Table 3-15
Argument
Description
<behavior>
<filename>
<group>
A sendergroup <name>.
<host>
<host_list>
Note
<name>
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-252
Chapter 3
Table 3-15
--max_size
--max_conn
--max_msgs
--max_rcpt
--override
--cust_acc
--acc_code
--cust_rej
--rej_code
--rate_lim
--cust_lim
--lim_code
--use_sb
--as_scan
--av_scan
--dhap
--tls
--sig_bits
--dkim_signing
--dkim_verification
--dkim_verification_profile
<name>
[options]
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-253
Chapter 3
Table 3-15
--spf
--spf_conf_level
--spf_downgrade_pra
--spf_helo_test
--dmarc_verification
--dmarc_verification_profile
<name>
--dmarc_agg_reports
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-254
Chapter 3
Exporting a RAT
listenerconfig edit <name> rcptacess export <filename>
Table 3-16
Argument
Description
Enter the hosts to add. Hosts can be formatted as
follows:
CIDR addresses (10.1.1.0/24)
Hostname (crm.example.com)
Partial Hostname (.example.com)
Usernames (postmaster@)
Full email addresses ([email protected],
joe@[1.2.3.4]
Note
<rat_addr>
--action
--cust_resp
--resp_code
--bypass_rc
--bypass_la
<options>
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-255
Chapter 3
Please specify the systems allowed to relay email through the IronPort C60.
Hostnames such as "example.com" are allowed.
Partial hostnames such as ".example.com" are allowed.
IP addresses, IP address ranges, and partial IP addresses are allowed.
Separate multiple entries with commas.
[]> .example.com
Do you want to enable rate limiting for this listener? (Rate limiting defines the maximum
number of recipients per hour you are willing to receive from a remote domain.)
[N]> n
Default Policy Parameters
==========================
Maximum Message Size: 100M
Maximum Number Of Connections From A Single IP: 600
Maximum Number Of Messages Per Connection: 10,000
Maximum Number Of Recipients Per Message: 100,000
Maximum Number Of Recipients Per Hour: Disabled
Use SenderBase for Flow Control: No
Spam Detection Enabled: No
Virus Detection Enabled: Yes
Allow TLS Connections: No
Allow SMTP Authentication: No
Require TLS To Offer SMTP authentication: No
Would you like to change the default host access policy? [N]> n
Listener OutboundMail created.
Defaults have been set for a Private listener.
Use the listenerconfig->EDIT command to customize the listener.
Currently configured listeners:
1. InboundMail (on PublicNet, 192.168.2.1) SMTP TCP Port 25 Public
2. OutboundMail (on PrivateNet, 192.168.1.1) SMTP TCP Port 25 Private
Choose the operation you want to perform:
- NEW - Create a new listener.
- EDIT - Modify a listener.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-256
Chapter 3
Example - Customizing the Host Acess Table (HAT ) for a listener via Export and Import
Many of the subcommands within the listenerconfig command allow you to import and export data in
order to make large configuration changes without having to enter data piecemeal in the CLI.
These steps use the CLI to modify the Host Access Table (HAT) of a listener by exporting, modifying,
and importing a file. You can also use the HAT CLI editor or the GUI to customize the HAT for a listener.
For more information, see the Configuring the Gateway to Receive Mail and Using Mail Flow
Monitor chapters in the User Guide for AsyncOS for Cisco Email Security Appliances.
To customize a HAT for a listener you have defined via export and import:
Step 1
Use the hostaccess -> export subcommands of listenerconfig to export the default HAT to a file.
In the following example, the HAT for the public listener InboundMail is printed, and then exported to
a file named inbound.HAT.txt
mail3.example.com> listenerconfig
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-257
Chapter 3
SMTP Services Configuration
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-258
Chapter 3
max_msgs_per_session = 10
spam_check = "on"
use_sb = "on"
max_message_size = 1048576
max_rcpts_per_msg = 25
max_concurrency = 10
}
WHITELIST:
$TRUSTED (My trusted senders have no anti-spam or rate limiting)
BLACKLIST:
$BLOCKED (Spammers are rejected)
SUSPECTLIST:
$THROTTLED (Suspicious senders are throttled)
UNKNOWNLIST:
$ACCEPTED (Reviewed but undecided, continue normal acceptance)
ALL
$ACCEPTED (Everyone else)
Default Policy Parameters
=========================
Allow TLS Connections: No
Allow SMTP Authentication: No
Require TLS To Offer SMTP authentication: No
Maximum Concurrency Per IP: 1,000
Maximum Message Size: 100M
Maximum Messages Per Connection: 1,000
Maximum Recipients Per Message: 1,000
Maximum Recipients Per Hour: Disabled
Use SenderBase For Flow Control: Yes
Spam Detection Enabled: Yes
Virus Detection Enabled: Yes
There are currently 4 policies defined.
There are currently 5 sender groups.
Choose the operation you want to perform:
- NEW - Create a new entry.
- EDIT - Modify an entry.
- DELETE - Remove an entry.
- MOVE - Move an entry.
- DEFAULT - Set the defaults.
- PRINT - Display the table.
- IMPORT - Import a table from a file.
- EXPORT - Export the table to a file.
- CLEAR - Remove all entries.
[]> export
Enter a name for the exported file:
[]> inbound.HAT.txt
File written on machine "mail3.example.com".
Step 2
Outside of the Command Line Interface (CLI), get the file inbound.HAT.txt.
Step 3
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-259
Chapter 3
In this example, the following entries are added to the HAT above the ALL entry:
spamdomain.com
.spamdomain.com
251.192.1.
169.254.10.10
REJECT
REJECT
TCPREFUSE
RELAY
The first two entries reject all connections from the remote hosts in the domain spamdomain.com
Security appliance as an SMTP relay for all of its outbound email to the Internet
Note
The order that rules appear in the HAT is important. The HAT is read from top to bottom for each
host that attempts to connect to the listener. If a rule matches a connecting host, the action is
taken for that connection immediately. You should place all custom entries in the HAT above an
ALL host definition. You can also use the HAT CLI editor or the GUI to customize the HAT for
a listener. For more information, see the Configuring the Gateway to Receive Mail and Using
Mail Flow Monitor chapters in the User Guide for AsyncOS for Cisco Email Security
Appliances.
Step 4
Save the file and place it in the configuration directory for the interface so that it can be imported. (See
Appendix B, Accessing the Appliance, for more information.)
Step 5
Use the hostaccess -> import subcommand of listenerconfig to import the edited Host Access Table
file.
In the following example, the edited file named inbound.HAT.txt is imported into the HAT for the
InboundMail listener. The new entries are printed using the print subcommand.
mail3.example.com> listenerconfig
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-260
Chapter 3
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-261
Chapter 3
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-262
Chapter 3
251.192.1.
TCPREFUSE (TCPREFUSE the IP addresses in "251.192.1")
169.254.10.10
RELAY (RELAY the address 169.254.10.10)
ALL
$ACCEPTED (Everyone else)
Remember to issue the commit command after you import so that the configuration change takes effect.
Example - Enabling Public Key Harvesting and S/MIME Decryption and Verification
The following example shows how to:
Retrieve (harvest) public key from the incoming S/MIME signed messages
mail.example.com> listenerconfig
Currently configured listeners:
1. MyListener (on Management, 172.29.181.70) SMTP TCP Port 25 Public
Choose the operation you want to perform:
- NEW - Create a new listener.
- EDIT - Modify a listener.
- DELETE - Remove a listener.
- SETUP - Change global settings.
[]> edit
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-263
Chapter 3
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-264
Chapter 3
[N]>
[N]>
[N]>
[Y]>
Enter the maximum number of invalid recipients per hour from a remote host.
[25]>
Select an action to apply when a recipient is rejected due to DHAP:
1. Drop
2. Code
[1]>
Would you like to specify a custom SMTP DHAP response? [Y]>
Enter the SMTP code to use in the response. 550 is the standard code.
[550]>
Enter your custom SMTP response.
custom_response
[Y]>
[Y]>
[Y]>
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-265
Chapter 3
[N]>
[N]>
[N]> y
[N]>
[Y]>
[N]> y
[N]>
[N]>
[N]>
[N]>
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-266
[N]>
Chapter 3
Parameter
Syntax
Values
Example Values
max_msgs_per_session
Number
1000
max_rcpts_per_msg
Number
10000
1k
max_message_size
Number
1048576
20M
Maximum concurrent
connections allowed to
this listener
max_concurrency
Number
1000
smtp_banner_code
Number
220
smtp_banner_text
String
Accepted
smtp_banner_code
Number
550
String
Rejected
on | off |
default
use_override_hostname
default
override_hostname
String
newhostname
Use TLS
tls
on | off |
on
spam_check
on | off
off
virus_check
on | off
off
max_rcpts_per_hour
Number
5k
max_rcpts_per_hour_code
Number
452
max_rcpts_per_hour_text
String
Too many
recipients
Use SenderBase
use_sb
on | off
on
required
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-267
Chapter 3
Table 3-17
Parameter
Syntax
Values
Example Values
Define SenderBase
Reputation Score
sbrs[value1:value2]
-10.0- 10.0
sbrs[-10:-7.5]
dhap_limit
Number
150
Neutral. The domain owner does not assert whether the client is authorized to use the given identity.
SoftFail. The domain owner believes the host is not authorized to use the given identity but is not
willing to make a definitive statement.
Fail. The client is not authorized to send mail with the given identity.
The appliance accepts the message for a Pass result unless you configure the SIDF Compatible
conformance level to downgrade a Pass result of the PRA identity to None if there are Resent-Sender:
or Resent-From: headers present in the message. The appliance then takes the SMTP action specified for
when the PRA check returns None.
If you choose not to define the SMTP actions for an identity check, the appliance automatically accepts
all verification results, including Fail.
The appliance terminates the session if the identity verification result matches a REJECT action for any
of the enabled identity checks. For example, an administrator configures a listener to accept messages
based on all HELO identity check results, including Fail, but also configures it to reject messages for a
Fail result from the MAIL FROM identity check. If a message fails the HELO identity check, the session
proceeds because the appliance accepts that result. If the message then fails the MAIL FROM identity
check, the listener terminates the session and then returns the STMP response for the REJECT action.
The SMTP response is a code number and message that the appliance returns when it rejects a message
based on the SPF/SIDF verification result. The TempError result returns a different SMTP response from
the other verification results. For TempError, the default response code is 451 and the default message
text is #4.4.3 Temporary error occurred during SPF verification. For all other verification results,
the default response code is 550 and the default message text is #5.7.1 SPF unauthorized mail is
prohibited. You can specify your own response code and message text for TempError and the other
verification results.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-268
Chapter 3
Optionally, you can configure the appliance to return a third-party response from the SPF publisher
domain if the REJECT action is taken for Neutral, SoftFail, or Fail verification result. By default, the
appliance returns the following response:
550-#5.7.1 SPF unauthorized mail is prohibited.
550-The domain example.com explains:
550 <Response text from SPF domain publisher>
To enable these SPF/SIDF settings, use the listenerconfig -> edit subcommand and select a listener.
Then use the hostaccess -> default subcommand to edit the Host Access Tables default settings.
Answer yes to the following prompts to configure the SPF controls:
Would you like to change SPF/SIDF settings?
[N]> yes
[Y]> yes
The following SPF control settings are available for the Host Access Table:
Table 3-18
Conformance Level
SPF Only
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-269
Chapter 3
Table 3-18
Conformance Level
SIDF Compatible
SIDF Strict
PRA Identity
PRA Identity
The following example shows a user configuring the SPF/SIDF verification using the SPF Only
conformance level. The appliance performs the HELO identity check and accepts the None and Neutral
verification results and rejects the others. The CLI prompts for the SMTP actions are the same for all
identity types. The user does not define the SMTP actions for the MAIL FROM identity. The appliance
automatically accepts all verification results for the identity. The appliance uses the default reject code
and text for all REJECT results.
[N]> yes
[N]> yes
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-270
Chapter 3
The following shows how the SPF/SIDF settings are displayed for the listeners Default Policy
Parameters.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-271
Chapter 3
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-272
Chapter 3
perform:
file.
file.
policies to system default.
Enter the default maximum message size. Add a trailing k for kilobytes, M for megabytes,
or no letter for bytes.
[20M]>
Enter the maximum number of concurrent connections allowed from a single IP address.
[10]>
Enter the maximum number of messages per connection.
[10]>
Enter the maximum number of recipients per message.
[50]>
Do you want to override the hostname in the SMTP banner?
[N]>
[N]>
[N]>
[Y]>
Enter the maximum number of invalid recipients per hour from a remote host.
[25]>
Select an action to apply when a recipient is rejected due to DHAP:
1. Drop
2. Code
[1]>
Would you like to specify a custom SMTP DHAP response? [Y]>
Enter the SMTP code to use in the response. 550 is the standard code.
[550]>
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-273
Chapter 3
[Y]>
[Y]>
[Y]>
[N]>
[N]>
[N]>
[N]> Y
Would you like to specify a custom SMTP response for envelope sender domains which do not
resolve? [Y]>
Enter the SMTP code to use in the response. 451 is the standard code.
[451]>
Enter your custom SMTP response.
Would you like to specify a custom SMTP response for envelope sender domains which do not
exist? [Y]>
Enter the SMTP code to use in the response. 553 is the standard code.
[553]>
Enter your custom SMTP response.
[N]>
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-274
[N]>
Chapter 3
==========================
Maximum Message Size: 20M
Maximum Number Of Concurrent Connections From A Single IP: 10
Maximum Number Of Messages Per Connection: 10
Maximum Number Of Recipients Per Message: 50
Directory Harvest Attack Prevention: Enabled
Maximum Number Of Invalid Recipients Per Hour: 25
Maximum Number Of Recipients Per Hour: Disabled
Maximum Number of Recipients per Envelope Sender: Disabled
Use SenderBase for Flow Control: Yes
Spam Detection Enabled: Yes
Virus Detection Enabled: Yes
Allow TLS Connections: No
Allow SMTP Authentication: No
Require TLS To Offer SMTP authentication: No
DKIM/DomainKeys Signing Enabled: No
DKIM Verification Enabled: No
SPF/SIDF Verification Enabled: No
DMARC Verification Enabled: Yes
DMARC Verification Profile: DEFAULT
Aggregate reports: Yes
Envelope Sender DNS Verification Enabled: Yes
Domain Exception Table Enabled: No
Accept untagged bounces: No
There are currently 4 policies defined.
There are currently 5 sender groups.
Choose the operation you want to
- NEW - Create a new entry.
- EDIT - Modify an entry.
- DELETE - Remove an entry.
- MOVE - Move an entry.
- DEFAULT - Set the defaults.
- PRINT - Display the table.
- IMPORT - Import a table from a
- EXPORT - Export the table to a
- RESET - Remove senders and set
[]>
perform:
file.
file.
policies to system default.
Name: Listener 1
Type: Public
Interface: Management (172.29.181.70/24) TCP Port 25
Protocol: SMTP
Default Domain: <none configured>
Max Concurrent Connections: 300 (TCP Queue: 50)
Domain Map: Disabled
TLS: No
SMTP Authentication: Disabled
Bounce Profile: Default
Use SenderBase For Reputation Filters and IP Profiling: Yes
Footer: None
Heading: None
SMTP Call-Ahead: Disabled
LDAP: Off
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-275
Chapter 3
localeconfig
Description
Configure multi-lingual settings
Usage
Commit: This command requires a commit.
Cluster Management: This command can be used in all three machine modes (cluster, group, machine).
Batch Command: This command does not support a batch format.
Example
mail3.example.com> localeconfig
Behavior when modifying headers: Use encoding of message body
Behavior for untagged non-ASCII headers: Impose encoding of message body
Behavior for mismatched encodings bodies and footers: Use encoding of message footer
Choose the operation you want to perform:
- SETUP - Configure multi-lingual settings.
[]> setup
If a header is modified, encode the new header in the same encoding as the message body?
(Some MUAs incorrectly handle headers encoded in a different encoding than the body.
However, encoding a modified header in the same encoding as the message body may cause
certain characters in the modified header to be lost.) [Y]>
If a non-ASCII header is not properly tagged with a character set, impose the encoding of
the body on the header during processing and final representation of the message? (Many
MUAs create non-RFC-compliant headers that are then handled in an undefined way. Imposing
the encoding of the body on the header may encode the header more precisely.) [Y]>
When there is an encoding mismatch between the message body and a footer, the system
initially attempts to encode the entire message in the same encoding as the message body.
If the system cannot combine the message body and the footer in the same encoding, do you
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-276
Chapter 3
want the system to failover and attempt to encode the entire message using the encoding of
the message footer? (When this feature is enabled, the system will attempt to display the
footer "in-line" rather than defaulting to adding it as an attachment.) [N]> y
Behavior when modifying headers: Use encoding of message body
Behavior for untagged non-ASCII headers: Impose encoding of message body
Behavior for mismatched encodings bodies and footers: Use encoding of message body
Choose the operation you want to perform:
- SETUP - Configure multi-lingual settings.
[]>mail3.example.com>
smtpauthconfig
Description
Configure SMTP Auth outgoing and forwarding profiles.
Usage
Commit: This command requires a commit.
Cluster Management: This command can be used in all three machine modes (cluster, group, machine).
Batch Command: This command does not support a batch format.
Example
In the following example, the smtpauthconfig command is used to create a new, forwarding-based
profile for the server smtp2.example.com:
mail3.example.com> smtpauthconfig
Choose the operation you want to perform:
- NEW - Create a new SMTP Auth profile
[]> new
Choose the type of profile you wish to create:
- FORWARD - Create an SMTP Auth forwarding server group profile
- OUTGOING - Create an outgoing SMTP Auth profile
[]> forward
Enter a name for this profile:
[]> forwarding-based
Please begin entering forwarding servers for this group profile.
Enter a hostname or an IP address for the forwarding server:
[]> smtp2.example.com
Enter a port:
[25]>
Choose the interface to use for forwarding requests:
1. Auto
2. Data 1 (192.168.1.1/24: mail3.example.com)
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-277
Chapter 3
System Setup
Note
Note
You may specify more than one forwarding server in a profile. SASL mechanisms CRAM-MD5 and
DIGEST-MD5 are not supported between the Email Security appliance and a forwarding server.
System Setup
systemsetup
Description
First time system setup as well as re-installation of the system.
Usage
Commit: This command requires a commit.
Cluster Management: This command can be used in all three machine modes (cluster, group, machine).
Batch Command: This command does not support a batch format.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-278
Chapter 3
Example
mail3.example.com> systemsetup
WARNING: The system setup wizard will completely delete any existing
'listeners' and all associated settings including the 'Host Access Table' mail operations may be interrupted.
Are you sure you wish to continue? [Y]> y
Before you begin, please reset the administrator password to a new value.
Old password:
New password:
Retype new password:
*****
You will now configure the network settings for the IronPort C100.
Please create a fully qualified hostname for the IronPort C100 appliance
(Ex: "ironport-C100.example.com"):
[]> ironport-C100.example.com
*****
You will now assign an IP address for the "Data 1" interface.
Please create a nickname for the "Data 1" interface (Ex: "Data 1"):
[]> Data 1
Enter the static IP address for "Data 1" on the "Data 1" interface? (Ex:
"192.168.1.1"):
[]> 192.168.1.1
What is the netmask for this IP address? (Ex: "255.255.255.0" or "0xffffff00"):
[255.255.255.0]>
You have successfully configured IP Interface "Data 1".
*****
Would you like to assign a second IP address for the "Data 1" interface? [Y]> n
What is the IP address of the default router (gateway) on your network?:
[192.168.1.1]> 192.168.2.1
*****
Do you want to enable the web interface on the Data 1 interface? [Y]> y
Do you want to use secure HTTPS? [Y]> y
Note: The system will use a demo certificate for HTTPS.
Use the "certconfig" command to upload your own certificate.
*****
Do you want the IronPort C100 to use the Internet's root DNS servers or would
you like it to use your own DNS servers?
1. Use Internet root DNS servers
2. Use my own DNS servers
[1]> 2
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-279
Chapter 3
System Setup
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-280
Chapter 3
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-281
Chapter 3
System Setup
(Recommended) [Y]> y
*****
You will now configure scheduled reporting.
Please enter the email address(es) to deliver scheduled reports to.
(Leave blank to only archive reports on-box.)
Separate multiple addresses with commas.
[]> [email protected]
*****
You will now configure system time settings.
Please choose your continent:
1. Africa
2. America
...
11. GMT Offset
[11]> 2
*****
Would you like to commit these changes at this time? [Y]> y
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-282
Chapter 3
URL Filtering
This section contains the following CLI commands:
aggregatorconfig
urllistconfig
webcacheflush
websecurityadvancedconfig
websecurityconfig
websecuritydiagnostics
aggregatorconfig
Description
Configure address for Cisco Aggregator Server on the Email Security appliance. This server provides
details of the end users who clicked on rewritten URLs and the action (allowed, blocked or unknown)
associated with each user click.
Usage
Commit: This command requires a commit.
Cluster Management: This command can be used in all three machine modes (cluster, group, machine).
Batch Command: This command does not support a batch format.
Example
mail.example.com> aggregatorconfig
urllistconfig
Description
Configure or import whitelists of URLs that will not be evaluated by URL filtering features. These lists
are not used by the Outbreak Filters feature.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-283
Chapter 3
URL Filtering
Usage
Commit: This command requires a commit.
Cluster Management: This command can be used in all three machine modes (cluster, group, machine).
Batch Command: This command supports a batch format.
Example
> urllistconfig
No URL lists configured.
Choose the operation you want to perform:
NEW - Create a new URL list[]> new
Do you want to import a URL list?
[N]>
Enter a name for the URL list
[]> sample
Enter the URL domains that need to be skipped from scanning for URL Filtering.
Enter one URL domain per line and '.' to finish.
cisco.com
ironport.com/*
*.example.com
10.2.4.5/24
[2001:DB8::1]
URL list sample added.
There are currently 4 URL lists configured.
Choose the operation you want to perform:
- NEW - Create a new URL whitelist.
- EDIT - Modify an existing URL whitelist.
- DELETE - Delete an existing URL whitelist.
[]>EDIT
Choose the operation to edit the URL whitelist:
IMPORT Import a file into an existing URL whitelist
EXPORT Export an existing URL whitelist into a file
RENAME Rename an existing URL whitelist
[]>IMPORT
Assign new name to the imported list? (By default, name stored in the
file will be applied to the list)
[N] > Y
Enter name of the list > new_list
Enter filename to import from > URLfile
NOTE: These files will be stored in /pub/configuration
URL list new_list added.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-284
Chapter 3
webcacheflush
Description
Flush the cache used by URL filtering features. Use this command if you change the certificate that is
used for communication with Cisco Web Security Services. Generally, you will use this command only
at the direction of Cisco support.
Usage
Commit: This command does not require a commit.
Cluster Management: This command is restricted to machine mode.
Batch Command: This command does not support a batch format.
Example
> webcacheflush
Web Security cache has been flushed.
websecurityadvancedconfig
Description
Configure advanced settings for URL filtering.
Note
Except to change timeout values for troubleshooting purposes, use this command only under the
direction of Cisco support.
The timeout value is the value, in seconds, for communication with the cloud services that provide
reputation and category for URLs.
Usage
Commit: This command requires a commit.
Cluster Management: This command is restricted to machine mode.
Batch Command: This command supports a batch format.
Batch Format
For the batch format, see the CLI inline help.
Example
> websecurityadvancedconfig
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-285
Chapter 3
URL Filtering
Enter URL lookup timeout (includes any DNS lookup time) in seconds:
[15]>
Enter the URL cache size (no. of URLs):
[1215000]>
Do you want to disable DNS lookups? [N]>
Enter the maximum number of URLs that should be scanned:
[100]>
Enter the Web security service hostname:
[example.com]>
Enter the threshold value for outstanding requests:
[20]>
Do you want to verify server certificate? [Y]>
Enter the default time-to-live value (seconds):
[30]>
Do you want to include additional headers? [N]>
Enter the default debug log level for RPC server:
[Info]>
Enter the default debug log level for SDS cache:
[Info]>
Enter the default debug log level for HTTP client:
[Info]>
websecurityconfig
Description
Configure basic settings for URL filtering (URL reputation and URL category features.)
Normally, certificate management is automatic. Unless directed to do otherwise by Cisco TAC, you
should select No at the prompt to set a certificate.
Usage
Commit: This command requires a commit.
Cluster Management: This command can be used in all three machine modes (cluster, group, machine).
Batch Command: This command supports a batch format. See the inline CLI help for more details. Use
the help command to access the inline help for this command.
Example
mail.example.com> websecurityconfig
Enable URL Filtering? [N]> y
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-286
Chapter 3
websecuritydiagnostics
Description
View diagnostic statistics related to URL filtering.
Usage
Commit: This command does not require a commit.
Cluster Management: This command is restricted to machine mode.
Batch Command: This command does not support a batch format.
Example
mail.example.com> websecuritydiagnostics
Cache Size: 254
Cache Hits: 551
Response Time
Minimum: None
Average: 0.0
Maximum: None
DNS Lookup Time
Minimum: 9.4198775
Average: 10.1786801765
Maximum: 10.544356
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-287
Chapter 3
User Management
User Management
This section contains the following CLI commands:
userconfig
password or passwd
last
who
whoami
userconfig
Description
Manage user accounts and connections to external authentication sources.
Usage
Commit: This command requires a commit.
Cluster Management: This command is restricted to cluster mode.
Batch Command: This command supports a batch format. See the inline CLI help for more details. Use
the help command to access the inline help for this command, for example,
mail.example.com> userconfig help
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-288
Chapter 3
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-289
Chapter 3
User Management
password or passwd
Description
Change your password.
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-290
Chapter 3
Usage
Commit: This command requires a commit.
Cluster Management: This command is restricted to cluster mode.
Note
The passwd command is a special case because it needs to be usable by guest users who can only ever
be in machine mode. If a guest user issues the passwd command on a machine in a cluster, it will not
print the warning message but will instead just silently operate on the cluster level data without changing
the user's mode. All other users will get the above written behavior (consistent with the other restricted
configuration commands).
Batch Command: This command does not support a batch format.
Example
mail3.example.com> password
last
Description
The last command displays who has recently logged into the system. By default, it shows all users who
have logged into the system
Usage
Commit: This command does not require a commit.
Cluster Management: This command is restricted to machine mode.
Batch Command: This command does not support a batch format.
Example
elroy.run> last
Username
========
admin
admin
admin
admin
admin
admin
admin
Remote Host
=============
10.251.23.186
10.251.23.186
10.251.16.231
10.251.23.186
10.251.23.142
10.251.23.142
10.251.23.142
Login Time
================
Thu Sep 01 09:14
Wed Aug 31 14:00
Wed Aug 31 13:36
Wed Aug 31 13:34
Wed Aug 31 11:26
Wed Aug 31 11:05
Wed Aug 31 10:52
Logout Time
================
still logged in
Wed Aug 31 14:01
Wed Aug 31 13:37
Wed Aug 31 13:35
Wed Aug 31 11:38
Wed Aug 31 11:09
Wed Aug 31 10:53
Total Time
==========
1h 5m
1m
0m
0m
11m
4m
1m
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-291
Chapter 3
User Management
admin
admin
shutdown
10.251.60.37
10.251.16.231
32m
11m
who
Description
The who command lists all users who are logged into the system via the CLI, the time of login, the idle
time, and the remote host from which the user is logged in.
Usage
Commit: This command does not require a commit.
Cluster Management: This command is restricted to machine mode. It is further restricted to the login
host (i.e., the specific machine you are logged onto). This command requires access to the local file
system.
Batch Command: This command does not support a batch format.
Example
mail3.example.com> who
Username
========
admin
Login Time
==========
03:27PM
Idle Time
=========
0s
Remote Host
===========
10.1.3.201
What
====
cli
whoami
Description
The whoami command displays the username and full name of the user currently logged in, and which
groups the user belongs to.
Usage
Commit: This command requires a commit.
Cluster Management: This command can be used in all three machine modes (cluster, group, machine).
Batch Command: This command does not support a batch format.
Example
mail3.example.com> whoami
Username: admin
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-292
Chapter 3
loadlicense
showlicense
loadlicense
Description
Loads an XML license for a virtual appliance. You can load from a file or copy and paste. For complete
information, see the Cisco Content Security Virtual Appliance Installation Guide available from
http://www.cisco.com/c/en/us/support/security/email-security-appliance/products-installation-guides-li
st.html.
This command is available to users with Admin or Operator privileges.
Usage
Commit: This command does not require a commit.
Cluster Management: This command is restricted to machine mode. It is further restricted to the login
host (i.e., the specific machine you are logged onto).
Batch Command: This command does not support a batch format.
Example
mail.example.com> loadlicense
1 Paste via CLI
2 Load from file
How would you like to load a license file?
[1]> 2
Enter the name of the file in /configurations to import:
[]> <filename>
TERMS AND CONDITIONS OF USE
<Terms and conditions>
Do you accept the above license agreement?
[]> y
The license agreement was accepted.
The following feature key have been added:
<feature keys>
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-293
Chapter 3
showlicense
Description
Displays information about the current virtual appliance license. Additional details are available using
the featurekey command.
This command is available to users with Admin or Operator privileges.
Usage
Commit: This command does not require a commit.
Cluster Management: This command is restricted to machine mode. It is further restricted to the login
host (i.e., the specific machine you are logged onto).
Batch Command: This command supports a batch format.
Batch Format
The syntax of this command is: showlicense
Example
mail.example.com> showlicense
company: Example Inc.
org: Widget Division
unit: Portland Data Center
seats: 1000
city: Portland
state: Oregon
country: US
email: [email protected]
begin_date: Tue Dec 6 17:45:19 2011
end_date: Mon Sep 1 17:45:19 2014
vln: ABC-123423123
serial: 1003385
CLI Reference Guide for AsyncOS 9.6 for Cisco Email Security Appliances
3-294