Exempt IP Addresses/Domains/Email Addresses from the ESA Bounce Configuration

Available Languages

Download Options

PDF (149.4 KB)
View with Adobe Reader on a variety of devices
ePub (211.3 KB)
View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
Mobi (Kindle) (183.7 KB)
View on Kindle device or Kindle app on multiple devices

Updated:October 14, 2014

Document ID:118502

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Table of Contents
          Introduction
          Exempt IP Addresses/Domains/Email Addresses from the ESA Bounce Configuration
          Outbound Mail
          Inbound Mail
          Related Information

Introduction

This document describes how to configure inbound and outbound mail to exempt IP addresses, domains, or email addresses for the Cisco Email Security Appliance (ESA).

Exempt IP Addresses/Domains/Email Addresses from the ESA Bounce Configuration

You can specify recipient domains on which to disable Bounce Verification when the ESA delivers to those domains. You will need to configure both outbound and inbound mail.

Outbound Mail

Go to Mail Policies > Destination Controls.
Select "Add destination...".
Call the new destination "example.com".
In the settings, set "Bounce Verification" to No.
Submit and Commit changes.

118502-technote-esa-01

Note: For outbound mail, you can only refer to the destination domain and not an IP address or email address.

Inbound Mail

From Mail Policies > Mail Flow Policies, use an exisiting Mail Flow Policy or create a new Mail Flow Policy, and set the Bounce Verification/"Consider Untagged Bounces to be valid" to Yes.
From Mail Policies > Hat Overview, add the domain to a Sender Group that uses the modified or created Mail Flow Policy.

118502-technote-esa-02