Re: Is this a reason?
- From: Peter <Peter@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 5 Jun 2006 12:23:02 -0700
Rich,
Thanks for your help and time. Sorry for long post.
Actually, we created two SMTP connectors with address * already. Here is
our detailed configuration:
............................................................
Routing group1: member-one ABC's FE server
SMTP connector (address space *)
Routing group connector to connect RG1 and RG2 (cost
1)
Routing group 2: member-ABC's two backend servers and one XYZ's backend
server
routing group connector between RG1 and RG2
routing group connector between RG2 and RG3
routing group3: member-one XYZ's FE server
SMTP connector (address space *)
routing group connector between RG3 AND RG1 (cost 20)
----------------------------------------------------------
What's your recommendation for cost? Our purpose is that emails are
automatically routed to the XYZ site in case ABC site T1 is down and I do not
need to manually change the cost.
THANK YOU VERY MUCH!
"Rich Matheisen [MVP]" wrote:
Peter <Peter@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:.
[ snip ]
Today, T1 at ABC site is down and we can receive inbound emails through T1
at XYZ site but we can not send emails out. When I check the routing group
connector, I found out that routing group connector between RG1 and RG2 has
cost 1 and routing group connector between RG2 and RG3 has cost 20. So, I
chnaged
routing group connector between RG2 and RG3 cost to 1 and routing group
connector between RG1 and RG2 to 20. Do you know WHETHER this is a reason
why mails did not route through T1 at XYZ site?
I want to route mails automatically in case T1 at ABC site or T1 at XYZ site
is down? How can I achieve this? any suggestions or recommendations are
welcomed!
Outbound mail is going to use either the nearest SMTP Virtual Server,
or the SMTP Virtual Server(s) in a SMTP Connector.
It sounds like you need to create a SMTP Connector, give it an Address
Space of "*" and put into the "Local Bridgeheads" the SMTP Virtual
Server at the location that still had Internet connectivity. That
*should* cause all the messages enqueued on the virtual servers to be
delivered to the bridgehead. If that doesn't happen in a reasonable
time (say, 15 minutes) you may have to force a recategorization of the
mail on each server.
Add the registry value by following the instructions here:
XCON: Adding a Registry Key to Re-Categorize Messages [279616]
**** NOTE: DO NOT REINSTALL EXCHANGE!!! You only have to restart the
SMTP service after making the change to the registry.
You don't have to remove the value after you're finished. Just change
the value from "1" to "0".
--
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
- Follow-Ups:
- Re: Is this a reason?
- From: Rich Matheisen [MVP]
- Re: Is this a reason?
- References:
- Re: Is this a reason?
- From: Rich Matheisen [MVP]
- Re: Is this a reason?
- Prev by Date: Re: Messages that Were Not Sent
- Next by Date: Re: Message between 2 Exchange servers
- Previous by thread: Re: Is this a reason?
- Next by thread: Re: Is this a reason?
- Index(es):
Relevant Pages
|
