Do I really need to upgrade my filters?

After posting the Exchange 2007 OPATH intro and How to Upgrade the Filters posts to EHLO over the past few days, one question that's come up enough to warrant another blog post is "Do I really need to upgrade my filters".

And the answer is pretty straight forward: maybe.

Ok, that's not fair. Let me explain...

If you want to update your existing legacy-version LDAP filter to have some new criteria, and you want to manage it from Exchange 2007 -- you'll need to upgrade the filter.

If you want to update your existing legacy-version LDAP filter to have the same criteria, but you want to start managing it from Exchange 2007 -- you'll need to upgrade the filter.

So what does that leave? Well, if you're perfectly content with the function of your current filter and you have no need to manage it from Exchange 2007 -- you don't need to upgrade the filter!

That's pretty key, as it probably describes a large number of the custom filters in use out there today. My advice: Save yourself the effort of doing the upgrade and just let it keep working as-is until you NEED to upgrade it...

Also, keep in mind that in most cases there's not a significant incentive to actually upgrade your existing filters. It's probably easier and less disruptive to create a new address list or email address policy from Exchange 2007 that has your desired filter (ideally a "precanned" filter created by GUI) and then decommission the old AL or EAP it replaces.

Comments (9)

  1. Anonymous says:

    After some time off-the-air, "Weekend reading" is back, and this time is really BIG! Exchange Server

  2. Anonymous says:

    In the Do I Really Need to Upgrade my Filters blog post, Several folks posted a question/comment asking

  3. David – we’re working on putting together a formatted list of the attribute mappings. Should be out not too long in the future, I think.

    What’s the LDAP filter you used to use for this AL query in Exchange 2003?


  4. Anonymous says:

    Since I’ve posted a number of times about OPATH filters for Exchange 2007 and RecipientFilter parameter

  5. David – unfortunately the MemberOf property is not exposed on the recipient objects nor is it filterable. Thanks for bringing this to my attention. I’ll have a look to see what can be done about this.

  6. David/Johan, et al – Whoops, I goofed! MemberOf *IS* exposed for use by recipient filter… it’s just called MemberOfGroup instead.

    [PS] D:>$groupidentity = $(Get-DistributionGroup testgroup).Identity.DistinguishedName

    [PS] D:>$groupidentity


    [PS] D:>Set-EmailAddressPolicy testpolicy -recipientfilter "memberofgroup -eq ‘$groupidentity’"

    [PS] D:>Get-EmailAddressPolicy testpolicy

    Name                                    Priority                                RecipientFilter

    —-                                    ——–                                —————

    testpolicy                              1                                       MemberOfGroup -eq ‘’

  7. Evan,

    Your recent posts about AL/EAPs and the OPATH syntax in Exchange 2007 (Powershell) are great.

    I am comfortable with the OPATH syntax for RecipientFilter, however I would like to have a list of all the attributes that I can use in an OPATH query.  I can’t find a list anywhere.

    In particular, I want to create an AL which is based on the members of an AD group.  This used to be easy with an LDAP query in Exchange 2003, but I can’t work out how to do it in Exchange 2007.



  8. I don’t have the LDAP filter handy, but it just filters for mailbox users and if the MemberOf attribue has CN=groupname,OU=OUname,DC=blah,DC=com etc.

    I’ve tried using RecipientFilter and assuming the attribute name is "MemberOf" but it doesn’t seem to work.

  9. Johan Lysen says:

    Hi Evand

    Pls expose the memberOf prop so we can use it in recipient filters

    /Johan Lysén, Sweden

Skip to main content