Past experience: had a setup very similar to the one described at a previous company. Had a similar thing happen: some wank with MCSE and a high-level mgmt. title ('cause they know more about this stuff) decided to sell the company on Ex[machina]change. I left the company when I figured out I couldn't stop them from replacing (yes, replacing) our perfectly fine Unix solution with the M$ pollution (among several other things -- straw that broke the camel-book's binding, as it were). Anyway, a smooth talker can sell ice cubes to Eskimos but _you_ have to deal with the consequences. Adding an Exchange server can be a viable solution if: 1) somebody else is responsible for it (I don't have time to read 600 pages of marketing hype disguised as a manual), and 2) you can put the server on a separate subnet so you neither have to deal with the amazingly increased traffic.
Slashdot Mirror
Past experience: had a setup very similar to the one described at a previous company. Had a similar thing happen: some wank with MCSE and a high-level mgmt. title ('cause they know more about this stuff) decided to sell the company on Ex[machina]change. I left the company when I figured out I couldn't stop them from replacing (yes, replacing) our perfectly fine Unix solution with the M$ pollution (among several other things -- straw that broke the camel-book's binding, as it were). Anyway, a smooth talker can sell ice cubes to Eskimos but _you_ have to deal with the consequences. Adding an Exchange server can be a viable solution if: 1) somebody else is responsible for it (I don't have time to read 600 pages of marketing hype disguised as a manual), and 2) you can put the server on a separate subnet so you neither have to deal with the amazingly increased traffic.
HTH.
The Lewis House