Cisco Cisco Email Security Appliance X1070 Guida Utente
26-71
User Guide for AsyncOS 10.0 for Cisco Email Security Appliances
Chapter 26 Configuring Routing and Delivery Features
Using Global Unsubscribe
Exporting and Importing a Global Unsubscribe File
Like the HAT, the RAT,
smtproutes
, static masquerading tables, alias tables, domain map tables, and
altsrchost
entries, you can modify global unsubscribe entries by exporting and importing a file.
Procedure
Step 1
Use the
export
subcommand of the
unsubscribe
command to export the existing entries to a file
(whose name you specify).
Step 2
Outside of the CLI, get the file. (See
for more information.)
Step 3
With a text editor, create new entries in the file.
Separate entries in the file by new lines. Return representations from all standard operating systems are
acceptable (<CR>, <LF>, or <CR><LF>). Comment lines start with a number sign (
acceptable (<CR>, <LF>, or <CR><LF>). Comment lines start with a number sign (
#
) and are ignored.
For example, the following file excludes a single recipient email address (
test@example.com
), all
recipients at a particular domain (
@testdomain.com
), all users with the same name at multiple domains
(
testuser@
), and any recipients at a specific IP address (
11.12.13.14
).
Step 4
Save the file and place it in the configuration directory for the interface so that it can be imported. (See
for more information.)
Step 5
Use the
import
subcommand of
unsubscribe
to import the edited file.
[]>
mail3.example.com> commit
Please enter some comments describing your changes:
[]> Added username “user@example.net” to global unsubscribe
Do you want to save the current configuration for rollback? [Y]> n
Changes committed: Fri May 23 11:42:12 2014 GMT
# this is an example of the global_unsubscribe.txt file
test@example.com
@testdomain.com
testuser@
11.12.13.14