12-02-2013 01:17 PM
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:
(&(employeeid=*)(proxyAddresses=smtp:{a}))
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?
Any input is appreciated.
Thank you
Fadi
10-16-2014 06:08 AM
Hi fashour,
have you been able to find a solution?
02-03-2015 08:01 AM
I made couple of tests in my lab and it seems the wildcard is working.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: