|
OwensZilla -> Mail Enabled Objects Forwarding Errors (25.Jan.2008 12:28:42 AM)
|
Environment:
Source: Exchange 2003
Target: Exchange 2007 SP1
Quest Migration Manager 8.0
Microsoft Transporter Suite (used for coexistence between Exchange 2007 and Notes)
Issue:
Mail forwarding fails because the mail enabled objects in target created by Quest for coexistence between source and target have the same SMTP address in the target attribute and secondary
Details:
The primary STMP address for mail enabled object is first.last@exchange.target.com
The target address for mail enabled object is first.last@service.source.com
Quest adds a secondary SMTP address of first.last@service.source.com
When a mailbox enabled user in source chooses a mail enabled user in the gal it reads the primary STMP, then see the target SMTP and send it to first.last@service.source.com For some reason it does not get our SMTP connector when that entry is there, instead it sees the first.last@service.source.com in the secondary SMTP address and gets caught in a loop.
When we remove the first.last@service.source.com from the secondary SMTP address of the mail enabled users’ mail forwards to target as it should. Unfortunately, Quest re-stamps the secondary each time the target mail agent runs. We found that it does this on its own, even if you have stopped the mail agents. So, once it has been removed a short while later it show up again and mail forwarding fails.
Possible Causes:
One theory is if the SMTP connector is authoritative for the source.com it would then keep the mail internal. However, I am at a loss to figure out why mail would forward once the secondary SMTP is removed.
Any opinion would be greatly welcomed!
|
|
|
|