I'm not clear on exactly what you and/or your users expectations are. How frequently are you going to be syncing the two e-mail data stores? Are you planning on mirroring across a WAN?
<sigh> I thought this was going to be so simple, just shows how much I really don't know. Here are my expectations: The second server will be used ONLY when the primary is unreachable..as in our internet connection is down for several hours or more. The second server is going to be set up at a remote site, and that remote site will have its own ISP and its own public block of IP addresses, one of which will go to the second server. The remote site is connected to our main site here by a frame circuit. I have a rather small user base, only about 300 users. My idea was to install IMAIL on the 2nd server (declude as well) and then import the registry key from my current Imail server to the new one. This would get all the current users and lists onto the new one. I really don't make a lot of user changes on a day to day basis, so any account I set up or delete on my primary server, I would just make the same change manually on the second server. Users would not be allowed to change their passwords via webmail. I relay only for IP addresses, remote users (salesppl) vpn in so smtp auth is not a factor here. If my primary server was unreachable, I would want my internal users to be able to send/receive email, via the second server, using their <user>@todhunter.com email address. My remote users would still need to be able to access webmessaging over the internet to retrieve their mail. I run my own primary nameserver here, at my main site. I would want to set up DNS entries for the second(new) server in advance, since, if my internet connection is down here at my site, my primary nameserver is too. I would want the second server to have the same IMAIL official host name and the same mail.todhunter.com alias. My thought was then, I could just create a host record (ie mail2) in DNS, point it to the IP address I will be using for it, create an mx record using mail2.todhunter.com and give it a higher number than the one than the primary, say 50 or 100 or whatever. In Outlook, on all client machines, we would set up a 2nd email account for mail2 as the incoming and outgoing server so users would be able to connect to it. If the primary is up, it shouldn't get mail sent to it as the mx record will have a higher number. I don't expect anything to happen automatically, I just want to ensure when I fire it up, and it needs to be working, everything on the server itself, and in DNS is working right. I could even keep the smtp service on the second server stopped, until I needed to use it. Sharyn I We are the worldwide producer and marketer of the award winning Cruzan Single Barrel Rum, judged "Best in the World" at the annual San Francisco Wine and Spirits Championships. For more information, please click (go to) <html><a href="http://www.cruzanrums.com";>www.cruzanrums.com</a></html> 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/
