Our forums are currently in maintenance mode and the ability to post is disabled. We will be back up and running as soon as possible. Thanks for your patience!

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 2 of 2)   Prev   01 | 02
Thread display: Collapse - | Expand +

All Comments

Collapse -

REVISED:Exchange 5.5 IMS routing problem

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

There are a couple more questions to get a better picture:

1. How are you connecting to the Internet and are your LAN IP addresses also your Internet IP addresses?

2. Do you maintain your own DNS or is it handled by your ISP?

3. Are you trying to make the primary Exchange server deliver directly to the forwarded mailbox? If so, where do the forwarded mailboxes reside?

The problem as I see it:

The two exchange servers are both in DNS as MX hosts one being under the primary domain and the other the secondary domain. The IP addresses for the servrs is the same for either Internet or WAN. With the use of the Custom SMTP Recipient containers you are actually doing the following routing of the mail.

1. The message comes in under the primary domain.
2. It gets forwarded to the custom recipient which uses an SMTP address for another domain.
3. The IMS does a lookup for the secondary domain and gets the IP address for the second Exchange server.
4. Noting that IP address actually coinsides with the IP addressing used accross the WAN it takes the most direct route and contacts the secondary IMS through the WAN link.
5. Now talking IMS to IMS the transfer of the message is made to the secondary server where the local MTA takes over and delivers the message to the mailbox.

The real question is then: How do you really want the forwarded message routed and delivered?

Looking forward to your reply...

Collapse -

REVISED:Exchange 5.5 IMS routing problem

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

I do not have the secondary server set up as the MX entry for any domain. The server that is suppsoed to receive the subdomain's email is out on the Internet, away from my WAN/LAN.

I really want the forwarded message to be delivered by the primary server. Since the primary server happens to be the one that received it to begin with, I feel like it should go ahead and re-deliver it out to the alternate recipient's address.

Collapse -

REVISED:Exchange 5.5 IMS routing problem

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

Steve,

If I understood you correctly you want each of your server deliver Internet mail using its own IMS (not the other server IMS) . I would suggest you have to reconfigure Address Space of IMS on both servers. There is an entry like "SMTP * 1"(where * means all addresses and 1 means routing cost). However, by both have "Organization" restriction by default. I believe your problem will be solved if you change that restriction to "Location".
Or, you may want to add an entry specifically for that subdomain with "Location" restriction at both servers.

Sorry, I have no sufficient test environment to check/test that myself :-))

Hope this gives you some ideas,
Dima

Collapse -

REVISED:Exchange 5.5 IMS routing problem

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

then, you have to restart IMS at both servers and probably wait for Routing recalculation.

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 Magetower In reply to REVISED:Exchange 5.5 IMS ...

The above answer is the right direction but would restrict your users to only sending out the server their mailbox resides on. This is no problem if your mailboxes are distributed between the servers but the information you have given here indicatesall the mailboxes reside on the primary server (kind of makes the secondary server worthless if the WAN link croaks). By using the location restriction the outgoing SMTP would never go through the secondary IMS. Some information for setting up Location restrictions can be found in MS KB article Q234639.

If you are only forwarding to one outbound location then you can set up routing for that domain by placing it in the Address Space for the IMS and giving it a 1 and the all others (*) route a2 on the primary indicating the primary IMS.

Do the same for the secondary IMS except for indicating itself for the all others (*) entry.

Hope this helps...

Collapse -

REVISED:Exchange 5.5 IMS routing problem

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

I have 3 WAN locations, each with their own server. Each mailbox is on the server at it's location.

The problem I'm having happens to be related to the forwarding of mail to custom recipients set up as the alternate recipient for some accounts on the primary server.

Collapse -

REVISED:Exchange 5.5 IMS routing problem

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

This question was closed by the author

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

Related Discussions

Related Forums