Re: Can't setup multiple smart hosts



SMTP Connector settings do not apply to Administrative Groups. Admin groups
are only a security/delegation boundary. They are not a routing boundary.
When you go to the help on that topic, it shows that setting the scope
defines which servers the SMTP Connector will be available to. However,
Cost needs to be taken into account as well. Exchange servers always take
the lowest cost, so they would likely only use the SMTP connector if it was
a lower cost than their normal delivery method.

In your case, I believe that you'll have to create a separate SMTP Connector
for each Routing group, and you will have to use SmartHosts. If this is
indeed the case, then setting the scope to Routing Group shouldn't have any
effect, though you might want to leave it to Organization so that it can be
used as a path if a less expensive path is not available...

Have you considered consolidating Routing Groups? Are all the servers in
these different routing groups in different locations with slow connecttions
between them?

--
Ben Winzenz
Exchange MVP
MessageOne
Read my blog!
http://winzenz.blogspot.com
http://feeds.feedburner.com/winzenz (RSS Feed)


"dave313" <dave313@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:AF2D9888-52F4-4181-9991-31957D56AC19@xxxxxxxxxxxxxxxx
> One question on the Entire Organization setting...is that truely the
> entire
> org or only that administration group?
>
> Reason I ask is that we are 4 unique areas (admin groups), and really only
> want it to affect my admin group (17 sites/RGs), not all 4 areas.
>
> "Ben Winzenz [Exchange MVP]" wrote:
>
>> Better accomplished by setting up an SMTP Connector, and you don't even
>> have
>> to use a SmartHost.
>>
>> Under the Routing Group, Connectors, create a new SMTP Connector.
>> Specify
>> the 2 central servers (assuming they are Exchange servers) as Bridgehead
>> servers. Specify the Address Space as *. Let it use DNS to route mail
>> (it
>> will work fine). Specify that the scope be Organization.
>>
>> Once you do this, ALL external mail should route to one of the Bridgehead
>> servers, which will then use normal methods (DNS) to lookup the remote
>> destination and send the mail. This is what you are desiring, correct?
>>
>>
>>
>> --
>> Ben Winzenz
>> Exchange MVP
>> MessageOne
>> Read my blog!
>> http://winzenz.blogspot.com
>> http://feeds.feedburner.com/winzenz (RSS Feed)
>>
>>
>> "dave313" <dave313@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:82AF9BD7-D04F-4CD7-8AA6-702B33B9022B@xxxxxxxxxxxxxxxx
>> > What we have is the following:
>> >
>> > 16 Exchange sites each with their own server. Each server current
>> > sends
>> > any
>> > external mail directly to the internet. This is NOT what we want. We
>> > want
>> > all external destination mail to come to a central point for control
>> > and
>> > go
>> > out 1 of 2 servers (these servers have the reverse DNS on the internet
>> > for
>> > proper SPAM checking).
>> >
>> > We thought using the smart host to forward external to these 2 servers
>> > woudl
>> > be the best and preferred way to accomplish this?
>> >
>> > But as mentioned in another message in here and mine, you can't specify
>> > more
>> > than 1 smart host on a VS.
>> >
>> > "Ben Winzenz [Exchange MVP]" wrote:
>> >
>> >> Don't configure Smarthosts on the SMTP Virtual Server, for starters.
>> >>
>> >> Create an SMTP Connector to do this. Assugn the connector the address
>> >> space
>> >> of "*".
>> >>
>> >> Where exactly do you get the error? If you use [1.2.3.4];[1.2.3.4] it
>> >> should allow that just fine.
>> >>
>> >> --
>> >> Ben Winzenz
>> >> Exchange MVP
>> >> MessageOne
>> >> Read my blog!
>> >> http://winzenz.blogspot.com
>> >> http://feeds.feedburner.com/winzenz (RSS Feed)
>> >>
>> >>
>> >> <dave313@xxxxxxxxx> wrote in message
>> >> news:1135697582.766753.15270@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
>> >> > Trying to setup all my servers to forward their externally bound
>> >> > internet mail to 2 servers so we can better control the mail flow
>> >> > outbound.
>> >> >
>> >> > On the SMTP virtual server, if we enter in the smart hosts names or
>> >> > IPs
>> >> > as follows we get an error saying "The Domain Name Is Not Valid":
>> >> >
>> >> > FQDN1;FQDN2 or [1.2.3.4];[1.2.3.5]
>> >> >
>> >> > If we put just 1 of the FQDN or the IP it will accept that, but not
>> >> > multiples of either. Any ideas why?
>> >> >
>> >> > Thanks
>> >> >
>> >>
>> >>
>> >>
>>
>>
>>


.



Relevant Pages

  • Re: 3 E2k3 servers, 1 admin group - want seperate smtp connectors for
    ... If you have 3 physical sites with Exchange servers but they're all in the ... same Routing Group, Exchange sees them as being in one Site. ... Site - servers within the same Routing Group route messages directly to each ... the servers to the appropriate RG, and create SMTP Connectors in each RG. ...
    (microsoft.public.exchange.setup)
  • Re: send mail for a specific customer to a specific mail server over vpn link
    ... I was attempting to force my Exchange server- only Exchange ... I created an additional SMTP Connector defining ... the address space for customer.com and the non preferred mail server as the ... A routing group is a logical concept. ...
    (microsoft.public.exchange.admin)
  • Re: Change to SmartHost Failed
    ... I'm assuming we're talking about Exchange 2003 since you didn't say. ... Do not configure a smart host in your back-end SMTP ... You created an SMTP Connector and specified the ... two front-end servers as bridgehead servers, so that dictates that all mail ...
    (microsoft.public.exchange.admin)
  • Re: Ex5.5 --> Ex2003 Migration questions
    ... servers while still in mixed mode. ... > Currently we have an Exchange 5.5 organization with four sites. ... > other sites and IMC for smtp connection). ... > And is it true that one Routing group will automatically built for every ...
    (microsoft.public.exchange.design)
  • Re: Move from Exchange 2000 to 2003
    ... you must upgrade the front end server first in the Admin Group. ... Upgrade your existing Front End server to Exchange 2003, ... routing Group be the old Routing Group For your old Administration Group. ... Retire the Old Exchange 2000 Servers. ...
    (microsoft.public.exchange.setup)

Loading