
Setting up the Zimbra messaging system of the Créteil academy on a smartphone raises a specific technical question: which protocol, which port, and which type of encryption ensure reliable synchronization without losing messages? The settings vary depending on the phone’s operating system, and an error in just one field is enough to block the connection.
This guide compares the configurations for iOS and Android, details common blocking points, and highlights recent developments that render some older tutorials obsolete.
Read also : How to Effectively Use Coffee Grounds to Keep Woodlice Away from the Garden
IMAP Protocol and Secure Ports: Technical Settings to Know
The first step before adjusting the phone settings is to identify the exact server values. Academies using Zimbra now require SSL/TLS encryption for all mobile access. Two receiving protocols coexist, but only one is worth keeping for smartphone use.
| Parameter | IMAP (recommended) | POP |
|---|---|---|
| Multi-device synchronization | Yes, messages remain on the server | No, the message is downloaded and then deleted from the server by default |
| Secure incoming port | 993 (SSL/TLS) | 995 (SSL/TLS) |
| Outgoing SMTP port | 465 (SSL/TLS) | 465 (SSL/TLS) |
| Retention of Zimbra folders | Yes, synchronized hierarchy | No, only the inbox is read |
IMAP keeps messages on the server and synchronizes all Zimbra folders (sent, drafts, trash). A teacher checking their emails on their phone in the morning finds the same structure on the webmail in the afternoon. With POP, the message disappears from the server as soon as it is retrieved on the device.
See also : The practical guide to collecting and successfully processing driftwood
For those who want to set up the Zimbra messaging system of the Créteil academy without trial and error, choosing IMAP on port 993 with SSL enabled eliminates most of the connection errors encountered by colleagues.

Zimbra Créteil Configuration on iPhone and iPad: Screens and Fields to Fill Out
On iOS, the path goes through Settings, then Mail (or Passwords & Accounts depending on the version), and finally Add Account. The reflex would be to choose Exchange, since Zimbra supports the ActiveSync protocol. In practice, the IMAP account remains more stable on iOS for academic servers, as ActiveSync sometimes requires a server-side license that not all academies activate.
Fields to Complete on iOS in IMAP
- Address: your full academic identifier ([email protected]). This is also the username requested later.
- Incoming server: enter the academy’s IMAP server, port 993, with SSL security enabled. The password is the same as your usual webmail authentication.
- Outgoing SMTP server: same server domain, port 465, SSL enabled, with identical authentication (same username and password).
Once the fields are validated, iOS attempts an automatic verification. If it fails, check that the “username” field contains the full address and not just the firstname.lastname without the domain.
Zimbra Créteil Configuration on Android: Differences from iOS
Android offers two paths depending on the application used. The built-in Gmail app manages third-party IMAP accounts. The manufacturer’s native mail app (Samsung Email, for example) sometimes offers an assistant that automatically detects servers, but often fails with academic domains.
Favoring manual configuration on Android prevents the assistant from filling in incorrect default values. In Gmail, choose “Other” when adding the account, then IMAP, and fill in the same fields as on iOS.
Main Divergence Point
On some versions of Android, the security field offers “SSL/TLS” and “STARTTLS” in a dropdown menu. For the academic messaging system of Créteil, select SSL/TLS and not STARTTLS. STARTTLS first attempts an unencrypted connection before switching, which may be rejected by the Zimbra server configured to require encryption from the start.
The SMTP port remains identical between the two systems: 465 with SSL. There is no difference in settings on the sending side.

Webmail URL and Evolution of Academic Servers
Several academies have changed their webmail URLs in recent years to align with regional mergers. The Normandy academy, for example, switched from webmail.ac-rouen.fr to webmail.ac-normandie.fr. This type of migration makes screenshots from older tutorials misleading: the server address displayed no longer corresponds to reality.
For Créteil, checking the webmail URL directly on the academic DSI website before configuring the phone remains the most reliable precaution. If the URL has changed, the associated IMAP server has likely changed as well. An old configuration that worked may stop functioning overnight after a migration.
Common Connection Errors and Quick Diagnosis
Three situations concentrate the majority of the blocks reported by users of the academic messaging system.
- Incomplete identifier: the “username” field must contain the full address with @ac-creteil.fr. Many only enter the part before the @ symbol, which causes an immediate authentication refusal.
- Incorrect port or encryption disabled: a port 143 (non-secure IMAP) or 587 (SMTP STARTTLS) will be rejected if the Zimbra server requires SSL from the connection.
- Expired password: academies enforce renewal policies. An expired password on the webmail is also expired on mobile, but the error message displayed by the mail application does not always specify this.
The quickest diagnosis is to first test the connection to the Zimbra webmail from a browser. If authentication works with the same username and password, the problem lies in the mobile settings. If it also fails in the browser, the issue is on the account side (password, lockout, ongoing migration).
Ultimately, the mobile configuration of Zimbra for the Créteil academy comes down to a few correctly filled fields: full address, IMAP 993 SSL, SMTP 465 SSL, and an up-to-date password. The rest is handled by the server.