Re: Exchange servers down for several days or weeks

For simple Routing Group Connectors you don't need to worry about the SMTP
address space... but to do the kind of routing you want to do, you'll need
to generate additional SMTP email addresses for each site you want to
connect your "roaming Routing Group to."

- Generate email addresses for site2 = site2.domain.com (and so on for other
sites)
- Now you can create SMTP connectors instead of Routing Group Connectors.
- The lower cost one connects to site2 bridgehead for address space
site2.domain.com
- Another SMTP Connector with higher cost connects to HQ bridgehead for same
address space (site2.domain.com)
- Now if your roaming site can't deliver to site2, it will route to HQ.
- HQ will send to Site2 when it has connectivity (assuming HQ already has a
Connector to get to Site2)

--
Bharat Suneja
MCSE, MCT
www.zenprise.com
blog: www.suneja.com/blog
-----------------------------------------


"Thinkpad21" <thinkpad21@xxxxxxxxx> wrote in message
news:Oub8Y319FHA.3804@xxxxxxxxxxxxxxxxxxxxxxx
> Yeah...
> That's was also what I was wondering, since all SMTP address space will be
> the same !!!
>
>
>
>
> --
> "Bharat Suneja" <bharatsuneja@xxxxxxxxxxx> wrote in message
> news:OjHWMR19FHA.1988@xxxxxxxxxxxxxxxxxxxxxxx
>> Do all Routing Groups have the same SMTP address space (domain.com?)
>> --
>> Bharat Suneja
>> MCSE, MCT
>> www.zenprise.com
>> blog: www.suneja.com/blog
>> -----------------------------------------
>>
>>
>> "Thinkpad21" <thinkpad21@xxxxxxxxx> wrote in message
>> news:O0vGrju9FHA.360@xxxxxxxxxxxxxxxxxxxxxxx
>>> Thanks, that helps allot,
>>>
>>> But I need to go a step further, here is the theoretical config I need
>>> to do, and wondering how it would be done technically :
>>>
>>> All the site are part of the same international network (Equant), and
>>> when the tours move, the actual server IP is always the same, just the
>>> ISP router that changes and all sites have unrestricted network access
>>> to each other ( Netowork cloud ) so don't need to transit trough the
>>> HQ...
>>>
>>> So what I want to do, is have a message from a spoke site to another
>>> spoke site go trough the network, without actually going to the HQ
>>> Exchange FE or BE servers, but if the target site is down, then, the
>>> originating site should send the message to an Exchange server on the HQ
>>> and this HQ server will need to keep the message until the destination
>>> site comes back online ( within max 50 days ).
>>>
>>> Right now in Ex 5.5, all messages transit trough HQ, but a network
>>> problem at HQ could impact all site to site email transport !
>>>
>>> So I might need two sets of SMTP connectors with different costs, but
>>> wondering how to make it choose one or the other depending if the
>>> destination site is down or not ???
>>>
>>>
>>> Thanks !!!
>>>
>>> --
>>> --
>>> ---
>>>
>>> "Bharat Suneja" <bharatsuneja@xxxxxxxxxxx> wrote in message
>>> news:ercY%23As9FHA.3132@xxxxxxxxxxxxxxxxxxxxxxx
>>>> SMTP Virtual Server properties | Delivery | Expiration Timeout. You can
>>>> set this to any number of days you want, and can also change the retry
>>>> intervals.
>>>>
>>>> In hub and spoke where spoke is going to be offline for long periods,
>>>> you most likely will have the spoke in its own Routing Group. Create a
>>>> new SMTP Virtual Server (using a different IP address than the one your
>>>> default SMTP VS is bound to). Change the Expiration Timeout and Retry
>>>> intervals. Create a new Routing Group Connector to connect to the spoke
>>>> Routing Group. Use the new SMTP VS as a Bridgehead. (Will also need to
>>>> create the RGC the other way, from spoke to the hub).
>>>>
>>>> Won't need to set up ETRN in this case. When the spoke server comes up
>>>> and both bridgeheads can talk, messages will be delivered at the next
>>>> retry interval.
>>>>
>>>> To make sure the hub's normal outbound smtp mail is not routed over the
>>>> new SMTP VS you can create a SMTP Connector with address space * (if it
>>>> doesn't already exist) and use the default SMTP VS.
>>>> --
>>>> Bharat Suneja
>>>> MCSE, MCT
>>>> www.zenprise.com
>>>> blog: www.suneja.com/blog
>>>> -----------------------------------------
>>>>
>>>>
>>>> "Thinkpad21" <thinkpad21@xxxxxxxxx> wrote in message
>>>> news:uYEyKvr9FHA.1184@xxxxxxxxxxxxxxxxxxxxxxx
>>>>> Well, I need to find exactly how to configure it, not just the option,
>>>>> but also make sure messages are not NDR'd after couple of days, but
>>>>> actually stay in the queue until the server comes back online...
>>>>>
>>>>> Thanks !!!
>>>>>
>>>>> --
>>>>> --
>>>>> "Bharat Suneja" <bharatsuneja@xxxxxxxxxxx> wrote in message
>>>>> news:O$oipJr9FHA.2364@xxxxxxxxxxxxxxxxxxxxxxx
>>>>>> You can use ETRN with SMTP.
>>>>>> You can configure SMTP servers to queue up mail for a certain domain
>>>>>> for that long.
>>>>>>
>>>>>> --
>>>>>> Bharat Suneja
>>>>>> MCSE, MCT
>>>>>> www.zenprise.com
>>>>>> blog: www.suneja.com/blog
>>>>>> -----------------------------------------
>>>>>>
>>>>>>
>>>>>> "Thinkpad21" <thinkpad21@xxxxxxxxx> wrote in message
>>>>>> news:Of4TLVq9FHA.4084@xxxxxxxxxxxxxxxxxxxxxxx
>>>>>>> Hi,
>>>>>>>
>>>>>>> Is there a way to accumulate messages in an Exchange 2003 server for
>>>>>>> another server in a hub-spoke config, if the spoke is off-line for
>>>>>>> several weeks ???
>>>>>>>
>>>>>>> Here is the situation :
>>>>>>> I'm doing an architecture review of an Ex2K3 deployment ( from an
>>>>>>> Exch 5.5
>>>>>>> org ), the particular thing about this client is, that half of their
>>>>>>> Exchange 5.5
>>>>>>> sites are actual tours that move around the world, and stay only
>>>>>>> about 6 weeks at each location ( brining the hole LAN of that site
>>>>>>> with them
>>>>>>> in the process, the Lan has it's own Win2K3 DC, Exchange 5.5, File
>>>>>>> server and etc...)
>>>>>>>
>>>>>>> Each time they move, they have about 5 to 45 days of dark time,
>>>>>>> where severs
>>>>>>> are in a box and off-line
>>>>>>> In the 5.5 org, they were using X400 with Etrn calls for the tour
>>>>>>> servers to
>>>>>>> come get the email retained at the HQ...
>>>>>>> Do not want to use X400 connectors for this, because of the
>>>>>>> licensing costs
>>>>>>> ( Enterprise is needed and SMTP is the future ), Wondering if same
>>>>>>> can be
>>>>>>> done with the SMTP connector...( think so, but haven't done it
>>>>>>> before )
>>>>>>>
>>>>>>> P.S. Consolidation is not an option yet, since WAN links and all, it
>>>>>>> would
>>>>>>> have been the best scenario, but not yet...
>>>>>>>
>>>>>>> If anyone has done this, I would really appreciate any comments,
>>>>>>> hints,
>>>>>>> documents, or anything on this...
>>>>>>>
>>>>>>> Thanks !!!
>>>>>>>
>>>>>>> --
>>>>>>> --
>>>>>>> ---
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>


.

Relevant Pages

  • Re: Exchange 2003 Not sending to ISPs SMTP Server
    ... YOu can't just "change the smtp" when using the pop connector, ... > including Exchange Server 2003. ... > POP connectors, it did set them up correctly, but it ...
    (microsoft.public.windows.server.sbs)
  • Re: SMTP Connector Question
    ... I had added a server to the SMTP bridgehead the ... If I add the server as a bridgehead should I restart the SMTP ... In the Active site (routing group A) we have an SMTP connector setup. ...
    (microsoft.public.exchange.design)
  • Exchange 2003 not sending mail to ISPs SMTP Host
    ... I have installed Microsoft Small Business Server 2003 ... POP and SMTP are mail.ptdprolog.net. ... SMTP host it never makes it. ... POP connectors, it did set them up correctly, but it ...
    (microsoft.public.exchange.connectivity)
  • Exchange 2003 Not sending to ISPs SMTP Server
    ... I have installed Microsoft Small Business Server 2003 ... POP and SMTP are mail.ptdprolog.net. ... SMTP host it never makes it. ... POP connectors, it did set them up correctly, but it ...
    (microsoft.public.windows.server.sbs)
  • Re: SMTP Connector Question
    ... I had added a server to the SMTP bridgehead the ... If I add the server as a bridgehead should I restart the SMTP ... In the Active site (routing group A) we have an SMTP connector setup. ...
    (microsoft.public.exchange.design)
Loading