Global System Services Corporation (GSS) - The leading provider of email and messaging, directory services, and groupware consulting and professional services

I've been following this thread and I've decided to comment. First, I have no intention of defending Lotus on any of the points that Jim and other have brought out. Instead, I'll elaborate on one point in particular: the cc:Mail product line and it's direction.

I don't think the product line itself has stood still so much as the underlying technology certainly has. Since the release of cc:Mail for Windows 1.0 in 1991,there have been many incremental improvements to products, and several new products such as the cc:Mail for UNIX products, cc:Mail for OS/2 Workplace Shell, cc:Mail Mobile for Windows and Macintosh, OS/2 Multisession Router, Link to MHS, cc:Mail View, and cc:Web.

Unfortunately, the underlying technology has remained literally identical. Further, as I think Jim more or less pointed out, there has been quite a bit of bundling, unbundling, repackaging, and re-pricing of existing products without any significant advances in the overall product line. What is more important than the latter point, however, is that all of the problems and limitations in the original DB6 cc:Mail database architecture have been with us for 6 years.

Fortunately, the new cc:Mail database (DB8) finally brings a new generation of technology to LAN-based e-mail. At the same time, however, the industry trend towards client/server products is playing out. Notes R4 is shipping with an all-new, cc:Mail-like messaging system; Microsoft Exchange is about to ship; and Internet-based mail products like Z-Mail and Eudora are rapidly gaining ground, while Internet company's like Netscape threaten to become players in the e-mail arena practically overnight.

Lotus would like to see you migrate either to the new generation of cc:Mail, or to Notes R4. Actually, Lotus will ship cc:Mail-to-Notes migration tools in the cc:Mail R6 timeframe -- Lotus is giving you a clear choice. At the same time, 3rd parties are offering migration solutions to Internet-based mail systems, and there can be no doubt that tools will soon exist for cc:Mail customers to migrate to Microsoft Exchange.

The question is not as simple as the lowest-cost solution, or the technically best messaging system, or the easiest migration path.

Obviously, the easiest migration path is to cc:Mail R6 (DB8). A cc:Mail-to-cc:Mail migration will preserve directory information, configured relationships between post offices responsible for the propagation of directory data and the routing of messages, etc. Migration to the new cc:Mail is also the lowest-cost solution. There's relatively few additional hardware or software resources needed, and no retraining of staff or users. Upgrading to cc:Mail R6 (DB8) is a plug-in solution with that can capitalize on existing back-end equipment while taking advantage of established protocols.

There's also the question of client/server versus file server systems. Although all the major vendors have gone down the client/server road, I think what we saw in the Notes 4 beta and now in the Exchange beta is that client/server systems bring with them their own issues and problems. Client/server systems in LAN environments as strategic technologies have not thus far proved themselves much superior when it comes to messaging. If nothing else, file server based systems are simpler, and that's not necessarily bad.

The original protocol, network, and platform independence of the core cc:Mail technology still has something to offer. Also, the cross-platform data transparency of the cc:Mail system is still viable, although the product line has been weakened substantially by product cancellations and a consistent failure to achieve product and feature parity across platforms. In fact, it seems that Lotus has simply abandoned the cross-platform strategy that led to it's original success. Nevertheless, a server-independent technology that sports interoperability and data transparency across platforms, is still very attractive.

Unfortunately, as I suggested above, the strategic IS picture is not that simple. Customers are also making decisions about desktop operating systems, server platforms, and vendor alliances. Nothing is sacred or beyond reconsideration at this juncture. In my view, Lotus needs to make clear their platform directions for cc:Mail clients, Routers, gateways and agents, as well as their response to the fast-paced developments in the Internet and World Wide Web arenas.

With the popularity of World Wide Web, for example, Internet technology is making new inroads into corporate networks. We know that Lotus intends full adoption of Internet standards for Notes, which now has a strong messaging infrastructure. At the same time, Internet technologies are evolving at a record pace and Internet mail systems promise X.500 directory services, enhanced security, and more in the near future.

I think customers need to know what Lotus' messaging strategy for cc:Mail is before they can choose the right migration path. It goes without saying that the path of least resistance is not necessarily the right path. Ideally, however, Lotus would make it so.