>What I am trying to do is to setup a redundancy link at different location,
>such that in case one location blows up, imail server at another location
>picks up,
That won't work. best you can do is "cross 2ndary" the MX of each domain so
that you get incoming mail redundancy:
file: db.location1.com
;
$ORIGIN location1.com.
@ MX 10 imail.location1.com.
@ MX 20 imail.location2.com.
and then...
file: db.location2.com
;
$ORIGIN location2.com.
@ MX 10 imail.location2.com.
@ MX 20 imail.location2.com.
If either MX 10 is unreachable, the incoming mail goes to MX 20, but the
mail stored at MX 20 is NOT accessible until the MX 10 comes up and can
receive the stored mail from MX 20.
>so that end users would not have any downtime, and they needn't
>know about it. For this to work, both imail server need to sync their user
>account setting, messages, etc.
That's not do-able with Imail facilities or any internet protocol I know.
Best you can do is on each site have the usual hot-sparing like disk mirros
and RAID, plus hw spares and frequent software backups of the Imail machine
so it can be re-built quickly. Until it's rebuilt, the mail accounts on
that machine will be inaccessible.
You simply can't have all accounts duplicated on both Imail machines. I'd
go with the above plan and see how it goes. You could test it by simply
unplugging the RJ45 from one Imail machine and watch the queue build up on
the on the other machine.
Len
Please visit http://www.ipswitch.com/support/mailing-lists.html
to be removed from this list.
