Re: Routing Question
- From: "Doug" <none>
- Date: Mon, 14 Aug 2006 09:58:27 -0400
Thanks - I'll give it a try
"Rich Matheisen [MVP]" <richnews@xxxxxxxxxxxxxxxxxxxxx> wrote in message
news:777sd2ttie5ravfuhm0d25mh7mijsk8lqi@xxxxxxxxxx
"Doug" <none> wrote:
I appreciate the response. We require the ability to deliver to our
smarthost on a non-typical port. You make it sound as if configuring your
VS
for smarthosting is "bad" why is that?
Because ALL mail is sent to the smarthost, even the internal stuff.
With just one server it doesn't really matter, but when you have more
than one Exchange server you're in for some interesting times.
The smtp connector does not have the
ability to be configured for smarthosting on any port besides 25. We
require
this as does our hosting company.
Create a second SMTP Virtual server and configure it to use whatever
ports you need (because you're not using port 25 you should be able to
use the same IP address). Then create a SMTP Connector and put the 2nd
SMTP VS as the local bridgehead server.
Maybe it would be helpful to give a little more insight into what I
experienced taht caused me to make the post.
Because you're now sending mail between two servers with SMTP, the VS
on the first machine is sending the mail for the 2nd machine to the
smart host for delivery. The 2nd machine thinks it can send mail to
the Internet becasue you haven't told it otherwise (there's no SMTP
Connector to direct outbound mail to just the one SMTP VS).
Existing configuration is a single 2003 Exchanger server (EX1) . EX1 is
configured to smarthost on non typical port to an outside company
(configured through virt. smtp server)
Okay. One server, no problem. Not advisable, but it'll work.
Brought up another 2003 Exchange server EX2. Moved a test mailbox to this
server and discovered some deliverability issues with this mailbox.
Internal
mail back and forth between this mailbox and others on EX1 was fine.
Sending
to external clients from EX2 was fine. Problem was inbound mail to EX2.
Anything destined for this test mailbox on EX2 looks like it was rcv'd by
EX1 as expected since EX1 is the only server listed in DNS as mx for this
domain. But, I had thought that EX1 would then forward to this test
mailbox
on EX2...however, what I saw was that instead of forwarding to the user on
EX2, it forwarded the mail to the smart host....and created a mail loop.
Sure. That's exactly what you've told it to do.
I thought this woould be a pretty straightforward thing to accomplish but
apparently not. Someone in this group advised that what I was trying to
accomplish was not possible. Trying to understand what I need to do to get
this to work correctly with the requirements that I was presented with.
--
Rich Matheisen
MCSE+I, Exchange MVP
MS Exchange FAQ at http://www.swinc.com/resource/exch_faq.htm
Don't send mail to this address mailto:h.pott@xxxxxxxxxxxxx
Or to these, either: mailto:h.pott@xxxxxxxxxxxxxxx
mailto:melvin.mcphucknuckle@xxxxxxxxxxxxx
mailto:melvin.mcphucknuckle@xxxxxxxxxxxxxxx
.
- References:
- Routing Question
- From: Doug
- Re: Routing Question
- From: Rich Matheisen [MVP]
- Re: Routing Question
- From: Doug
- Re: Routing Question
- From: Rich Matheisen [MVP]
- Routing Question
- Prev by Date: Full text index on Exchange 2003
- Next by Date: Search for secondare email address?
- Previous by thread: Re: Routing Question
- Next by thread: Port 25 traffic with Firebox 1000
- Index(es):
Relevant Pages
|