The owner of my company has set up another company and during the start up, we were hosting their email. Over the weekend, I have moved them over to their own Hosted Exchange Server in order to seperate everything.
Originally they wanted to have the users remain in our GAL so I created a contact to forward their mail. Some users started getting rejections and I have been asked to just delete these users all together.
So, the problem is that I am getting the following rejection:
In the event viewer, I am receiving the following:
I had verified that the contact and users did not share the same email address, so I'm not sure how this happened.
Anyway, I have since deleted all the users and contacts to make sure there are no duplications.
I did all of this today, so it is just a matter of time of Exchange/AD updating until I can send DomainB.
Originally they wanted to have the users remain in our GAL so I created a contact to forward their mail. Some users started getting rejections and I have been asked to just delete these users all together.
So, the problem is that I am getting the following rejection:
Code:
User on 6/1/2009 11:43 AM
A configuration error in the e-mail system caused the message to bounce between two servers or to be forwarded between two recipients. Contact your administrator.
<mail.mydomain.com #5.4.6>
In the event viewer, I am receiving the following:
Code:
Cause: A forward loop was detected by the categorizer. This is a common hosting configuration problem caused when someone uses the provisioning tool to create a contact in one organization unit and creates a user in a different organization user that share the same e-mail address.
Solution: Verify that you do not have a user in organizational unit and a contact in a different organizational unit that have the same e-mail address.
I had verified that the contact and users did not share the same email address, so I'm not sure how this happened.
Anyway, I have since deleted all the users and contacts to make sure there are no duplications.
I did all of this today, so it is just a matter of time of Exchange/AD updating until I can send DomainB.