1. Set up the exchange server as mail2.server.com
location.duda.com would be more self-documenting?
2. Set the MX record to have a priority of 20
I'd keep exchange off internet, and out of DNS records.
3. remove the users for the imail server
probably not, see below
Keep the 15 users accounts on Imail under @duda.com domain, but for each of those accounts, set a forwarding rule that points to [EMAIL PROTECTED] (with no leading ".,[EMAIL PROTECTED]").4. set them up on the exchange server an have them still use @duda.com
This approach retains Imail as the single MX for duda.com (less DNS to manage, a single @recipient.domain for both main and satellite sites, avoiding the @location.duda.com in public email addresses, and the forwarding gives you some fake "address re-writing" / aliasing capability, hiding from public senders that these 15 people are actually on another mailbox server.
It also allows all Scott's Declude stuff on Imail to scan/defend the mail going to Exchange. :))
Unfortunately, this requires location.duda.com to have MX records, because that's where Imail forwarding will send the mail for location.duda.com.
But you can avoid that, by putting this in the Imail hosts file:
ip.ad.re.ss location.duda.com # use a real number, ok?
... because when Imail wants to forward to @location.duda.com, it looks up the MX for location.duda.com, it won't find one in DNS (this is useful obscurity for somewhat protecting Exchange, see below for total protection). Then Imail falls back and will try to deliver to the A record of location.duda.com, which it will find in its local hosts file. Voila inbound routing successful.
You can further hide Exchange from internet, by having Exchange's Internet connector relay all its outbound mail through Imail, giving you a log trace (and control) of all the company's mail flow, inbound and outbound, using Imail as the "SMTP chokepoint". Put Exchange's ip in Imail's relay for addresses.
On the firewall at the exchange site, block access from internet to port 25 of exchange, and allow access from Imail's ip to port 25 of exchange.
And you can do same for one satellite site, or 50.
btw, since I have admitted/confessed/prostrated myself before the Imail list, that "I don't touch Imail anymore", you should disqualify all comments as useless, in fact, I guess I should proably unsubscribe from this list. So, Valiant Mail Gladiators, caveat emptor, habeas corpus, and, primum inter pares, hocus pocus!
You can do all the above with IMGate, too. And avoid routing the traffic location.duda.com through Imail (for 15, no big gain, for 1500, Just Do It). An advantage being that Imail can be down, and IMGate will continue to route the mail for location.duda.com, and you don't have to create maintain those 15 accounts on Imail.
Len
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/
