
Caen Normandy University uses Zimbra as its institutional webmail for the entire community, including students and staff. Accessing this email from a smartphone requires manually configuring several distinct protocols, a reality that the web interface partially masks. The procedure has evolved in recent months, particularly because the historical ActiveSync protocol is being gradually deprecated by the IT department.
Three separate streams instead of one: what the end of ActiveSync changes on mobile
For several years, ActiveSync allowed the creation of a single profile on the smartphone to synchronize Zimbra emails, calendar, and contacts in one operation. This protocol is gradually being abandoned by Unicaen’s IT department, which now directs users towards a configuration with three distinct streams.
See also : Everything You Need to Know About the ADMR Hourly Rate in 2026 and Its Impact on Your Budget
Specifically, this means configuring IMAP for emails, CalDAV for the calendar, and CardDAV for contacts. Each stream requires its own server settings. The gain in reliability and control is real, but the setup requires more manipulation than simply adding an Exchange account.
This evolution is not unique to Caen. Other French universities (Lille, Cherbourg, Montpellier) are following the same trajectory, with documentation that now details the IMAP/CalDAV/CardDAV configuration rather than ActiveSync. A detailed guide on Zimbra Unicaen email on mobile precisely describes the server parameters to be filled in for each protocol.
You may also like : How to use your Kadéos vouchers to shop easily on Amazon
A common pitfall: attempting to add an Exchange/ActiveSync account by reflex. On some recent Android devices, this option still appears in the menus, but the connection fails or degrades after a few days without an explicit error message.

IMAP activation on the ENT side: a often overlooked preliminary step
Several institutions now require an explicit activation of authenticated IMAP/SMTP access before any mobile configuration. Montpellier University, for example, asks its users to go through the ENT, section “Computer Account,” and then manually check a box to unlock IMAP access on smartphones.
The official documentation from Unicaen on docenstock does not mention this step as prominently. Field feedback varies on this point: some users manage to connect via IMAP without prior manipulation, while others report connection failures that are only resolved after checking the digital identity portal.
If the IMAP connection fails while the username and password are correct, checking the status of IMAP/SMTP access in the My Digital Account portal should be the first reflex. This check takes less than a minute and avoids wasting time modifying server settings that are, in fact, correct.
Limiting Zimbra Unicaen synchronization: quota and smartphone autonomy
The general trend in French universities in 2026 is to limit the depth of synchronization on mobile rather than replicating the entire inbox. Several institutions recommend synchronizing only messages from the last two to four weeks.
This limitation has two technical justifications:
- The Zimbra storage quota is shared between webmail and the mobile client. Synchronizing several years of archives saturates the smartphone’s memory and slows down the messaging application without providing any real benefit in daily use.
- The consumption of mobile data and battery increases proportionally to the volume synchronized. A push setting on a large mailbox can cause frequent network awakenings and notably reduce battery life.
- In case of loss or theft of the smartphone, limited synchronization reduces the exposure of university data stored locally on the device.
On both Android and iOS, the synchronization window setting can be found in the mail account settings, usually under the title “Synchronization Period” or “Messages to Synchronize.”
CAS authentication and off-campus connection: blocking cases
Caen University uses the CAS (Central Authentication Service) system as a single sign-on portal. On the webmail accessible via a browser, the connection goes through the CAS page. On mobile, however, authentication is done directly with the username and password of the digital account, without CAS redirection.
This distinction is a source of confusion. The password to be used in the mobile mail client is that of the Unicaen digital account, the same as that used for CAS, but the authentication procedure is not identical. Some mail applications display an “authentication failed” error screen when they attempt to interpret a CAS redirection that does not occur in IMAP.

Connecting from an external network to the campus
IMAP and SMTP access works normally from a home network or a 4G/5G mobile network. No VPN is required for Zimbra Unicaen email outside the campus. However, some internal services (business applications, intranet) may require VPN access, which sometimes creates confusion among users who think that email is also affected.
Differences between iOS and Android for configuring Zimbra Caen
The behavior varies depending on the mobile platform. On iOS, the native Mail app manages CalDAV and CardDAV in an integrated manner: simply adding a CalDAV account in the settings makes the Zimbra calendar appear in Apple’s Calendar app. The setup remains manual, but the integration between applications is seamless.
On Android, the situation depends on the manufacturer and the version of the system. The Gmail app, installed by default on most devices, accepts IMAP accounts without difficulty. For CalDAV and CardDAV, a third-party app often needs to be installed:
- DAVx5 (formerly DAVdroid) is the most documented app by university IT departments for synchronizing CalDAV/CardDAV calendars and contacts on Android.
- The native Samsung Email app handles IMAP but not CalDAV, which requires using DAVx5 as a complement.
- On Pixel devices with stock Android, Google Calendar does not natively support CalDAV, making DAVx5 or an equivalent app essential for the Zimbra calendar.
The configuration of server addresses remains the same regardless of the platform. What changes is the number of applications to configure and whether or not there is native support for each protocol.
Configuring Zimbra Unicaen on mobile in 2026 is not complex in itself, but it requires understanding that three protocols now replace a single one. Once the server addresses are filled in and the synchronization window is adjusted, daily operation remains stable and does not require regular intervention.