We have an Exchange 2003 server sp2 on a server2003 box. We use policies to apply the primary SMTP address for each user. Last week i created a policy, say uhoh.com, specified SMTP g%.s%@uhoh.com, set (objectCategory=user)(company=uhoh*) and clicked apply. This policy was the lowest priority policy. For some reason, it applied this policy to people that did NOT have uhoh in their company field. As a matter of fact, near as i can tell the people it applied to have either nothing in their company field, or a company that didn't have a rule applied to it. Any idea why it happened?

Hi, Base on my research, you can configure a filter rule that specifies the subset of messaging-enabled objects to which the recipient policy applies. When we create and associate address lists and recipient policies with specific accounts, based on specific criteria by using a filter that is based on group membership or that is based on attributes that the Recipient Update Service is responsible for, the behavior of the address list or of the recipient policy may be inconsistent. We may avoid to use company attribute. This is a known issue. Workaround for this issue can be found from kb304516 The address list or the recipient policy filter is not applied when it is based on group membership or an attribute that the Recipient Update Service is responsible for http://support.microsoft.com/kb/304516/en-us Hope it helps. Xiu

The workaround in the article you are mentioning is exactly what we are doing .We use the company field to apply the policy. We don't use group memberships or any other attributes. That's the problem. Somehow the policy applied to people that did NOT have "uhoh" in the company field.