Postby CharlieBrooks » Wed Jul 15, 2009 5:10 pm
Wouldn't it make more sense to put the SWA server behind the firewall, and only allow HTTPS connections incoming to it? Keep your patchlevels up to date on apache and tomcat, get a cheap SSL cert, and you'll be simple, secure and easily maintainable.
If you put the SWA machine outside the firewall, you effectively have more holes in your wall (the holes are virtual if you VPN or CIPE or something, but that really doesn't matter) since the SWA machine needs to talk on more than one port... including the IMAP port which I personally would not open on my firewall. And your overall configuration will be much more complex, and therefore less reliable. I think you will also multiply the traffic through your firewall, since the communication between SWA and a scalix backend seems much bulkier than communication between the user and SWA.
Obviously if you don't keep up with patches on the SWA server you will be vulnerable to attack no matter what you do. A distribution with strong patch management, such as SuSE or Red Hat for example, seems like a good idea.