| Application | Exchange | Perimeter | SMB | Typo3 |
|---|---|---|---|---|
| Centos | XX | XX | XX | XX |
| Windows 2003 (& AD) | XX | Optional | Optional | Optional |
| Webmin | XX | XX | XX | XX |
| PostFix | XX | XX | XX | XX |
| Shorewall | Optional | XX | XX | XX |
| Dovecot | XX | NA | Optional | Optional |
| Open-Xchange | Not Used | Not Used | Not Used | Not Used |
| OpenGroupware | Not Used | Not Used | Not Used | Not Used |
| eGroupware | Not Used | |||
| Fetchmail | XX | Optional | Optional | Not Used |
| Amavisd | XX | Optional | Optional | Not Used |
| SpamAssassin | XX | Optional | Optional | Not Used |
| ClamAV | XX | Optional | Optional | Optional |
| Apache | XX | XX | XX | XX |
| OpenLDAP | Not Used | Not Used | Not Used | Not Used |
| MySQL | XX | XX | XX | XX |
| DNSmasq | Optional | Optional | Optional | Optional |
| Bind | XX | XX | XX | XX |
Why CentOS
Why no Debian
Why Windows 2003 & Windows Active Directory
Strictly speaking the Shoreline Firewall isn't a firewall. Rather, Shorewall, is a a high-level tool for configuring Netfilter.
Shorewall reads the configuration files that describe your firewall and with the help of the iptables utility, Netfilter to match your is configured to provide what you described.
Shorewall can take advantage of Netfilter's connection state tracking capabilities.