If bandwidth is a major concern, IMail peering with 4 servers might be an issue. If bandwidth is an issue, and you decide on multiple servers, one way to do it is with a meta-like mail domain which contains aliases to the real addresses on the corresponding branch's mail server.
IMGate can do that kind of "meta" mail routing, and we have tools now to export the Imail user list to IMGate.
This does increase admin burden
Not with the IMGate approach, it's fully automatic.
Each site exports its local user list to IMGate.
IMgate does the aliasing at the domain level, with an alias file per site, for site A the file would have:
[EMAIL PROTECTED] [EMAIL PROTECTED]
Another alias file for B site has:
[EMAIL PROTECTED] [EMAIL PROTECTED]
This avoids Imail peering completely, a good thing to avoid.
Len
_____________________________________________________________________ http://MenAndMice.com/DNS-training: New York; Seattle; Chicago IMGate.MEIway.com: anti-spam gateway, effective on 1000's of sites, free
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/
