I didn't quite realize that at the time, so I set up an Exchange server, moved us all to Outlook, and was happy. Exchange is a lot like chess: relatively simple to learn, but takes a lifetime to master. So, jump forward to 2002 when I was now runing a site about Outlook.
Talk about technology in need of virtual machines, eh? It took four or five physical machines to run this one mail server. The cc:Mail environment ran on DOS (yes, I'm not kidding), and each piece of the mail server (the database, the incoming mail exchanger, the outgoing mail exchanger) needed to run on its own physical server box. Way back then, since I was editing a publication about cc:Mail, I decided to use it for the company mail server. Way back in the mid-1990s, I was the editor of the print newsletter Insider for Lotus cc:Mail, produced by the Cobb Group, an ancestor company of ZDNet sister site TechRepublic. To become familiar with Outlook and Exchange, we moved from Eudora to Outlook.īy the way, this wasn't the first time I did the dogfood thing with our email environment. But when ZATZ decided to add an Outlook-centric site, I thought it would be a good idea to eat our own dogfood. Prior to that, we were actually using the incredibly easy-to-administer Mac-based Eudora mail server, which ran on a Mac. I've been using Exchange since 2002, when I started the OutlookPower Web site. I'll tell you this: it wasn't an easy choice, and for some surprising reasons. In my first two installments, I discussed Microsoft's surprisingly exceptional technical support for Office 365Īnd the questions of when you get the Good Microsoft and when you get the Bad Microsoftīut, until now, I haven't explained why I chose to migrate to Office 365 and not Google Apps. Over the past few weeks, I've been detailing my move from an independent Exchange hosting provider to Microsoft's Office 365 service. Ukrainian developers share stories from the war zone The best Wi-Fi router for your home office 3G shutdown is underway: Check your devices now
0 kommentar(er)
