I have an ironport implementation that requires mail routing based on ldap attribute employeeid. the thought is to have ironport route messages when employeeid attribute is populated with a value to alt-mailhost. if the value is null, use normal routing.
I am thinking of using the following query:
then use message filters to make use of the ldap routing to alt-mailhost.
Question: is wildcard value (*) allowable to search for non null attributes?
If logic above is not an option, any recommendation on how to implement the requirement?
Table of ContentsIntroductionVersion HistoryPossible Future
UpdatesDocuments PurposeNAT Operation in ASA 8.3+ SectionsRule Types
Network Object NATTwice NAT / Manual NATRule Types used per SectionNAT
Types used with Twice NAT / Manual NAT and Network Obje...
Table of Contents Introduction:This document describes details on how
NAT-T works. Background: ESP encrypts all critical information,
encapsulating the entire inner TCP/UDP datagram within an ESP header.
ESP is an IP protocol in the same sense that TCP an...