PDF(39.5 KB) View with Adobe Reader on a variety of devices
ePub(85.4 KB) View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
Mobi (Kindle)(71.2 KB) View on Kindle device or Kindle app on multiple devices
Updated:May 20, 2020
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.
This document describes how to use Lightweight Directory Access Protocol (LDAP) accept or routing queries on the Cisco Email Security Appliance (ESA)/Cloud Email Security (CES) when email addresses contain separator characters.
How to Configure LDAP Accept or Routing Queries to Function when Email Addresses contain Separators?
In order to achieve this, use CLI and issue the command sievechar to activate the Sieve Email Filtering feature.
Note: Allowable characters are: - _ = + / ^ #
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. >
This feature allows LDAP Accept/Routing queries to ignore the details that follow the defined separator on the ESA/CES.
An example of this feature is when an email contains the recipient address of firstname.lastname@example.org arrives into the ESA/CES where LDAP accept is configured, the LDAP accept query in question would send the query for email@example.com and ignoring the +technicalsupport as per the sievechar setting to the LDAP server for validation.