When users/contacts are created by SharePoint they are in the format of alias<at>mysharepointserver.mydomain.com I want them to have the address of alias<at>mydomain.com added via a recipient policy...but have not had any luck.Can you give me an example of a policy that will get the above done?I have tried several different things and have been unsuccessful.If I create a filter rule, and run it, I get the contacts listed that I want.The E-Mail Addresses (Policy) is exactly the same as my default policy (which is what I want, i.e. alias<at>mydomain.com - at least I think).Recipient Update Service is set to run continuously. The new policy was created several weeks ago and should have worked by now if it was going to.But, my contacts e-mail address are still only set as alias<at>mysharepointserver.mydomain.com There has been no alias<at>mydomain.com e-mail address added in AD/Exchange for the Contact.Environment:WSS3Exchange 2003Any help is appreciated.Thanks, Ray

Is " Automatically update e-mail addresses based on e-mail address policy" checked for those accounts?

Yes.

Well, the default policy should have stamped those objects ( i.e. no need to create a new RUS), assuming that Sharepoint correctly creates them. ( do they show up in the GAL at all?)You may want to ask this in the Sharepoint forum as well:http://social.technet.microsoft.com/Forums/en-US/category/sharepoint/

They do show up in the GAL.I already tried the SharePoint forums, they sent me here.....Something to keep in mind is that SharePoint creates "Contacts" not "Users" in AD.Would that have anything to do with it?

It should update any valid mail-enabled object.Have you gone through the troubleshooting steps for RUS?http://support.microsoft.com/kb/822794http://msexchangeteam.com/archive/2004/07/15/184356.aspxI would also make sure that the OU you are creating the object in has security inheritance enabled. ( YOu could also run ExBPA and do a permissions and health check on the Exchange Server)I dont know if there is something unique to those objects that Sharepoint creates or not. ( You dont want to change the default email address do you? Otherwise how will the mail be delivered to the sharepoint server - You want to just add an additional email address correct? In that case, an additional RUS would make sense)

I just noticed that I am getting the following in the Application Event Log with I try to "Apply this policy now..." for the default policy.Event Type: ErrorEvent Source: MSExchangeISEvent Category: General Event ID: 9667Date: 1/14/2010Time: 4:40:57 PMUser: N/AComputer: MAILSERVERNAMEDescription:Failed to create a new named property for database "First Storage Group\Mailbox Store (MAILSERVERNAME)" because the number of named properties reached the quota limit (8192). User attempting to create the named property: "username" Named property GUID: 00020386-0000-0000-c000-000000000046 Named property name/id: "X-Sharing-WSSBaseUrl" I'll investigate and see if this has anything to do with my isses. If you have knowledge about this error, any guidance is appreciated.I confirmed that the OU has Security Inheritance enabled, so that shouldn't be the issue.I do not want to change the default address, just create a valid FQDN for external users to e-mail to (our sharepoint server is not open to the public using the actual machine name).

Looks like that error is related to Message Headers, which shouldn't impact the addition of a smtp e-mail address to a contact.

Correct. but it is a a xheader that sharepoint uses in its alerts. As for Event 9667, it should be addressed:http://technet.microsoft.com/en-us/library/bb851495(EXCHG.80).aspxIf you create a mail-enabled contact via ADUC instead of Sharepoint using the same naming and email scheme and in the same OU that the Sharepoint contacts are created in, does it get stamped correctly?

On Thu, 14-Jan-10 18:17:56 GMT, rchamberland wrote:>When users/contacts are created by SharePoint they are in the format of alias<at>mysharepointserver.mydomain.com I want them to have the address of alias<at>mydomain.com added via a recipient policy...but have not had any luck.Can you give me an example of a policy that will get the above done?I have tried several different things and have been unsuccessful.If I create a filter rule, and run it, I get the contacts listed that I want.The E-Mail Addresses (Policy) is exactly the same as my default policy (which is what I want, i.e. alias<at>mydomain.com - at least I think).Recipient Update Service is set to run continuously. The new policy was created several weeks ago and should have worked by now if it was going to.But, my contacts e-mail address are still only set as alias<at>mysharepointserver.mydomain.com There has been no alias<at>mydomain.com e-mail address added in AD/Exchange for the Contact.Environment:WSS3Exchange 2003Any help is appreciated.Thanks, Ray If the contacts are created in the AD with a SMTP address the RUSisn't going to generate any other addresses on the contact. Whateveris creating the contacts needs to assign the correct addresses.Contact are funny things. You really don't want a primary SMTP proxyaddress in your email domains on them. In fact, you probably don'twant a secondary SMTP proxy address in your domain on them, either --unless you intend to have them sent email from outside yourorganization.Sharepoint should be creating the Contact with the primary SMTP proxyaddress, the "mail" attribute, and the "targetAddress" properties allthe same. If you apply a recipient policy to a contact, the primarySMTP proxy address in the policy will NOT replace the existing one,it'll just add the new address as a secondary SMTP proxy address. Thisbehavior is different to the way policies are applied to other mail-and mailbox-enabled objects.---Rich MatheisenMCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

I do want external (non-domain) users to be able to send to e-mail enabled lists.I want it to be a secondary address, not the primary.Sharepoint creates the address with the SharePoint server name as the subdomain so the mail can be routed correctly.According to their (Sharepoint) documentation if you want to add another address to the contact you have to create a Recipient Policy to do so.The following link goes to a widely used document for setting up SharePoint for use with Exchange 2003 - http://www.combined-knowledge.com/Downloads/2007/How%20to%20configure%20Email%20Enabled%20Lists%20in%20Moss2007%20RTM%20using%20Exchange%202003.pdfBasically, this is all it says "Create a new Exchange Server Global recipient policy so that all contacts created in that OU Automatically get the second mail address added."Helpful, isn't it?All contacts created by SharePoint are in a OU dedicated for that purpose.From a TechNet article located here (at the bottom of the page) - http://technet.microsoft.com/en-us/library/cc287879.aspx"Alternatively, the Exchange Server can be configured by adding a new Exchange Server Global recipient policy to automatically add external addresses that use the second-level domain name and not the subdomain or host for Windows SharePoint Services 3.0. For more information about how to manage Exchange Server, see the Help documentation for Exchange Server. "Any thoughts are appreciated.

Andy,When you manually create a Contact in AD, you have to manually specify the e-mail address. It is not auto-generated and therefore it does not get "my" desired address of TestAccount<at>mydomain.com, unless that is what I put in the field.Same thing is going on with SP creating the contact. It creates it with the WSS/MOSS server name as the subdomain in the format TestAccount<at>wss.mydomain.com, and RUS doesn't appear to stamp it.So I guess the question is, how do you get RUS to stamp an AD Contact? Or can you?

On Fri, 15-Jan-10 16:30:14 GMT, rchamberland wrote:>I do want external (non-domain) users to be able to send to e-mail enabled lists.I want it to be a secondary address, not the primary.Sharepoint creates the address with the SharePoint server name as the subdomain so the mail can be routed correctly.According to their (Sharepoint) documentation if you want to add another address to the contact you have to create a Recipient Policy to do so.The following link goes to a widely used document for setting up SharePoint for use with Exchange 2003 - http://www.combined-knowledge.com/Downloads/2007/How%20to%20configure%20Email%20Enabled%20Lists%20in%20Moss2007%20RTM%20using%20Exchange%202003.pdfBasically, this is all it says "Create a new Exchange Server Global recipient policy so that all contacts created in that OU Automatically get the second mail address added."Helpful, isn't it?All contacts created by SharePoint are in a OU dedicated for that purpose.From a TechNet article located here (at the bottom of the page) ->http://technet.microsoft.com/en-us/library/cc287879.aspx"Alternatively, the Exchange Server can be configured by adding a new Exchange Server Global recipient policy to automatically add external addresses that use the second-level domain name and not the subdomain or host for Windows SharePoint Services 3.0. For more information about how to manage Exchange Server, see the Help documentation for Exchange Server. "Any thoughts are appreciated. When you create a mail-enabled Contact using the ADUC does it have theaddresses you think it should, based on the data in the appropriateRecipient Policy? Or does it have only the targetAddress you gave whenyou created the object?---Rich MatheisenMCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

On Fri, 15-Jan-10 16:30:14 GMT, rchamberland wrote:>I do want external (non-domain) users to be able to send to e-mail enabled lists.I want it to be a secondary address, not the primary.Sharepoint creates the address with the SharePoint server name as the subdomain so the mail can be routed correctly.According to their (Sharepoint) documentation if you want to add another address to the contact you have to create a Recipient Policy to do so.The following link goes to a widely used document for setting up SharePoint for use with Exchange 2003 - http://www.combined-knowledge.com/Downloads/2007/How%20to%20configure%20Email%20Enabled%20Lists%20in%20Moss2007%20RTM%20using%20Exchange%202003.pdfBasically, this is all it says "Create a new Exchange Server Global recipient policy so that all contacts created in that OU Automatically get the second mail address added."Helpful, isn't it?All contacts created by SharePoint are in a OU dedicated for that purpose.From a TechNet article located here (at the bottom of the page) ->http://technet.microsoft.com/en-us/library/cc287879.aspx"Alternatively, the Exchange Server can be configured by adding a new Exchange Server Global recipient policy to automatically add external addresses that use the second-level domain name and not the subdomain or host for Windows SharePoint Services 3.0. For more information about how to manage Exchange Server, see the Help documentation for Exchange Server. "Any thoughts are appreciated. When you create a mail-enabled Contact using the ADUC does it have theaddresses you think it should, based on the data in the appropriateRecipient Policy? Or does it have only the targetAddress you gave whenyou created the object?---Rich MatheisenMCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP Yep!

Rich,If I create a Contact using ADUC, it only has the target address that I gave it when I created it.Ex. TestSharePointContact<at>moss2007.mydomain.comI would expect that the Recipient Policy would create a SMTP Address of TestSharePointContact<at>mydomain.com (policy is set for alias<at>mydomain.com).FYI, a X400 address is created.I even created a test contact using a domain that I personally own as the e-mail address to test and see if the Recipient Policy/RUS would work differently. It did not.There is nothing special about the OU that I am creating these object in vs. other OU's, except that the MOSS2007/WSS user has special permissions to create contacts (whereas it doesn't on other OU's). Otherwise the permissions are the same.Thanks,Ray

On Tue, 19-Jan-10 15:57:50 GMT, rchamberland wrote:>Rich,If I create a Contact using ADUC, it only has the target address that I gave it when I created it.Which is what I said you'd see.>Ex. TestSharePointContact<at>moss2007.mydomain.comI would expect that the Recipient Policy would create a SMTP Address of TestSharePointContact<at>mydomain.com (policy is set for alias<at>mydomain.com).This is one of the reasons why we're glad to see the Reciient UpdateService go away. It's not applying the policy properly.Exchange 2007 will apply the policy correctly, assuming you use theExchange Powershell cmdlets. If you just plunk a Contact into the ADthere won't be any RUS to stamp the object with the necessaryattributes and permissions, so the Contact won't work.>FYI, a X400 address is created.I even created a test contact using a domain that I personally own as the e-mail address to test and see if the Recipient Policy/RUS would work differently. It did not.There is nothing special about the OU that I am creating these object in vs. other OU's, except that the MOSS2007/WSS user has special permissions to create contacts (whereas it doesn't on other OU's). Otherwise the permissions are the same.Thanks,Ray Don't do this ==> If you applied the Recipient Policy that dealssolely with Contacts, the address you expect to see will be created.I said don't apply a policy becasue I don't know what your policieslook like. Applying the wrong one can have, ummm, interestingconsequences. :-)The RUS in E2K3 doesn't apply policies in the way you expect them tobe applied. It hasn't done so forever.---Rich MatheisenMCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP