Hello, Did the exchange developers remove that actual code that used LDAP for filtering. I don't need a GUI to construct a Filter. I can do that myself. What I would like to know is if I build a filter and put it into the appropriate attribute within an addresspolicy object in the Exchange configuration container in AD if it will work. What ever possesed the exchange team to use OPATH to begin with is beyond me. It is next to usless for a complex organization. You have limited the ability to build dynamic distribtuion groups, address lists, and addressing policy. Thanks

Just learn OPATH and get used to it. Like you, I don't see anything wrong with LDAP, but that ship has sailed.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

On Thu, 7 Apr 2011 22:41:05 +0000, Ed Crowley [MVP] wrote: >Just learn OPATH and get used to it. Like you, I don't see anything wrong with LDAP, but that ship has sailed. Learning it and using it aren't a problem, but using OPATH with properties that the developers didn't think of (or didn't think anyone would use) *is* a problem -- especially if those properties are custom schema extensions. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

"LDAP syntax filters are supported in Exchange 2007 and will exist only on objects that have been migrated from Exchange 2003 or earlier. " Upgrading Custom LDAP Filters to OPATH Filters http://technet.microsoft.com/en-us/library/cc164375(EXCHG.80).aspx Frank Wang TechNet Subscriber Support in forum If you have any feedback on our support, please contact tngfb@microsoft.com Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.