[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 262
  • Last Modified:

Exchange routing - Ideas on current setup

Hi all,

Bit of a strange, and probably uneccessarily complicated one.

We have an SBS server, running Exchange 2003 listening on port 97 and a Mail Gateway/Archiving product listening on port 25.
The Gateway product receives mail and passes onto exchange and exchange outbound sends out through the gateway product also... (smarthost SMTP connector).

The problem i have is that the exchange is not fully responsible for the domain in question.
In addition there is a domain (domain1.com) that is pulled into the gateway product via POP3. This account for 5 mailboxes, the rest are situated around europe.

The Exchange has been setup not to be responsible for the domain, however the limitations in the gateway product do not allow this - so i need to bypass the product for mail from these domains.
For various reasons the domain has to be the Primary mail domain for mailboxes.

The question: How can i filter mail going to domain1.com (outbound) to bypass the Mail Gateway product. I have tried creating another SMTP connector not using the smarthost feature, but does not seem to work.
Is there an article for this kind of exchange routing?

Thanks in advance.
0
utilize
Asked:
utilize
  • 2
1 Solution
 
SembeeCommented:
You are almost there with the SMTP Connectors.
You need to adjust the cost on the SMTP Connector.

On the connector for everything except the domain that you wish to bypass, change the cost to 2.
Leave the cost on the SMTP connector for the domain1.com domain as 1.

Make sure that you have NOT configured a smart host on the SMTP virtual server.

Simon.
0
 
utilizeAuthor Commented:
Thanks for the reply, much appreciated.

However - i did try exactly what you said, with the costing set correctly on the 2 different SMTP Connectors.
With this setup, the system simply doesnt receive ANY mail, local or externally. Its like the system has no idea where to route internally or deliver externally.

I am clearly doing something wrong if you agree the SMTP connector setup is correct - One delivering through the gateway software, the other using DNS - this "appears" to work ok, accept the mail internally or receiving does not work.

The Recipient policy is set to use the domain1.com domain (the one we are routing all over the place) as the primary, although not responsible for the domain (this option is unticked, but greyed out).

What am i missing?!? Surely this should be relatively simple in terms of exchange routing?
0
 
SembeeCommented:
Unfortunately what you are trying to do is not usual. I don't tend to recommend that email domains are shared between two servers. The added complexity of trying to bypass the gateway product has further made things more difficult.

In fact, speaking to another Exchange MVP, we don't think you are going to be able to do what you want to do.

The SMTP Connector is getting in the way. Exchange sees the domain listed in the connector and then sends the email to the server listed. That would explain why your email fails totally.

I think that you only have two choices - make the Exchange server responsible for all email or use a different gateway product.

Simon.
0

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now