General discussion

Locked

REVISED:Exchange 5.5 IMS routing problem

By Steve Cody ·
More info here, please read original posting text that follows:
I have tried having the server that has been delivering the mail forward all mail for that subdomain.mydomain.com to the primary server. This causes a mail loop and those messages arenever delivered.
ORIGINAL MESSAGE BELOW
I have 2 Servers with Exchange 5.5(SP3). One is the primary mail server for our domain. I have some accounts on the primary server that have an alternate recipient. Those alternate recipients are set up as custom recipients to cause the mail to deliver to a subdomain for my company.
The mail should come into the primary server to those users and then be re-delivered right back out to the custom recipient. What's happening is they are coming to the primary server and then being sent to the other exchange server, through our WAN, and that server is actually delivering the message.
I can find no place where I have told it to deliver mail through the secondary system.

Any ideas? This is bothering me because I want to control which system delivers the subdomain's email.

If you need more information, just ask. I REALLY want to fix this problem soon.

Steve Cody
MCSE, CCNA, A+

This conversation is currently closed to new comments.

18 total posts (Page 1 of 2)   01 | 02   Next
| Thread display: Collapse - | Expand +

All Comments

Collapse -

REVISED:Exchange 5.5 IMS routing problem

by Steve Cody In reply to REVISED:Exchange 5.5 IMS ...

The users are not part of any local network that the exchange servers are on. Email comes into my mail server to their mailbox with an address of user@mydomain.com and is forwarded to a custom recipient with the address user@sub.mydomain.com. My primary exchange server is set to deliver mail for sub.mydomain.com using DNS. It is at this point that it sends it, for some reason, to another exchange server on my WAN and has it deliver the mail.

Each custom recipient was created on the primary server. They do not list a home server, only a home site. The Home "Server" for each user is also the primary server. Each user's NT account, for their real mailboxes is also created on the primary server. I have their mail forwarding to the Custom Recipient only.
I have one Exchange organization, and one Exchange site. The two servers are in this same site. Both have the IMS installed.

Collapse -

REVISED:Exchange 5.5 IMS routing problem

by burcjo In reply to REVISED:Exchange 5.5 IMS ...

Steve,

I thought I needed to ask more questions, but now I believe I may have an answer for you.

I will make the assumption that all your "MX" records are correct making this a real Microsoft Exchange issue having nothing related to IP name services.

You may simply need to modify the "cost" value in the "site addressing | routing" section in the secondary or sub.mydomain.com server. Change that to a number higher than the one that is in your primary. 100 is the worst route and 1 isthe default and best route. Make sure the primary cost is 1 and the secondary cost is more.

The MTA handles routing of messages and you actually only need one IMC for each site. If you have 2 servers in the same site you need to let microsoft MTA know how to handle the routing of those internet messages.

John Burchell
Network Manager
Green Mountain Energy Company

Collapse -

REVISED:Exchange 5.5 IMS routing problem

by Steve Cody In reply to REVISED:Exchange 5.5 IMS ...

Your answer is closest to what I'm looking for, I believe so you and another guy below will split the points.

The problem hasn't been resolved, but I'm working around it.

Thanks!

Collapse -

REVISED:Exchange 5.5 IMS routing problem

by Steve Cody In reply to REVISED:Exchange 5.5 IMS ...

John:
I have the IMS's at each location because they both have their own Internet connection, but the WAN connection between them is low speed.
I understand what you are saying about the routing cost. I really don't want a work around. I want a fix.
I have nothing configured that is telling the IMS on the primary server to deliver mail for this subdomain using anything but itself. This is why I don't understand why it's sending the mail to another IMS to be delivered. Why isn't it doing the delivery?

Collapse -

REVISED:Exchange 5.5 IMS routing problem

by burcjo In reply to REVISED:Exchange 5.5 IMS ...

Excuse me, I really don't have enough information afterall. I'm sure I can help you solve your problem if you wish to contact me offline.

Collapse -

REVISED:Exchange 5.5 IMS routing problem

by Steve Cody In reply to REVISED:Exchange 5.5 IMS ...

Poster rated this answer

Collapse -

REVISED:Exchange 5.5 IMS routing problem

by gmscne In reply to REVISED:Exchange 5.5 IMS ...

If you have one Exchange organisation and one site, but that site has two exchange servers, one being the primary server, then it may be that the other server is being used by the main server as a bridgehead. If so, bridgehead servers do deliver mail. It may be that the other server on the wan is closer to the recipient of the message which gets routed there.

Collapse -

REVISED:Exchange 5.5 IMS routing problem

by Shanghai Sam In reply to REVISED:Exchange 5.5 IMS ...

None of the servers are any closer to the alternate recipients than the others. The alternate recipients are the ones receiving the emails and they are out on the Internet.

Collapse -

REVISED:Exchange 5.5 IMS routing problem

by kdrungilas In reply to REVISED:Exchange 5.5 IMS ...

Questions:
1. How long has this been occurring? From the initial setup of Exchange? From a point where you created the custom recipients? From a change on the IMC properties? From the moment you created a sub-domain?

2. Does this happen with every message sent to the custom recipient? Or only randomly as it would if you have enabled "forward to host" set on the IMC Connector Tab of Properties? An entry for forwarding to host would cause the first message to go to the primary EX server and the next message to go to the other server, the next goes to the primary and so on...

I assume you have message tracking enabled in order to follow these messages from the primary to the other EXCH server.

3. Are both IMCs receiving mail for the same domain? One is not for domain and other for sub.domain, right?

Collapse -

REVISED:Exchange 5.5 IMS routing problem

by Steve Cody In reply to REVISED:Exchange 5.5 IMS ...

The other guys were real close to the answer....

Back to Software Forum
18 total posts (Page 1 of 2)   01 | 02   Next

Related Discussions

Related Forums