Lotus cc:Mail
» see lotus.com/ccmail as it lived, on the wayback machine
~ the last words ~
cc:mail's whole life happened in the part of corporate computing that was not visible to me. i was in primary school when cc:mail was at its peak in '93 and '94, and even by the time i was studying computer engineering in turkey in the mid '00s, the universities here used webmail and the companies that had real email infrastructure were already on exchange. honestly, cc:mail is one of those products you have to be a particular age and have worked at a particular kind of u.s. office to remember firsthand. for me it shows up as a name in old it textbooks rather than as a program i ever ran.
cc:mail came out of a small silicon valley startup founded around '84 by robert plummer with hubert lipski and michael palmer, which was first named concentric systems then pcc systems before settling on cc:mail inc as the product became the brand. the architecture was unusual for the time: instead of running a dedicated mail server, cc:mail used a shared file directory on a novell netware server (the "post office") and let each user's client write into and read from that directory directly. that made the system cheap to deploy on the same lan that already had a file server, which was most of corporate america in the late '80s.
the product won the lan-mail category through the late '80s and early '90s on that simplicity. lotus bought the company in 1991 for somewhere around 64 million dollars, then rolled cc:mail into its desktop application suite alongside 1-2-3 and freelance and ami pro and the rest of lotus smartsuite. ibm acquired lotus in june 1995 in a hostile takeover priced at 3.5 billion dollars, mostly to get notes, but cc:mail came along in the same deal. by 1997 the installed base was roughly 14 million seats and cc:mail was the email program a sizable share of american office workers saw when they sat down at their pc each morning.
the death was structural. the shared-file-system mail model that had made cc:mail cheap to deploy did not scale to wide-area corporate networks. microsoft exchange, which shipped in '96 as a proper server with a sql-style message store, was built for the world cc:mail could not handle. lotus's own answer was domino (the notes server), which had been the long-term strategic platform inside lotus since '89, so cc:mail was a doomed bridge product from the moment ibm bought the parent company. development was wound down through the late '90s. lotus pulled the product from the market october 31 2000 with version 8.5 as the last release, formally ended development january 31 2001 and closed the support line exactly a year after withdrawal.
~ the record ~
| Born | mid 1980s as a Concentric Systems product, San Francisco Bay Area |
|---|---|
| Peak | 1997 with about 14 million deployed seats across enterprise LAN deployments |
| Killed | October 31, 2000 withdrawal from the market by Lotus / IBM |
| Lifespan | about 15 years |
| Made by | Robert Plummer with Hubert Lipski and Michael Palmer at Concentric Systems, later Lotus and IBM |
| Killed by | Microsoft Exchange and Outlook winning the post-LAN enterprise mail platform race |
~ what it was ~
the cc:mail client on dos and later on windows had a distinctive ui that anyone who used it in the early '90s remembers. text-mode menus on dos, then a windows version with the familiar lotus icon set. messages were threaded with simple in-reply-to relationships rather than full conversation views. the address book was a flat list per post office, with directory replication between post offices for multi-office companies. file attachments worked but were size-limited, which meant the email-as-document-transport workflow that exchange later normalized was clumsy on cc:mail.
the post-office model was the load-bearing part of the architecture. each post office was a directory tree on a netware volume with a known structure: inbox files, address books, a database of folders. clients on each user's workstation polled that directory for new mail. there was no service running on the server, which was why deployment was so simple. it was also why scaling and security were eventually killers, since every client needed write access to every other user's mailbox file. for late '80s lans where every desktop was already in the same building and connected by token ring, the model worked. by the mid '90s wan it was a liability.
~ the fall ~
exchange shipped in '96 and immediately took the new-enterprise-deal market. the lotus reaction was confused since notes was the long-term mail platform but notes had a different architecture and a different ui, with cc:mail customers not migrating cleanly to it. ibm tried marketing cc:mail and notes as a paired solution for a while, with cc:mail for the low end and notes for the high end, but the message did not land. customers either kept cc:mail running as long as possible on legacy lans, or migrated to exchange in one step and skipped the lotus answer entirely.
the second crack was the internet. cc:mail had been built before smtp was anything anyone in corporate it cared about, since corporate email in the late '80s was lan-internal. by '95 the internet was a real medium, smtp gateways became necessary, and cc:mail's smtp gateway product was a clunky add-on. exchange in '96 had smtp built in. internet mail interop became the defining feature of enterprise mail in the second half of the '90s, and cc:mail's architecture was wrong-shaped for it.
~ the legacy ~
the seat count peaked in '97 and started a slow decline through the rest of the decade. by '99 most large customers had either moved or scheduled a move to exchange. lotus quietly pulled cc:mail off the price list october 31 2000, finalized version 8.5 as the last release and stopped supporting it a year later. the migration tools cc:mail to notes-mail and cc:mail to exchange got a lot of work in '99 and '00 since both lotus and microsoft wanted the seat conversions on their own platforms.
what cc:mail left behind is mostly the memory of an entire generation of office workers' email habits. the addressing convention with two colons that became the visual signature of the product. the post-office file structure that lived on as a migration source for years after the product itself was gone. and the lesson that an email architecture built for one network shape does not survive the next one, which was relearned again with exchange when cloud email arrived and proper exchange installs got replaced by office 365.
~ leave a rose ~
an anonymous tribute. one rose per visitor per day.
@}-->-- ... roses left here
~ leave a wreath ~
a rose fades by morning. a wreath stays on this grave for good, with your name on it.
from $1, paid once through stripe. it keeps the graveyard running: the hosting and the nightly digging. adopt it and the headstone reads "maintained in memory by" you. the groundskeeper plants new wreaths at the next tending, usually within a day.
» one email a week: new graves and the anniversaries of the dead. subscribe
other software: Google Tour Builder, Interleaf, TAURUS, Olive AI
also died in the 2000s: Open Market, Morpheus, Interleaf
~ leave a note ~
visitors before you have left these graveside notes. anonymous welcome.