Works With Every Email Client Your Team Uses

Validate your exact client builds and workflows before production migration.

This guide describes connection paths for MailSite 11. It is not a certification of every client version or complete Exchange feature parity. Classic Outlook support does not establish support for New Outlook. Confirm your precise client build against the release notes and with Rockliffe before committing to migration.

Current release notes and downloads · MailSite 11 administrator guide · Confirm client-version support

Classic Microsoft Outlook

Connection: MAPI over HTTPS.

MailSite 11 provides email, calendars and contacts through MAPI. Its documented extended features include delegated folder access and administration, out-of-office configuration, free/busy lookup and server-based rules.

Configuration and acceptance checks

  • Record the exact client, operating-system and extension versions. Confirm support for those builds before rollout; this guide does not publish a version-by-version support matrix.
  • Use the documented public endpoint, account permissions and a trusted TLS certificate matching the server name. Validate client discovery where applicable.
  • Test send/receive, attachments, folder operations, calendar invitations and contact changes for the functions your chosen connection supports.
  • Test shared folders, delegated access and calendar permissions separately wherever required. Do not infer these capabilities from basic mail synchronization; confirm limitations for your client and release with Rockliffe.

Product capability details · Deployment requirements

Thunderbird Desktop

Connection: IMAP or EWS for mail; TbSync with ActiveSync for calendars and contacts.

The connection method and required extensions depend on your Thunderbird build. Check that the selected build and extensions support the protocols you intend to use; IMAP alone does not synchronize calendars and contacts.

Configuration and acceptance checks

  • Record the exact client, operating-system and extension versions. Confirm support for those builds before rollout; this guide does not publish a version-by-version support matrix.
  • Use the documented public endpoint, account permissions and a trusted TLS certificate matching the server name. Validate client discovery where applicable.
  • Test send/receive, attachments, folder operations, calendar invitations and contact changes for the functions your chosen connection supports.
  • Test shared folders, delegated access and calendar permissions separately wherever required. Do not infer these capabilities from basic mail synchronization; confirm limitations for your client and release with Rockliffe.

Product capability details · Deployment requirements

macOS Mail, Calendar and Contacts

Connection: Exchange Web Services (EWS).

Evaluate the Mail, Calendar and Contacts applications together. Verify mail delivery and calendar and contact changes in both directions with your macOS release.

Configuration and acceptance checks

  • Record the exact client, operating-system and extension versions. Confirm support for those builds before rollout; this guide does not publish a version-by-version support matrix.
  • Use the documented public endpoint, account permissions and a trusted TLS certificate matching the server name. Validate client discovery where applicable.
  • Test send/receive, attachments, folder operations, calendar invitations and contact changes for the functions your chosen connection supports.
  • Test shared folders, delegated access and calendar permissions separately wherever required. Do not infer these capabilities from basic mail synchronization; confirm limitations for your client and release with Rockliffe.

Product capability details · Deployment requirements

iOS Mail, Calendar and Contacts

Connection: Exchange ActiveSync.

Configure the device for the server’s ActiveSync endpoint. Test mail, calendar and contact changes in both directions, reconnecting after network changes and your device policies.

Configuration and acceptance checks

  • Record the exact client, operating-system and extension versions. Confirm support for those builds before rollout; this guide does not publish a version-by-version support matrix.
  • Use the documented public endpoint, account permissions and a trusted TLS certificate matching the server name. Validate client discovery where applicable.
  • Test send/receive, attachments, folder operations, calendar invitations and contact changes for the functions your chosen connection supports.
  • Test shared folders, delegated access and calendar permissions separately wherever required. Do not infer these capabilities from basic mail synchronization; confirm limitations for your client and release with Rockliffe.

Product capability details · Deployment requirements

Android Gmail

Connection: Exchange ActiveSync.

Verify the device’s Exchange account support and the applications used for calendar and contacts. Client and device versions can expose different synchronization and policy capabilities.

Configuration and acceptance checks

  • Record the exact client, operating-system and extension versions. Confirm support for those builds before rollout; this guide does not publish a version-by-version support matrix.
  • Use the documented public endpoint, account permissions and a trusted TLS certificate matching the server name. Validate client discovery where applicable.
  • Test send/receive, attachments, folder operations, calendar invitations and contact changes for the functions your chosen connection supports.
  • Test shared folders, delegated access and calendar permissions separately wherever required. Do not infer these capabilities from basic mail synchronization; confirm limitations for your client and release with Rockliffe.

Product capability details · Deployment requirements

ExpressPro in a web browser

Connection: HTTPS.

ExpressPro provides a browser workspace for mail, calendars and contacts. Test the browser versions, permissions and workflows your organization will deploy.

Configuration and acceptance checks

  • Record the exact client, operating-system and extension versions. Confirm support for those builds before rollout; this guide does not publish a version-by-version support matrix.
  • Use the documented public endpoint, account permissions and a trusted TLS certificate matching the server name. Validate client discovery where applicable.
  • Test send/receive, attachments, folder operations, calendar invitations and contact changes for the functions your chosen connection supports.
  • Test shared folders, delegated access and calendar permissions separately wherever required. Do not infer these capabilities from basic mail synchronization; confirm limitations for your client and release with Rockliffe.

Product capability details · Deployment requirements

Start a trial · Plan migration and rollback