I have a SharePoint 2007 Server installation in Company A (domain A), we have merged with company B (domain B), there is a two-way trust between them. I have setup my people-picker to query both domains, and my SSP to import the user profiles from both domains. The email server is in domain A and alerts work fine for any email address of accounts in domain A, but SharePoint will not send any alerts to people picked from domain B. If I setup a user in domain A with an email address in domain B, it works! But I can't do that for the whole company (too many) Why wont SharePoint send any alerts to the accounts from domain B? Thanks Kevin

Could you please check the Domain B users in the user profile. Weather Domain B users are existing there or not. If not then you have to run stsadm -o migrateuser let me know if it worksCheers, Hemendra-MCTS

Domain B user profiles exist in the SSP/User Profiles and Properties/View User Profiles. Don't forget that I have all user profiles appear as Domain A\user ... Domain B\user, so to migrate users won't merge the profiles as they are, I believe, distinct profiles. Kev

This blog may help you http://social.technet.microsoft.com/Forums/en-US/sharepointadmin/thread/319d5b0e-336a-4815-9ee5-5d1685db867fCheers, Hemendra-MCTS

I've seen this article and his solution was to import the users from domain B into domain A and update the email addresses to point back to domain B, but this is not a viable solution for me as there are too many people in domain B; and there is the problem of keeping them in sync too. I have a potential solution to do with Exchange Receivers, in that I add a receiver that has my SharePoint servers as trusted sources to relay to the alternate domain. At the moment this is with my Exchange man and I'm waiting for him to get back to me. Of course the ideal solution is to have a single Exchange server with both domain accounts integrated, but that is a little way down the road. Kev

I have found the solution; I needed to create a Receive Connector on the Exchange server to allow relaying to "effectively" an external address. But, and this is what all the other blogs DIDN'T mention, the connector needs to be setup to use IPSec as this is what SharePoint wants when sending externally. I listed my SharePoint servers in the connector, so that any of them can email, but found out that it's almost random which server in the farm is running the timer jobs and therefore sending emails. This is held in a table in the Content DB called [TimerLock] Kev