I got this from a customer today regarding contacts in the exchange module (domain.com is replacing customer domain and contactdomain.com is replacing the contact domain)
"
Hi Jeremy, I am getting calls because exchange is (apparently) creating addresses @domain.com for all of our contacts. Thus, when people go to send an email to someone that is in the GAL they are seeing what appears to be a bad email address.
Example: administrator@contactdomain.com pulls up administrator@domain.com, and messages to administrator@domain.com go to the mail contact. We cannot have this because we may need that email address at domain.com as a legitimate one, and don't want internal mail going to our contacts!
"
This was a change a while back to remove the guid string from the contacts because it was an eyesore to some. But it didn't cause erroneous mail routing issues and addressing conflicts.
I've resorted to rewriting the contacts on the back end for this customer, it is not a good solution but at least its a work around.
Contacts are created that way due to segregation.
the GUID that was fixed in the past wasn't an eye sore to some but also made some features impossible to work with (unable to identify which contact is who) to which this was addressed.
I'm not really sure what an alternative would be compared to @domain.com
at most i could imagine something like (user)-contact@domain.com but i am not sure if that sorts the issue in general.
The guid was a unique identifier and not likely to collide with a common user name, say jsmith, croberts or jdoe if you will. Its really that a lot of people use common conventions for email addresses (first initial, last name for example).
(user)-contact@domain.com may be a reasonable solution. I would be interested in hearing other alternatives if anyone had any.
