Cisco Bug: CSCuq22507 - Apply LDAP routing for bounced messages
Apr 24, 2017
- Cisco Email Security Appliance
Known Affected Releases
10.0.1-087 8.0.1-113 8.5.6-074
Symptom: Our ESAs support many internal mail systems. Some share the same sender email domain (jhu.edu) as well. The ESAs currently bypass LDAP routing whenever they generate a bounce to an internal sender. For example, consider the following message: Sender: senderA@jhu.edu (sent from Math department server which sends all outgoing mail to the ESAs) Recipient: firstname.lastname@example.org Conditions: When the ESA tries to deliver this message, it will bounce because email@example.com does not exist. The ESA will then attempt to send the bounced email to senderA@jhu.edu.. But when the ESA generates the bounce, it will bypass LDAP routing for senderA@jhu.edu and try to deliver to either the MX record or A record for jhu.edu, which in our environment will not work (no internal MX record jhu.edu and the A record is a web server). This a problem because the ESAs will not know how to properly route the bounce to senderA@jhu.edu. We cannot use an smtp route for jhu.edu because not all jhu.edu mail is hosted on the same mail system. We rely heavily on LDAP routing to get email to the proper mail server.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases