Thank you.  This is what I wanted to know.

David.

-----Original Message-----
From: "Cybertime Hostmaster" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Date: Wed, 15 Jan 2003 23:38:10 -0800
Subject: [IMGate] Re: Exchange server behind IMGATE


> Right now the Exchange server is directly connected to the internet.  It'=
s
=3D
> a Windows 2000 Small Business server, with Exchange and ISA installed.  I=
=3D
>  would just change the name of the server if I could.  But it's a domain =
=3D
> controller.
>
> Is there a solution to this problem using IMGATE/postfix?

Set up an IMGate as the MX for your domain.

Lock access to the Exchange server so that it only talks to machines inside
your domain and/or IP block, or clients that authenticate.

Valid mail from the rest of the world should ONLY use the MX record to find
where to go, that will be the IMGate.

Because the IMGate will be inside your domain and/or IP block it will be
allowed to talk to the Exchange server.

So all mail gets filtered by IMGate, which is what you want.  Your users ca=
n
authenticate to send mail, and still use the Exchange server remotely that
way.

No need to change the A record or name of the Exchange server in this
configuration.

--Eric






Reply via email to