> In my mind, this seems pretty straightforward, mirror my current > IMAIL server, give the new one a different name, a static IP address > from the remote site's ISP and put a mx entry with a higher number > for that server.
> On the client side, configure Outlook to check both accounts in case > there is a connection issue for a short time, that I'm not aware of, > and mail goes to the backup even when the primary is working. That isn't likely the easiest to support. Rather, I'd recommend using ldap2aliases (see my sig) to synchronize the userbase into an alias table on the secondary. In normal operation, mail will be forwarded to the primary, enabling you (among other benefits) to save on a Declude license. _If_ the primary goes down hard, you'd then delete the alias key on the secondary, causing mail to be delivered locally on the secondary rather than being forwarded across the wire. --Sandy ------------------------------------ Sanford Whiteman, Chief Technologist Broadleaf Systems, a division of Cypress Integrated Systems, Inc. e-mail: [EMAIL PROTECTED] SpamAssassin plugs into Declude! http://www.mailmage.com/products/software/freeutils/SPAMC32/download/release/ Defuse Dictionary Attacks: Turn Exchange or IMail mailboxes into IMail Aliases! http://www.mailmage.com/products/software/freeutils/exchange2aliases/download/release/ http://www.mailmage.com/products/software/freeutils/ldap2aliases/download/release/ To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/
