ShackDaddy
MIS
I've come in to a partially complete coexistence setup in which an E2007 server has been added to an existing E2003 organization that has a FE/BE arrangement. The intention is to migrate all mailboxes to the new server, once we've tested difference scenarios and know that things are working properly, and then sunset the old server.
Right now the only problem we are having is delivering mail from the outside to a mailbox on the E2007 server. That mail is being received by an E2003 FE server and then it doesn't land anywhere, but an event 3005 is generated, which refers to a routing loop.
Mail originating from an E2003 mailbox is delivered to the E2007 server, and the E2007 server's mailboxes can send email outbound directly to the internet and also to mailboxes on the E2003 server.
I'm tempted to have the E2007 server start handling inbound public mail, but I'd like to resolve this issue on the routing level.
The routing groups were automatically generated when the new server was added to the org, but they reference routing only between the E2003 BE server and the E2007 server, and not between the E2003 FE server:
---- ------------------ ------------------
EXCHANGE7-EXCHANGE Exchange Routing Group ... First Routing Group
EXCHANGE-EXCHANGE7 First Routing Group Exchange Routing Group
Could that be the issue? Do I need to create a separate group between the E2003 FE and the E2007 server? I had been thinking that the FE/BE were treated as a single unit as far as routing went.
Happy for any ideas.
Dave Shackelford
Shackelford Consulting
Right now the only problem we are having is delivering mail from the outside to a mailbox on the E2007 server. That mail is being received by an E2003 FE server and then it doesn't land anywhere, but an event 3005 is generated, which refers to a routing loop.
Mail originating from an E2003 mailbox is delivered to the E2007 server, and the E2007 server's mailboxes can send email outbound directly to the internet and also to mailboxes on the E2003 server.
I'm tempted to have the E2007 server start handling inbound public mail, but I'd like to resolve this issue on the routing level.
The routing groups were automatically generated when the new server was added to the org, but they reference routing only between the E2003 BE server and the E2007 server, and not between the E2003 FE server:
---- ------------------ ------------------
EXCHANGE7-EXCHANGE Exchange Routing Group ... First Routing Group
EXCHANGE-EXCHANGE7 First Routing Group Exchange Routing Group
Could that be the issue? Do I need to create a separate group between the E2003 FE and the E2007 server? I had been thinking that the FE/BE were treated as a single unit as far as routing went.
Happy for any ideas.
Dave Shackelford
Shackelford Consulting