Zimbra Daffodil (v10)
License
Synacor, Inc., 2026
© 2026 by Synacor, Inc. Zimbra Collaboration Zimbra Connectors Guide
This work is licensed under the Creative Commons Attribution-ShareAlike 4.0 International License unless another license agreement between you and Synacor, Inc. provides otherwise. To view a copy of this license, visit https://creativecommons.org/licenses/by-sa/4.0 or send a letter to Creative Commons, PO Box 1866, Mountain View, CA 94042, USA.
Synacor, Inc., 2026
505 Ellicott Street, Suite A39
Buffalo, NY 14203
US
Choosing a client
You can read your Zimbra Collaboration mail, calendar and contacts in a desktop or mobile application instead of the web client. Which application you use decides which protocol you connect over, and the protocol decides what you can do once you are connected.
This chapter tells you which one to use. The rest of the guide tells you how to set it up and what its limits are.
Which protocol/connector for which platform
| Platform | Use | Applications | Where to look |
|---|---|---|---|
Windows desktop |
Zimbra Connector for Outlook (ZCO) |
Classic Outlook 2021, 2024, 365 |
The ZCO guides. See Zimbra Connector for Outlook on Windows |
macOS desktop |
Exchange Web Services (EWS) |
Outlook for Mac, Apple Mail |
|
iOS and Android |
Exchange ActiveSync (EAS) |
Apple Mail and Calendar, Gmail, Samsung Email, Outlook mobile |
|
Any platform |
IMAP, POP, CalDAV, CardDAV |
Any standard protocol-based client |
Your administrator |
| EAS is also supported on Classic Outlook for Windows but lacks all feature stability. We recommend using ZCO Connector. |
EWS, EAS protocols and ZCO connector are separately licensed or add-on features, and your administrator enables them per account. If a protocol/connector is not enabled for you, setup fails at the sign-in step.
What each protocol/connector gives you
- ZCO Connector
-
Full synchronisation of mail, calendar, contacts and tasks into Outlook on Windows, with delegate access, offline access and S/MIME. It is the richest option, and it is Windows only.
- EWS Protocol
-
Mail, calendar, contacts and tasks for desktop clients on macOS. What you actually get depends on which application you use, and the differences are real. See Supported clients and known limitations before you commit to one.
- EAS Protocol
-
Mail, calendar and contacts on phones and tablets, kept in sync as changes happen. This is the standard choice for mobile.
- IMAP and POP
-
Mail only. No calendar and no contacts. Use these when a client supports nothing better.
- CalDAV and CardDAV Protocols
-
CalDAV syncs calendars and CardDAV syncs contacts with the Calendar and Contacts apps on macOS and iOS. Outlook for Windows requires a third-party synchronizer to use them. Available features vary by client and synchronizer; certain features found in the Zimbra web client or over EWS might not be supported. Additionally, CalDAV has known limitations that can affect calendar synchronization.
Before you deploy
Read Supported clients and known limitations first, particularly if you are moving a group of people onto a client at once. It records what each client does with mail, contacts and calendar, and every limitation that has an open defect behind it.
Two cases catch people out often enough to name here:
-
On macOS, mail and calendar do not necessarily travel over the same protocol. See What you get on macOS.
-
In Outlook on mobile, Free/Busy and the Scheduling Assistant do not work over EAS. See Free/Busy is not available in Outlook on mobile.
Zimbra Connector for Outlook on Windows
ZCO has its own documentation and this guide does not repeat it.
-
ZCO User Guide for installing ZCO, creating an Outlook profile, signing in and using Zimbra features inside Outlook.
-
ZCO Administration Guide for customising the installer, deploying it and troubleshooting.
You can also read about ZCO’s Supported clients and known limitations, so you can compare it against the other protocols in one place.
Exchange ActiveSync on mobile devices
Exchange ActiveSync (EAS) connects the mail application already on your phone or tablet to your Zimbra Collaboration account. Your mail, calendar and contacts stay in sync as changes happen, on the device and on the server.
This chapter covers phones and tablets. For a desktop computer see Choosing a client.
Before you start
Your administrator has to enable EAS on your account. It is a separately licensed add-on feature, so it is not on by default.
You need your email address, your password and, in some cases, the server name. If your administrator has set up autodiscover, the server name is found for you and you are not asked for it.
| If your account uses two-factor authentication, you cannot use your normal password here. Mobile applications have nowhere to show a passcode prompt, so you sign in with an application password instead. See Signing in with two-factor authentication. |
Setting up your device
iOS, Outlook app
-
If the Microsoft Outlook app is not installed, download and install it from the App Store.
-
Launch the Microsoft Outlook app.
-
Add the account:
-
First time: tap Get Started → Add Account.
-
Already using Outlook: tap Home (your initials) → Settings → General → Accounts → Add Account → Email Account.
-
-
Enter your full email address and tap Add Account.
-
Depending on what Outlook detects, follow one of these:
-
If Outlook shows an IMAP screen:
-
Tap Not IMAP? in the top-right corner.
-
Tap Change Account Provider.
-
Select Exchange.
-
-
If Outlook shows a Microsoft 365 sign-in screen:
-
Tap Not Microsoft 365? in the top-right corner.
-
Tap Change Account Provider.
-
Select Exchange.
-
-
-
Enter your account details:
-
Email: your email address
-
Password: your Zimbra password, or your application password if you use two-factor authentication
-
Server: your server name
-
Domain: leave blank unless your administrator tells you otherwise
-
Username: the part of your email address before the @ sign. For
john.doe@example.com, enterjohn.doe
-
-
Tap Sign In.
Outlook verifies the account and starts syncing mail, calendar and contacts.
| Free/Busy and the Scheduling Assistant do not work in the Outlook mobile app. See Free/Busy is not available in Outlook on mobile. |
iOS, Apple Mail
-
Go to Settings → Apps → Mail → Mail Accounts → Add Account.
-
Choose Microsoft Exchange.
-
Enter your Email address and an optional Description such as "Work Account", then tap Next.
-
If autodiscover is set up:
-
Tap Sign In, enter your password and tap Next.
-
Select the services to sync: Mail, Contacts, Calendar.
-
Tap Save.
-
-
If autodiscover is not set up:
-
Tap Configure Manually, enter your password and tap Next.
-
Enter the Server name.
-
Enter your Username, which is your full email address, and tap Next.
-
Select the services to sync: Mail, Contacts, Calendar.
-
Tap Save.
-
Android, Gmail app
-
Open the Gmail app, tap your profile icon in the top-right corner, then tap Add another account.
-
Select Exchange and Office 365.
-
Enter your details:
-
Email: your email address, then tap Next
-
Password: your password, then tap Next
-
Server: your server name, if you are asked for it
-
-
Tap Done.
To open the account, tap your profile icon and select it.
Android, Outlook app
-
If the Microsoft Outlook app is not installed, download and install it from the Play Store.
-
Launch the Microsoft Outlook app.
-
Depending on your current setup:
-
With no accounts configured, Outlook shows an Add Account screen straight away.
-
With an account already configured:
-
Tap the Exchange logo at the top-left to open the side menu.
-
Tap the Settings icon at the bottom-left.
-
Go to General → Accounts.
-
Tap Add Account, then Add an email account.
-
-
-
Enter your email address and tap Continue.
-
When you are asked to choose the account type, select IMAP.
This is a temporary selection so you can reach the advanced options. You switch to Exchange in the next steps. -
On the IMAP settings screen, tap the ? help icon in the top-right corner.
-
Tap Change Account Provider.
-
Select Exchange.
-
Enable ADVANCED SETTINGS.
-
Enter your details:
-
Email: usually pre-filled. If not, enter your email address
-
Password: your password
-
Server: your server name
-
Domain: leave blank unless your administrator tells you otherwise
-
Username: the part of your email address before the @ sign
-
-
Tap the tick icon in the top-right corner to connect.
Outlook validates the configuration and starts syncing mail, calendar and contacts.
| Free/Busy and the Scheduling Assistant do not work in the Outlook mobile app. See Free/Busy is not available in Outlook on mobile. |
Samsung Email
Samsung Email is a supported EAS client. Setup follows the same pattern as the Gmail app: choose an Exchange account type and enter your email address, password and server name.
Autodiscover
Autodiscover lets your device find the server for you, so you enter your email address and password and nothing else.
When it is set up, you are never asked for a server name. When it is not, your device asks, and you enter the name your administrator gives you. Both paths are covered in the setup steps above.
If your device cannot find the server on its own and you have not been given a name, ask your administrator. Setting up autodiscover is a server-side task that involves a certificate and a DNS record, and it is described in the Administrator’s Guide under Supporting Autodiscover.
Signing in with two-factor authentication
If your account uses two-factor authentication, your mobile mail application cannot prompt you for a passcode. You sign in with an application password instead: a password generated for one application, used in place of your normal password.
Generate one from the web client, then enter it in the Password field during setup.
| Resetting your account password revokes every application password. Each device then stops syncing until you generate a new application password and enter it. If every device stops syncing at once shortly after a password change, this is why. |
You can revoke a single application password without affecting the others.
Managing your devices
You manage your own devices from the web client, without asking an administrator.
- Suspend and resume sync
-
Suspends a device. New messages stop arriving on it and the messages already there stay readable. Resume when you want it syncing again.
- Remove a device from your list
-
Removes it. If the device syncs again afterwards, the server makes it fetch the policy again first.
- Remote wipe
-
Erases data from a device you have lost, had stolen, or stopped using.
| Remote wipe is destructive and you cannot undo it. Check which kind of wipe you are issuing before you confirm. A full device wipe returns the device to its original factory settings and erases everything on it, including data that has nothing to do with Zimbra. |
Your administrator can also apply policies that wipe a device, and can allow, block or quarantine devices. If your device will not sync at all and setup looked correct, ask whether it is waiting for approval.
Known limitations
Supported clients and known limitations carries the full list with links. The ones that come up most on mobile are here.
Free/Busy is not available in Outlook on mobile
When you use the Outlook mobile app on iOS or Android with a Zimbra account over EAS, Free/Busy availability is not shown. The Scheduling Assistant is not available when you create a meeting.
This is a limitation of the Outlook mobile app. It shows calendar availability only for Office 365 and Microsoft Exchange accounts, and it makes no Free/Busy request to Zimbra over ActiveSync.
What to use instead
To see Free/Busy and use full scheduling:
-
Use the native calendar app on iOS or Android, which supports Free/Busy over EAS.
-
Use the Zimbra Web Client.
-
Use the Zimbra Mobile App, if it is available in your environment.
We monitor updates from Microsoft and will revise this guidance if the Outlook app extends its support.
Shared calendars in Outlook on mobile
Shared calendar access is currently disabled in the Outlook mobile app because of problems with modify and delete actions. We are working on full support in a future release.
Recurring meetings
Recurring meetings, and single instances changed within a series, are where EAS calendar sync breaks most often. Several defects in this area were fixed in 10.1.21. If you are on an earlier release and see duplicated instances, or a response that does not reach the organiser, check the matrix chapter and then your server version.
Folder permissions and multiple lists
Syncing several contact lists, calendars or task lists over EAS is not supported by every client.
| Only folders you have Admin or Manager permission on can sync. ActiveSync cannot sync a read-only folder, and attempting it causes errors and can lose data. |
Exchange Web Services
Exchange Web Services (EWS) connects a desktop mail application on macOS to your Zimbra Collaboration account. Zimbra acts as the Exchange server, and your application connects to it as an Exchange client.
EWS is a separately licensed add-on feature. Your administrator enables it per account from the Features tab of the admin console, and the Class of Service sections of the Administrator’s Guide describe how. If EWS is not enabled on your account, setup fails when you try to sign in.
Before you start
You need:
-
An active Zimbra Collaboration account with EWS enabled.
-
Your email address and password.
-
Your server name, unless your administrator has set up autodiscover.
What you get on macOS
Which application you use decides what synchronises. The differences are real, and they are the reason to read this section before you choose.
| Application | Contacts | Calendar | Tasks | |
|---|---|---|---|---|
Outlook for Mac (Classic) 2021, 365 |
Yes |
Yes |
Yes |
Yes |
Apple Mail |
Yes, with limitations |
Yes |
See below |
Not verified |
| On macOS, mail and calendar do not necessarily travel over the same protocol. Apple Mail connects over EWS for mail and contacts. The calendar on macOS is a separate application, Apple Calendar, which connects over CalDAV as well as EWS. But EWS with Apple Calendar has known limitations. Read Known limitations for more information. If you are planning a deployment around Apple Mail, plan the calendar separately. |
Outlook for Mac is the fuller client of the two, and it is the one to choose when you want mail, calendar, contacts and tasks in a single application.
Apple Mail is supported and has two open limitations that decide whether it suits you. Read Known limitations before you deploy it to a group.
Setting up Outlook for Mac
-
Open Outlook on your Mac.
-
From the Outlook menu, select Legacy Outlook mode if you are using the new Outlook interface.
-
Go to Settings → Accounts → + → Add an Account.
-
Enter your full Zimbra email address and click Continue.
If you have a Microsoft 365 subscription, Outlook may try to configure the account against Microsoft 365. On the "Connecting to Microsoft 365…" screen, click Not Microsoft 365? in the top-right corner. -
From the list of email providers, select Exchange.
-
Enter the following:
-
Method: select Username and Password
-
Email Address: your email address
-
DOMAIN\username or Email Address: your email address
-
Password: your Zimbra password
-
Server: your server name. Leave this empty if autodiscover is set up
-
-
Click Add Account.
-
When setup finishes, click Done.
Notes
-
If you do not know your EWS server name, ask your administrator.
-
When you are asked for an account type, always select Exchange. Do not select IMAP or Microsoft 365.
-
Recent Outlook versions default to Microsoft services. Use the Not Microsoft 365? link to override this for Zimbra accounts.
Setting up Apple Mail
-
Open Mail.
-
Click Mail → Add Account.
-
Select Exchange.
-
Enter your email address and password.
-
Choose manual configuration.
-
Enter the EWS URL:
https://<zimbra-server>/EWS/Exchange.asmx, replacing<zimbra-server>with your server name. -
In case of multinode, Enter the internal and external URL:
https://<zimbra-server>/EWS/Exchange.asmx, replacing<zimbra-server>with your server name. -
Finish setup and wait for the mailbox to sync.
Your folders and messages appear once the first sync completes.
| Apple Mail does not always find the endpoint on its own. Choosing manual configuration and entering the URL is the reliable path. |
Known limitations
Supported clients and known limitations carries the full list. These are the EWS ones.
Apple Mail: a second account for the same server fails
Adding a second EWS account for the same Zimbra server in Apple Mail fails with the message "This account already exists". One account per server works normally.
This affects anyone who needs a personal and a shared mailbox, or two accounts on one server, in Apple Mail on one Mac.
Apple Mail: messages sharing a Reply-To address
When several messages carry the same Reply-To address, Apple Mail over EWS shows only the first of them. The remaining messages are on the server and are visible in the web client and over IMAP, and they do not appear in Apple Mail.
The effect is that mail appears to be missing when it is not.
Calendar behaviour before 10.1.21
Several EWS calendar defects were fixed in 10.1.21, released in September 2026: invites not syncing between EWS and CalDAV, an attachment missing for an attendee in a changed occurrence of a recurring meeting, and an extra all-day instance appearing on the organiser’s calendar. An all-day meeting created in Apple Calendar showing one day early in the web client was fixed in 10.1.17.
If you are on an earlier release and see any of these, upgrading is the fix.
| Appointments created in Apple Calendar appear correctly in the Zimbra web interface, but appointments created in the Zimbra web interface may not appear in Apple Calendar; this is a known limitation of the Exchange 2010 EWS integration, so please create your appointments in Apple Calendar (or Outlook) if you need them to sync across all devices, and use the Zimbra web interface to view them. |
Outlook for Mac 2019
Outlook 2019 for Mac reached end of life in October 2023 and is not supported. Move to Outlook 2021 or 365.
New Outlook for Mac
New Outlook for Mac is not supported. See Outlook ecosystem and runway.
Supported protocol versions
Zimbra’s EWS implementation supports Exchange 2010-level compatibility. In other words, it acts like an Exchange 2010 server to clients built for Exchange.
Supported clients (macOS)
-
Outlook for Mac (Classic Outlook, Legacy 2021 and 365)
-
Apple Mail (the default macOS Mail app)
Supported clients and known limitations
This chapter records which clients Zimbra Collaboration supports on each protocol, what each one synchronises, and every limitation we know about.
Each entry reads one of:
- Supported
-
Works as described.
- Supported with limitations
-
Works, with a named limitation below.
- Not supported
-
Do not use this combination.
- Not verified
-
We have no test coverage, so we make no claim either way.
The recommendation is ZCO for Outlook on Windows, EWS for Outlook on Mac, and ActiveSync for mobile access on Android and iOS.
| Behaviour in this chapter is verified against Zimbra 10.1.21 unless stated otherwise. Where a limitation was fixed in a specific release, the release is named. On an earlier release you will still see it. |
Windows
| Client | Protocol | Contacts | Calendar | Tasks | Notes | |
|---|---|---|---|---|---|---|
Classic Outlook 2021, 2024, 365 |
ZCO |
Yes |
Yes |
Yes |
Yes |
Recommended for Windows. One Zimbra account per Outlook profile |
Classic Outlook 2016, 2019 |
ZCO |
Deprecated |
Deprecated |
Deprecated |
Deprecated |
Deprecated from October 2025 |
New Outlook for Windows |
none |
Not supported |
Not supported |
Not supported |
Not supported |
|
Outlook for Windows |
EAS |
Not supported |
Not supported |
Not supported |
Not supported |
Microsoft withdrew ActiveSync from this platform. Use ZCO |
Windows 10 and Windows 11 are supported.
ZCO has its own documentation. See Zimbra Connector for Outlook on Windows.
macOS
| Client | Protocol | Contacts | Calendar | Multiple accounts, one server | Notes | |
|---|---|---|---|---|---|---|
Outlook for Mac (Classic) 2021, 365 |
EWS |
Yes |
Yes |
Yes |
Yes |
Recommended for macOS. Also syncs tasks |
Apple Mail |
EWS |
Yes, with limitations |
Yes |
See note |
Coming Soon |
Open limitations mentioned |
Apple Calendar |
CalDAV/EWS |
n/a |
n/a |
Yes |
Not verified |
Calendar on macOS is a separate application |
Outlook for Mac 2019 |
EWS |
Not supported |
Not supported |
Not supported |
Not supported |
End of life since October 2023 |
New Outlook for Mac |
EWS or Graph |
Not supported |
Not supported |
Not supported |
Not supported |
macOS 14 (Sonoma), macOS 15 (Sequoia) and macOS 26 (Tahoe) are supported.
| On macOS, mail and calendar do not necessarily travel over the same protocol. Apple Mail uses EWS for mail and contacts. The calendar is Apple Calendar, which uses CalDAV as well as EWS but with limitations. See What you get on macOS. |
Is Apple Mail supported over EWS?
Yes, but with the limitations mentioned in Known limitations.
This has been stated inconsistently in the past, and this chapter is where the answer now lives. Apple Mail is a client we test against EWS, and it has been listed as supported in published documentation for several years. The limitations mentioned have been open for some time and were not published, which is the gap this guide closes.
If the limitations mentioned in Known limitations matter to your deployment, use Outlook for Mac instead.
Mobile
| Client | Protocol | Contacts | Calendar | Free/Busy | Notes | |
|---|---|---|---|---|---|---|
Apple Mail and Calendar, iOS |
EAS |
Yes |
Yes |
Yes, with limitations |
Yes |
|
Gmail and Calendar, Android |
EAS |
Yes |
Yes |
Yes |
Yes |
|
Samsung Email and Calendar |
EAS |
Yes |
Yes |
Yes |
Not verified |
No setup walkthrough published |
Outlook mobile, iOS and Android |
EAS |
Yes |
Yes |
Yes, with limitations |
Not supported |
No Scheduling Assistant. Shared calendars disabled |
Boxer |
EAS |
Yes, with limitations |
Not verified |
Not verified |
Not verified |
Attachment download is affected |
Android 15 and 16, and iOS 26, are supported.
Autodiscover
| Protocol | Autodiscover | Notes |
|---|---|---|
EAS |
Supported |
Configures an account without a manual server entry when your administrator has set it up |
EWS |
Supported |
Apple Mail does not always find the endpoint. Use manual configuration and the EWS URL |
ZCO |
n/a |
The server is entered during profile creation |
Authentication
| Protocol | Password | Two-factor | Application password | Single sign-on | Certificate |
|---|---|---|---|---|---|
ZCO |
Yes |
Yes, authenticator app or email code |
Not Required, supports TOTP/Email (second factor code) |
Yes |
Yes |
EWS |
Yes |
No |
Yes |
No |
No |
EAS |
Yes |
Application password only |
Yes |
No |
No |
Mobile applications have nowhere to show a passcode prompt, so an account with two-factor authentication signs in over EAS with an application password.
| Resetting your account password revokes every application password, and every device using one stops syncing until it is given a new one. |
Known limitations
Open
| Reference | What you see | Affects | Position |
|---|---|---|---|
ZBUG-2512 |
Adding a second EWS account for the same Zimbra server fails with "This account already exists". One account per server works |
Apple Mail, macOS |
Fix awaiting release |
ZBUG-4722 |
Where several messages share a Reply-To address, only the first appears. The others are on the server and visible in the web client and over IMAP |
Apple Mail, macOS |
Open. The fix would need the server to rewrite message content, which risks altering messages |
ZBUG-5383 |
An attachment is missing in Outlook after a sync while still present in the web client |
ZCO, Windows |
Open, with the engineering team |
ZCS-18204 |
A changed occurrence of an all-day recurring meeting carrying an attachment does not reach the attendee, and the original stays on the organiser’s calendar |
iOS Calendar, EAS |
Open |
ZCS-20055 |
Responding to one instance of an all-day recurring series leaves duplicate instances on the calendar |
iOS, EAS |
Fix awaiting release |
ZBUG-5440 |
Attachments cannot be downloaded |
Boxer, EAS |
Fix awaiting release |
Product behaviour, not defects
| What you see | Affects | Position |
|---|---|---|
Free/Busy and the Scheduling Assistant are not shown. The app makes no Free/Busy request to Zimbra over ActiveSync |
Outlook mobile |
Limitation of the Outlook app. Use the native calendar app, the web client, or the Zimbra Mobile App |
Shared calendar access is disabled |
Outlook mobile |
Disabled because of problems with modify and delete actions. Full support is planned |
Syncing several contact lists, calendars or task lists is not supported by every client |
EAS, varies |
Client-dependent |
Only folders you have Admin or Manager permission on can sync. Read-only folders cannot, and attempting it causes errors and can lose data |
EAS |
Protocol limitation |
EAS is not available |
Outlook for Windows |
Microsoft withdrew ActiveSync from the platform. Use ZCO |
Outlook 2016 and 2019 for Windows are deprecated |
ZCO |
Deprecated from October 2025 |
Outlook 2019 for Mac is not supported |
EWS |
End of life since October 2023 |
Fixed in 10.1.21
These were live issues before 10.1.21, released in September 2026. On an earlier release you will still see them, and upgrading is the fix.
- EWS
-
Invites not syncing between EWS and CalDAV (ZCS-18890). An attachment missing for an attendee in a changed occurrence (ZCS-17716). An extra all-day instance on the organiser’s calendar (ZCS-17714). Sync errors in Outlook for Mac (ZCS-18514).
- EAS
-
Duplicate instances on Android after the organiser changes an occurrence (ZCS-20056). A response message with a blank body whose subject omits the response type on iOS Mail (ZCS-19263). A response to one instance not reaching the attendee’s calendar (ZCS-19878). Invites received through a distribution list auto-accepting on iOS (ZCS-19144). A forwarded instance staying on the calendar after the organiser deletes it (ZCS-17864). Android unable to forward changed instances of a series (ZCS-17801).
- ZCO
-
Attachments not appearing until another is added (ZBUG-3695). Fewer attachments displayed than were sent (ZBUG-5290). No prompt after a password expires (ZBUG-5045).
Fixed in 10.1.17: an all-day meeting created in Apple Calendar showing one day early in the web client (ZCS-17822). Delegated Send settings not applied when sending from Outlook (ZBUG-4853). Forwarded mail appearing distorted through ZCO (ZBUG-5176).
Where problems concentrate
Simple mail sync is reliable across every supported client. Calendar is where these protocols break, and within calendar it is recurring meetings and changed occurrences. Every open calendar limitation above is a recurring-series case. If you are testing before a migration, test recurring meetings with exceptions, and test them on each client you plan to deploy.
Supported protocol/connector versions
| Protocol/connector | Versions supported |
|---|---|
EWS |
Exchange 2010 |
EAS |
16.1 |
ZCO (MAPI) |
ZCO 1952 |
Outlook ecosystem and runway
Microsoft is changing Outlook, and the changes decide which versions of Outlook work with Zimbra Collaboration and for how long. This chapter states our position on each one.
Where the answer depends on a Microsoft decision that has not been made, we say so rather than predict it.
Where each version of Outlook stands
| Surface | Connects over | What Microsoft is changing | Status | Runway |
|---|---|---|---|---|
Outlook on Windows (Classic) |
ZCO (MAPI), plus a COM add-in |
Classic Outlook stays. COM add-ins work in Classic only |
Supported |
At least 2029 |
Outlook on Mac (Classic) |
EWS |
No change affecting on-premises EWS |
Supported |
At least 2029 |
Outlook on Windows (New Outlook) |
Web add-ins only |
No COM add-in support |
Not supported |
No date |
Outlook on Mac (New Outlook) |
EWS or Microsoft Graph |
Graph is closed to third parties |
Not supported |
No date |
iOS and Android mail apps |
ActiveSync |
No change |
Supported |
Ongoing |
Does Zimbra work with New Outlook?
No, on Windows or on Mac using EWS or COM add-ins.
New Outlook drops COM add-ins and supports web add-ins only. The Zimbra Connector for Outlook is a COM add-in, so it cannot load. We investigated whether ZCO could be made to work with New Outlook for Windows and concluded that it cannot.
On Mac, New Outlook connects over EWS or over Microsoft Graph. Graph is a Microsoft interface for Microsoft services, and Microsoft does not open it to third-party mail servers, so there is no route for Zimbra to serve a New Outlook client through it.
Customer demand for New Outlook support is tracked on ZRFE-1808. If Microsoft changes what third-party servers and add-ins can do in New Outlook, we will reassess. That decision is Microsoft’s and we will not forecast it.
Standard protocols like IMAP and POP work with New Outlook on Windows, Mac. But they support very limitied functionalities.
Therefore, we recommend using Classic Outlook with ZCO on Windows, or Classic Outlook for Mac with EWS on macOS.
How long does Classic Outlook last?
Microsoft states that existing installations of Classic Outlook, under both perpetual and subscription licensing, are supported until at least 2029.
Microsoft describes the migration to New Outlook in three stages. New Outlook became the default in April 2026, and users can still switch back to Classic. In the final cutover stage users will no longer be able to switch back, and Microsoft has committed to giving administrators at least 12 months' notice before that stage reaches production.
For a Zimbra deployment this means Classic Outlook remains a supported client for several years, and that New Outlook becoming the default does not by itself break anything, because users can switch back. Plan on the assumption that Classic Outlook is available through 2029, and watch for Microsoft’s cutover notice.
Microsoft is retiring EWS. Does that affect Zimbra?
No.
This is the most common Outlook question we are asked, and it comes from conflating two different things.
Microsoft is retiring EWS in Exchange Online, its cloud mail service. Blocking begins on 1 October 2026 and completes during 2027. Microsoft has stated that the retirement applies only to Microsoft 365 and Exchange Online and that there are no changes to EWS in on-premises Exchange Server.
Zimbra is not Exchange Online. When your Outlook for Mac or Apple Mail client connects over EWS, it connects to your own Zimbra server. Microsoft’s change to its cloud service does not reach it.
EWS on Zimbra continues to be supported. See Exchange Web Services.
Where this leaves you
- Windows
-
Use Classic Outlook with the Zimbra Connector for Outlook. Supported until at least 2029. Do not move users to New Outlook while they need Zimbra in Outlook.
- macOS
-
Use Classic Outlook for Mac via EWS. Check Supported clients and known limitations before choosing Apple Mail instead.
- Mobile
-
Use ActiveSync. Nothing here affects it.
- Watching for change
-
The one Microsoft decision that would change our position is whether New Outlook gains a way for third-party servers and add-ins to work with it. ZRFE-1808 tracks it.
Troubleshooting connection problems
This chapter covers problems setting up a client and keeping it connected. For problems inside Outlook on Windows once ZCO is working, see the ZCO Administration Guide, which has a troubleshooting chapter.
Start here
Before working through a symptom, check three things:
-
Is the protocol enabled on your account? EWS and EAS are separately licensed add-on features and are not on by default. Ask your administrator.
-
Are you on a supported client and version? See Supported clients and known limitations.
-
Is what you are seeing a known limitation? Several behaviours that look like faults are documented in the same chapter, with the release that fixed them where there is one.
Setup fails
Sign-in is rejected and the password is correct
If your account uses two-factor authentication and you are setting up a mobile client, your normal password will not work. Mobile applications have nowhere to show a passcode prompt, so you sign in with an application password. See Signing in with two-factor authentication.
If you are setting up a desktop client, check that the protocol is enabled on your account.
The client asks for a server name and you do not have one
Autodiscover finds the server for you when your administrator has set it up. If your client is asking, it has not been set up, or it is not working for your device.
Ask your administrator for the server name and enter it manually. Every setup procedure in this guide has a manual path.
Apple Mail cannot find the account
Apple Mail does not reliably discover the EWS endpoint on its own. Choose manual configuration during setup and enter the EWS URL:
https://<zimbra-server>/EWS/Exchange.asmx
Replace <zimbra-server> with your server name.
Outlook tries to connect to Microsoft 365 instead
Recent Outlook versions assume a Microsoft account. On the "Connecting to Microsoft 365…" screen, click Not Microsoft 365? in the top-right corner, then select Exchange.
On mobile, Outlook may show an IMAP screen instead. Tap Not IMAP?, then Change Account Provider, then Exchange.
Always select Exchange. Do not select IMAP or Microsoft 365.
A certificate warning appears
A warning that the server certificate is not trusted usually means the server uses a self-signed certificate. You can continue past the warning, and check with your administrator whether you should.
If sync is blocked rather than warned about, the server certificate has expired. That is a server-side problem and your administrator has to replace it.
Adding a second EWS account in Apple Mail fails
Apple Mail reports "This account already exists" when you add a second EWS account for the same Zimbra server. This is a known limitation, ZBUG-2512, and there is no workaround in Apple Mail. Use one account per server, or use Outlook for Mac. See Known limitations.
The device never syncs and setup looked correct
Your administrator may have to approve the device before it can sync. Ask whether device approval is in use and whether your device is waiting for it.
Sync stops working
Every mobile device stops syncing at once
If your account password was reset recently, this is why. Resetting the password revokes every application password. Generate a new application password and enter it on each device.
One device stops after a password change
The client is still offering the old password. Enter the new one. On a mobile device using an application password, generate a new application password rather than entering your account password.
Sync stops and the account looks fine
Check whether sync is suspended. You can suspend and resume a device yourself from the web client. See Exchange ActiveSync on mobile devices.
Mail problems
Messages are missing in Apple Mail
Compare the same mailbox in the web client. If the messages are there and Apple Mail does not show them, and the missing messages share a Reply-To address with one that is visible, this is ZBUG-4722. The messages are safe on the server. Read them in the web client or over IMAP.
An attachment is missing in Outlook on Windows
If the attachment is present in the web client and missing in Outlook after a sync, this is ZBUG-5383, which is open. Download the attachment from the web client.
An attachment cannot be downloaded in Boxer
This is ZBUG-5440. A fix was awaiting release when this guide was written. Check your server version, and use another client for the attachment.
Calendar problems
Calendar is where these protocols break most often, and recurring meetings with changed occurrences are where calendar breaks. Check your server version first. Several calendar defects across EWS and ActiveSync were fixed in 10.1.21.
A meeting appears twice
Responding to one instance of an all-day recurring series can leave duplicate instances on iOS. See Supported clients and known limitations for the current position.
A response to a meeting does not reach the organiser
Responses to a single instance of a recurring series not reaching the organiser’s calendar were fixed in 10.1.21. If you are on an earlier release, upgrading is the fix.
Free/Busy is blank when scheduling
In the Outlook mobile app, Free/Busy and the Scheduling Assistant do not work over ActiveSync, and this is a limitation of the app rather than a fault. Use the native calendar app, the web client, or the Zimbra Mobile App. See Free/Busy is not available in Outlook on mobile.
A shared calendar does not appear on mobile
Shared calendar access is disabled in the Outlook mobile app. Use the native calendar app or the web client.
A shared folder causes errors
ActiveSync cannot sync a folder you have read-only access to.
| Attempting to sync a read-only folder causes errors and can lose data. Only folders you have Admin or Manager permission on can sync. |
Contacts and tasks
Tasks do not synchronise over ActiveSync to every mobile client, and are not verified over EWS for Apple Mail. Check the matrix chapter before assuming a client should be showing them.
What to give support
If you need to raise a case, include:
-
Your Zimbra server version.
-
The client and its version, for example Outlook for Mac 2021 or iOS 18.5 Apple Mail.
-
The protocol: ZCO, EWS or ActiveSync.
-
What you did, what you expected and what happened.
-
Whether it reproduces in the web client. This separates a server problem from a client one faster than anything else.