On 12/01/11 03:10, Tom Cross wrote:
> Hi
> I have had a request from one of our customers that have Exchange on
> their "in house" server.
> They would like us to be their "Backup", Secondary mail server.
>
> We are doing this for some other customers at the moment.
> Their server goes down, our server, receives the mail until their server
> comes back on line.
> That is what normally happens.
>
> This customer wants us to enable them, if their server goes down to be
> able to logon with surgeweb and answer mail, untill their server comes
> back up????
>
> Any ideas??
>
> This is what I was thinking, do not know if it would work.
>
> Exchange Mail = mail.aaabbb.com.au ip 203.203.203.203
> We setup = mail.aaabbb.com ip 203.19.159.244 BUT on that domain we setup
> the alias mail.aaabbb.com.au
> We would have to get the Exchange server to query the Surgemail server
> at periods, because any user on our server sending them mail it would go
> into the Surgemail Server.
>
> Another problem would be syncing passwords.
>
>
> Tom Cross
> Partner (Synergist)
> HTMLnet
> 0418 295 336
>HIDDEN@tml.com.au
> ** <http://www.html.net.au/>
>
>

If it was me, I would say, no to acting as a backup mailbox server.  You 
can be their backup MX server, but no access to their mail while their 
system is down.  You can easily store email until their server gets back 
online.

But the issue of syncing mailbox adds/deletes, aliases, groups and 
passwords is beyond what is reasonably possible.  I can not think of any 
way to automate that process, especially passwords.

Lyle Giese
LCR Computer Services, Inc.