As it stands, the Exchange server will re-direct any unrecognized addresses to the IMail server and delivery occurs. However, this is not the case when we attempt to send email to an address from the IMail server to the Exchange server. It is automatically seen as an invalid final delivery address because it is trying to deliver it locally. We have made every effort to ensure that there are no addresses duplicated on these servers.afaik, no way per-domain in Imail (you could futz around with nobody alias and scripting), but a cleaner way that requires no programming is per-user. You setup an Imail account for every Exchange user, and put a forwarding rule on every account:
Is there a way to tell the IMail server to re-direct to the Exchange server if the address does not exist on itself much like the way the Exchange box does? Thanks.
forward: [EMAIL PROTECTED]
In Imail hosts file
ip.ad.re.ss exchange.domain.com
This doesn't scale well if have frequent Exchange user add/delete or 100's of Exchange users.
IMGate provides a more systematic solution:
Every user has the usual public address of
[EMAIL PROTECTED]
As the mail passes in/out Imgate, a simple, single table file re-writes the public @domain to a an internal sub-domain, reflecting where the mailbox really is:
[EMAIL PROTECTED] [EMAIL PROTECTED]
[EMAIL PROTECTED] [EMAIL PROTECTED]
So mail between the internal sub-domains servers is routed correctly, but @domain.com is the universal public address. Internet never sees nor needs to know about the "imail" and "exchange" internal sub-domains.
There are scripts for Imail and Exchange that export their user list periodically to IMGate where the above table is automatically maintained. So your per-user admin work for this setup is nil. And no external Imail/Exchange traffic has to pass through the Exchange/Imail box.
Internal users setup their mail programs normally with
[EMAIL PROTECTED]
On Exchange, mail to Imail users gets routed by exchange to Imail, as you have now.
On Imail, mail to Exchange users gets delivered to nobody alias, that filters/forwards all of it to IMGate which routes it to Exchange.
This solution is easily scaleable to any number of internal mailbox servers and to any number of accounts and traffic.
oh, yeah, IMGate is also useful for anti-spam. :)) You really shouldn't hook Exchange to Internet. It's an intranet server. You can do it, but dogs can walk on their hind legs, too.
I'm consulting to the US Department of Defense for precisely the above solution. IMGate as SMTP defense, and for routing external/internal mail to multiple Exchange boxes that are not yet integrated under AD (which will provide, when very eventually fully implemented, global mail routing).
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/
