Cisco Cisco Email Security Appliance C170 Guia Do Utilizador

On the Mail Policies > Bounce Verification page, click New Key.

Enter a text string and click Submit.

Commit your changes.

You can purge your old address tagging keys by selecting a rule for purging from the pull-down menu 
and clicking Purge.

The bounce verification settings determine which action to take when an invalid bounce is received. 

Choose Mail Policies > Bounce Verification.

Click Edit Settings. 

Select whether to reject invalid bounces, or to add a custom header to the message. If you want to add a 
header, enter the header name and value.

Optionally, enable smart exceptions. This setting allows incoming mail messages, and bounce messages 
generated by internal mail servers, to be automatically exempted from bounce verification processing 
(even when a single listener is used for both incoming and outgoing mail).

Submit and commit your changes.

You can use the 

bvconfig

 and 

destconfig

 commands in the CLI to configure bounce verification. These 

commands are discussed in the Cisco AsyncOS CLI Reference Guide.

Bounce verification works in a cluster configuration as long as both Cisco appliances use the same 
"bounce key." When you use the same key, either systems should be able to accept a legitimate bounce 
back. The modified header tag/key is not specific to each Cisco appliance. 

The 

deliveryconfig

 command sets parameters to be used when delivering email from the Cisco 

appliance.