Email Address Policies trouble
In Exchange 2003 you could create very detailed "Recipient Policies" (E-mail Address Policies) based on almost any attribute in Active Directory. I created a few policies (in 2003) that would stamp addresseson accounts based on which server theywere on. Now, in 2007 I have to define my scope of users based on "Recipient is in a State or Province", "Recipient is in a Department", "Recipient is in a Company" and Custom Attributes 1 through 15. Normally I wouldnt mind just letting the new policy cover everything, but when I did that it messed up Exchange 2003. So, in the meantime (and I probably shouldnt have done this) but I used an Exchange 2003 Recipient Policy to control what address is stamped on the user account (for those users on my Exchange 2007 server. Any help is appreciated...
August 1st, 2007 11:00pm

Honestly, I don't really have a good grasp of how to reproduce this functionality in E2K7, but it seems to be possible. The Exchange team wrote an article about OPATH receipient filtering recently. I have read this, but have yet to give it a try and see if it does what I expect. I'm terrible at explaining things I have not yet done for myself. Is this link any help? http://msexchangeteam.com/archive/2007/01/10/432143.aspx
Free Windows Admin Tool Kit Click here and download it now
August 2nd, 2007 1:30am

Thanks, this helps greatly. Also, I found an ldap to opath conversion to on the msexchangeteam website for those of you interested.
August 3rd, 2007 4:03pm

Translating old policies from LDAP to OPATH is not easy. Complicating the task is the fact that there are some Email Address Policies that you may haved used in Exchange 2003 (using LDAP)that you simply can't construct in Exchange 2007 (using OPATH). The biggest problem I've encountered is that OPATH only allows for wildcard matches on certain attributes. I don't know why that is, and I don't think I've ever seen a list of attributes that do/don't allow matching. But I do know that any attribute availableon all object types (users, groups, contacts, etc..) that contains the Active Directory domain name will, disappointingly, not allow for wildcard matching. About 5 months ago I posted this problem here: http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=1550848&SiteID=17 But I still haven't found any way to create an Email Address Policy that will allow you to assign email addresses to groups or contacts based on which Active Directory domain they're in. I don't proclaim to be an OPATH expert, so I'd love for someone to prove me wrong!
Free Windows Admin Tool Kit Click here and download it now
August 3rd, 2007 4:11pm

Unfortunately, you are right. OPATH is not easy to get a good handle on. I'm hoping that is why I don't have a good handle on it, at least. I suspect the sad truth is I'm just spacey. Maybe Microsoft will introduce a tool or web-based wizard that could help with this. Hello, anyone on the Exchange Team listening????
August 5th, 2007 5:42am

Since I have some of your attention... I am trying to write a policy where the primary smtp address (or Reply Address) is something other than the default "@localhost". When I created the policy I included the specific address in, but it never sets it as the default. Here is my OPATH... New-EmailAddressPolicy "MUXC09" -RecipientFilter {((ServerLegacyDN -eq '/O=College University/OU=COLLEGE/cn=Configuration/cn=Servers/cn=MUXC09') -and (RecipientType -eq 'UserMailbox'))} -EnabledPrimarySMTPAddressTemplate 'SMTP:%m@somecollege.edu' Everything works as it should except for the fact that the -EnabledPrimarySMTPAddressTemplate 'SMTP:%m@marshall.edu' doesnt show up as primary...the local shows as primary.
Free Windows Admin Tool Kit Click here and download it now
August 7th, 2007 5:48pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics