Our organization has two sites: Boston and London. I just setup a 2K7 server in Boston. Initially, it could only send mail to local mailboxes. Then I added the following route: New-RoutingGroupConnector -Name "us-dc-ex-01 Connection" -SourceTransportServers "us-ex2k7-01" -TargetTransportServers "us-dc-ex-01" -Cost 1 -BiDirectional $true -PublicFolderReferralsEnabled $true After that, the 2K7 server could send to all US mailboxes and the public Internet (via theus-dc-ex-01 server). But messages destined for the UK Site/server remain queued: quote:Identity: us-ex2k7-01\Unreachable\752 Subject: 130 Internet Message ID: <C2837FCDF028724AA9005B9907157BA421A3EB91@us-ex2k7-01.XXX.com> From Address: testme@XXX.com Status: Ready Size (KB): 3 Message Source Name: FromLocal Source IP: 255.255.255.255 SCL: -1 Date Received: 11/1/2007 1:30:21 PM Expiration Time: 11/3/2007 1:30:21 PM Last Error: There is currently no route to the mailbox database Queue ID: us-ex2k7-01\Unreachable Recipients: joeuk@XXX.comNot really sure what do from here. Do I need another route? Send connector? thanks

Do you have a RGC from EK3 to EK7

There wasn't a RGC between London and the 2K7 server. I just created one: Name SourceRoutingGroup TargetRoutingGroup---- ------------------ ------------------us-dc-ex-01 Connection Exchange Routing Group ... Bostonus-dc-ex-01 ConnectionBoston Exchange Routing Group ...UK Connection Exchange Routing Group ... LondonUK ConnectionLondon Exchange Routing Group ... Messages destined for London users are still be queued, though. Under send connectors I only have the connectors that were created under Exchange 2003

Fixed it. Added the 2K7 server to the Exchange Domin Servers group, added an Internal Connector pointing to the London server, and restarted the Exchange Transport service.

has AD replication been completed in order for all Exchange servers to pick up the new RGC?