<div>
OK, cool. I wasn't sure what it was I was looking for exactly. This will also work with a subdomain? sub.domain.local being where the T1 goes and domain.local being where the mail server currently is?<br />

</div>


<div>
It looks like its a little more complicated them I thought. It looks like its going to be a combination of exchange and router policies... I haven't figured this one out yet...
</div>


<div>
<div class="content wysiwyg-content">
Hi. Ok, the customer setup is just a standard 2003 SMB server setup running exchange 2003. They are using a smart host for external mail delivery. (Postini). The issue is that they have now gotten a T1 connection to another vendor with a mail server. for a particular application, they need internal messages to be able to be sent through this new T1 connection. I can telnet to it and have added a MX record in the servers DNS so it knows what IP it is, but the exchange server keeps trying to send it outside and it gets rejected because the domain is a local domain, not a public one. How do I get exchange to not send messages destined for the T1 to the outside? I know its confusing, please ask me to clarify if need be!<br />
thanks in advance!<br />
<br />
JT<br />

</div>
</div>


Hi. Ok, the customer setup is just a standard 2003 SMB server setup running exchange 2003. They are using a smart host for external mail delivery. (Postini). The issue is that they have now gotten a T1 connection to another vendor with a mail server. for a particular application, they need internal messages to be able to be sent through this new T1 connection. I can telnet to it and have added a MX record in the servers DNS so it knows what IP it is, but the exchange server keeps trying to send it outside and it gets rejected because the domain is a local domain, not a public one. How do I get exchange to not send messages destined for the T1 to the outside? I know its confusing, please ask me to clarify if need be!
thanks in advance!

JT


OK, cool. I wasn&amp;#39;t sure what it was I was looking for exactly. This will also work with a subdomain? sub.domain.local being where the T1 goes and domain.local being where the mail server currently is?


It looks like its a little more complicated them I thought. It looks like its going to be a combination of exchange and router policies... I haven&amp;#39;t figured this one out yet...

how to route mail to a T1 connected local server

Interactions between email servers and clients are governed by email protocols. The three most common email protocols are POP, IMAP and MAPI. Most email software operates under one of these (and many products support more than one).  The correct protocol must be selected, and correctly configured, if you want your email account to work.

Email Protocols

Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.

Exchange

Transmission Control Protocol/Internet Protocol (TCP/IP) is the set of networking protocols that define end-to-end connectivity specifying how data should be packeted, addressed, transmitted, routed and received at the destination. This functionality is organized into four abstraction layers which are used to sort all related protocols according to the scope of networking involved.