But that shouldn't stop you from building a linux-based front end <smile>.
Actually, that would be an excellent idea at my company. For a long time, I've wanted to build some sort of Linux-based "first defense" box for my clients. This could also act as a sort of MX backup in case their mail servers went down. The problem, however, is that let's say I took a couple of days to build and configure it (I'm new at this task, so let's say three), there still is no one at my company who cares about Linux. The other day I tried to show an MCSE how to change IP configs (IP, mask, gate) on a CentOS box, and he wasn't at all interested. I just ended up spooling a PDF of what I did and attaching it to the documentation that we use internally for whatever schmuck inherits the project after me. If a Linux solution won't be properly taken care of, then my bias is that it's not the best solution, regardless of how well it works or how much money it saves.
