[wellylug] Apache as a proxy for Outpuke's web-interface

[Michael Dittmer (An Inside Job)]

Hi Andrej

What you can do and is recommended by Microsoft is to have the Exchange 2003
box sitting on your protected-local network and have a Windows Server 2003
or Windows Server 2003 (Web-Edition) sitting in the DMZ.

Basically, the IIS of the box in the DMZ hides the internal Exchange box,
but presents the OWA client to the internet using SSL. All you then need to
do is make sure that SSL is being passed through the firewall from the DMZ
host to the internal network.

The DMZ host unpacks the SSL-stream, checks for errors and then repacks the
stream to the internal Exchange box and the same happens in reverse.

Regards

Michael

-----Original Message-----
From: wellylug-admin at lists.wellylug.org.nz
[mailto:wellylug-admin at lists.wellylug.org.nz] On Behalf Of
andrej at paradise.net.nz
Sent: Tuesday, 17 May 2005 2:15 p.m.
To: wellylug at lists.wellylug.org.nz
Subject: [wellylug] Apache as a proxy for Outpuke's web-interface

Hi Guys,

I need a case study for someone running Apache as a front-end (shielding
exchange from the internet) for staff to be able to access webmail from
home.

I'm aware of the fact that it's next to trivial to set Apache up to do this,
but I need someone as an
*example* to be able to convince my manager :) that there's no need to but
an M$ ISA license to do that ... 


Cheers,
Andrej


--
Wellington Linux Users Group Mailing List: wellylug at lists.wellylug.org.nz To
Leave:  http://lists.wellylug.org.nz/mailman/listinfo/wellylug