So, how is your customer feedback regarding this "feature"? We have many legacy filters relying on things like custom attributes, and even simple attributes like "St" (State) and these simply CANNOT be converted to OPATH because they don't work.

While it's annoying enough to be forced to populate our custom attributes into the Exchange-provided custom attributes, it is absolutely mind-boggling that "st" is not supported. Does no-one create geographically-based distribution lists?

Luckily we still have an Exchange 2003 server in the org.

Awesome Post! Thank you!

Do we need to warn the end users about this update? Meaning is there a change to the Outlook client that we should warn them about?

Thank you