Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
Outlook Support for cc:Mail was a legacy MAPI service for connecting older Outlook installations to a Lotus cc:Mail post office—not a feature of modern Outlook or Microsoft 365. Microsoft’s archived guidance covers Outlook 98 and Outlook 2000 in Corporate/Workgroup mode. If you are preserving a working legacy system, the service may help with limited access; for current production use, plan a migration instead.
What “Outlook Support for cc:Mail” meant
In Outlook 98 and Outlook 2000, MS Outlook Support for Lotus cc:Mail was an information service in an Outlook MAPI profile. It let Outlook communicate with a Lotus cc:Mail post office through a translation layer involving Windows MAPI and Lotus Vendor Independent Messaging (VIM). The post office typically lived on a file server, reached through a mapped network drive.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
Microsoft Outlook 365 In Practice | $139.19 | Buy on Amazon |
| 2 |
|
Microsoft Outlook 2016 Step by Step | $33.51 | Buy on Amazon |
| 3 |
|
Microsoft Outlook 2010 | $7.96 | Buy on Amazon |
| 4 |
|
Shelly Cashman Series Microsoft Office 365 & Outlook 2019 Comprehensive (MindTap Course List) | $68.67 | Buy on Amazon |
| 5 |
|
Microsoft Outlook 2010 | $8.99 | Buy on Amazon |
The historical implementation was associated with Transend’s ConnectorWare technology. It was distinct from connecting Outlook to a POP, IMAP, or Exchange account. Microsoft’s archived Outlook 2000 troubleshooting guidance describes the service and its configuration; a 1999 technical overview describes the MAPI-to-VIM arrangement and periodic retrieval of cc:Mail Inbox contents into Outlook Personal Folders. That is not the same as a modern, continuously connected Exchange mailbox or a complete migration.
Free tools Windows power users keep installed
One-click scans. No signup required.
Historical compatibility at a glance
| Component | What the historical evidence supports |
|---|---|
| Outlook 98 and Outlook 2000 | Covered by archived Microsoft documentation for the cc:Mail service. |
| Outlook installation | Corporate/Workgroup (CW) was required; the Internet Mail Only installation was not the documented configuration. Microsoft’s article says “Corporate” should appear in Outlook’s About dialog. |
| cc:Mail DB6 / version 2.x | Identified as supported in Microsoft’s archived Outlook 2000 guidance. |
| cc:Mail DB8 / version 6.x | Not officially supported by Outlook in that guidance. Some configurations could work with additional VIM files and vendor components; this was not equivalent to standard Microsoft support. |
| Current Outlook, new Outlook for Windows, Outlook on the web, and Microsoft 365 | Do not assume compatibility. The surviving cc:Mail instructions concern old Outlook releases, and current Microsoft documentation does not describe this legacy MAPI transport as a supported account connection. |
The current-compatibility conclusion is based on the scope of the archived documentation and the absence of cc:Mail from Microsoft’s current Outlook account-support guidance; it is not a claim that Microsoft published a specific deprecation notice for this service.
#1 Best Overall
How the legacy setup worked
Legacy-only reference: The steps below apply to a deliberately maintained compatible system, not a new Windows or Microsoft 365 setup. Use a backed-up, isolated workstation or virtual machine where possible. Do not install unverified old DLLs on a modern work computer.
Typical prerequisites were:
- Outlook 98 or Outlook 2000 configured as Corporate/Workgroup.
- Access to the cc:Mail server and the correct post-office directory. Microsoft noted that
Ccdatawas a common default folder, but administrators could choose another location. - The cc:Mail user name and password, plus the cc:Mail program directory, historically often
CcmailorLotappsCcmail. - The compatible Lotus VIM and connector components required by that specific installation.
- A backup of the workstation, Outlook profile, and relevant data before changing profiles, files, or the registry.
- Map a drive to the complete network path for the cc:Mail post office, and confirm that the drive is available before Outlook starts.
- In the legacy Outlook Corporate/Workgroup profile, add the MS Outlook Support for Lotus cc:Mail service. The historical configuration path was Tools > Services.
- Open the service’s properties and enter the post-office path, logon name, and password.
- When prompted, identify the installed cc:Mail program directory.
- Start Outlook and test mail retrieval. Test address-book access, bulletin boards, attachments, formatting, and delivery separately; a successful login does not establish that every feature or data type works.
Labels and available options can differ with the old Outlook release and connector version. These are historical paths, not current Outlook instructions.
Troubleshooting a surviving installation
“Could not find the cc:Mail postoffice”
- Check that the server share is reachable and the mapped drive exists before Outlook launches.
- Confirm that the mapping points to the actual post-office directory, not just a parent folder or shortened network path.
- Verify file-system permissions, the configured post-office path, and the cc:Mail program directory.
“Unable to logon to cc:Mail using the information you have entered”
After confirming connectivity and the path, check the spelling of the user name and password and verify that the VIM components match the installed cc:Mail and connector versions. Microsoft’s archived repair guidance mentions the historical registry area HKEY_LOCAL_MACHINESoftwareTransendCcmsvc. It also identifies the Outlook profile area under HKEY_CURRENT_USERSoftwareMicrosoftWindows Messaging SubsystemProfiles<profile name>. These references are for diagnosis on an existing legacy system, not an invitation to delete keys or replace files speculatively.
The same archived article names files including Ccmab32.dll, Ccmdlist.exe, Ccmsvc.cnt, Ccmsvc.hlp, and Ccmxp32.dll; some version 6.x arrangements also involved Export.exe, Import.exe, and Ie.ri. Its references to old VIM packages such as Vdlw32.zip and historical Lotus download locations are archival details, not safe current download recommendations. Obtain legacy binaries only from a trustworthy source and verify provenance and version compatibility. Back up first: Microsoft warns that registry changes can damage the system.
Rank #3
Bulletin boards appear empty
A documented Outlook 2000 failure involved mapping an incomplete UNC path. For example, mapping only \myserver and then using M:myshare could leave bulletin boards empty when the actual share was \myservermyshare. Microsoft’s archived bulletin-board troubleshooting article says to map the drive to the complete UNC share path. A drive letter alone does not guarantee that the connector resolves the post-office path as expected.
HTML arrives as plain text or images become attachments
HTML did not travel reliably through the native cc:Mail transport. Archived Microsoft notes for Outlook 98 and Outlook 2000 describe messages arriving as plain text, with graphics separated into attachments. A conditional legacy workaround was:
Rank #4
- In Outlook, open Tools > Services.
- Select MS Outlook support for cc:Mail, then choose Properties > Delivery.
- Enable Send using Microsoft Exchange rich text format.
This workaround was tested in limited Corporate/Workgroup LAN conditions. The archived guidance did not establish that it works for Internet recipients passing through a cc:Mail gateway. Rich-text/TNEF behavior is therefore not a general HTML fix.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsMissing VIM components or profile problems
Missing or mismatched VIM files can prevent logon or retrieval. A corrupted MAPI profile may also be at fault. Record its settings and back up data before rebuilding the profile or restoring connector files. Registry edits and DLL replacement should be last-resort repairs on a recoverable legacy machine, not first steps on a current computer.
Best Value
Limits that matter before relying on it
- DB8 support was conditional. The Outlook-bundled ConnectorWare 1.2 did not include all VIM DLLs needed for DB8 access. The 1999 technical overview says enhanced DB8 integration was associated with Transend ConnectorWare 3.0 or later; Microsoft’s own archived guidance did not officially support DB8.
- It was not a full mailbox migration. The historical connector periodically copied or synchronized Inbox contents into Outlook Personal Folders; the overview gives an interval of about one minute by default. That does not establish complete server-side folder, calendar, shared-mailbox, or archive synchronization.
- Address books and group data could be incomplete. Personal Address Book access could be unavailable in some bundled configurations, and bulletin boards depended on correct path resolution.
- Formatting and delivery could differ. HTML could be flattened, images detached, and some delivery arrangements still depended on cc:Mail background or router processes.
- The dependencies are obsolete. The system relied on old Outlook, Windows, file-sharing behavior, Lotus components, and third-party binaries. There is no sound basis for treating it as a modern, security-supported production integration.
Should you use it today?
Only consider the old service when you must temporarily operate or inspect a genuine cc:Mail environment and already have a compatible legacy setup. Keep it isolated, backed up, and limited to access, validation, or staged export. It is a poor choice for new Outlook installations, Microsoft 365 production mail, modern authentication requirements, or long-term supportability.
For an organization leaving cc:Mail, plan a migration rather than making the legacy connector permanent. Inventory post offices, users, aliases, archives, address books, bulletin boards, and shared or group data; pilot the export and import; validate metadata and attachments; and retain the original system read-only or offline as needed for audit and recovery.
Migration options and validation
- Specialist migration software or services: Transend remains a relevant vendor name because of the historical ConnectorWare connection, but the current Transend FAQ does not explicitly confirm cc:Mail as a currently supported source. Obtain written confirmation for your exact cc:Mail release, post-office format, export method, and target platform before buying or engaging a service.
- Standard-format export: If your cc:Mail release and export utilities can produce a format accepted by a current platform, test that specific route. Do not assume EML, PST, or another format preserves every cc:Mail feature or metadata field.
- Legacy access plus migration: Preserve a disk image or controlled virtual machine, use it to inspect or validate historical data, and perform the migration separately with a supported method.
- Archive only: If not all historical content needs to become active mailboxes, consider a searchable archive or read-only preservation approach, subject to retention and legal requirements.
Before declaring a migration complete, compare mail counts and folders, dates and time zones, sender and recipient data, attachments, address books, bulletin boards, duplicate handling, searchability, and any retention or legal-hold obligations. Test HTML and inline images explicitly. A connector that can retrieve messages is not proof that a conversion preserved the archive faithfully.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Microsoft’s current instructions for importing EML-based mail into new Outlook are available in its mail and contacts import guidance, but that does not make the old cc:Mail connector compatible with new Outlook; a valid intermediate export is still required.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
