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

[Cliff Pratt]

Michael Dittmer (An Inside Job) wrote:

[Please excuse, I'm not a top-post/bottom-post bigot - I 
just like to follow the thread in *one* direction <grin>]
> 
> -----Original Message-----
> From: wellylug-admin at lists.wellylug.org.nz
> [mailto:wellylug-admin at lists.wellylug.org.nz] On Behalf Of Cliff Pratt
> Sent: Tuesday, 17 May 2005 7:47 p.m.
> To: wellylug at lists.wellylug.org.nz
> Subject: Re: [wellylug] Apache as a proxy for Outpuke's web-interface
> 
> andrej at paradise.net.nz wrote:
> 
>>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 ...
>>
> 
> Why Apache? Why not just a Linux or FreeBSD firewall with ports 25 and 443
> forwarded to the Exchange server.
> 
> Lets see, Anti-Virus and Anti-Spam for Exchange is expensive.
> 
> Also, SSL certs for Exchange can be a pain to get right.
>
In my case I had two Linux boxes in front of the firewall, 
one of which received all mail, and virus and spam checked 
it, and another which acted as a mail router and which sent 
internally destined mail through the firewall to the 
Exchange server. (Really, I only needed one, but the other 
was a historical hangover0.

As far as I recall I had no problem with Exchange and SSL 
certs, but that's a good point.

Cheers,

Cliff