The Convergence webmail of the Montpellier academy is based on Oracle’s web communication client. This technical detail changes the game for anyone wanting to properly configure their environment: the supported protocols, the extensions activated on the server side, and the limitations of the interface directly depend on this architecture. Here, we detail the points that public guides overlook.
IMAP, POP, and SMTP Protocols: Technical Configuration of Convergence Webmail
The Convergence platform supports three messaging protocols: IMAP, POP, and SMTP. The choice between IMAP and POP determines the synchronization of your messages across multiple devices.
IMAP keeps emails on the academic server. Each action (reading, deleting, moving to a folder) is reflected on all connected clients. For staff checking their email from a desktop at the rectorate, a laptop at home, and a smartphone, IMAP is the only coherent protocol.
POP, on the other hand, downloads messages locally and may delete them from the server. This mode is suitable only for single-device use, such as a dedicated administrative workstation in DSDEN. We recommend checking the option “keep a copy on the server” if POP is imposed by a local network constraint.
The SMTP parameters for sending are routed through the servers of the Montpellier academy. SMTP authentication requires the same credentials as logging into the portal. A practical guide detailing the initial configuration is available for the Convergence Montpellier webmail for beginners who wish to connect a heavy client like Thunderbird or Outlook to their academic account.
Here are the parameters to be filled in most email clients:
- Incoming IMAP server: the server name is provided in the instructions from the rectorate, along with the dedicated port and SSL/TLS encryption enabled by default
- Outgoing SMTP server: same academic domain, distinct port, mandatory authentication with the identifier @ac-montpellier.fr
- Login identifier: your full address [email protected], never a shortened alias
Convergence Server Extensions: Functions Actually Activated in the Montpellier Academy
The official Convergence help lists several Web 2.0 extensions (advertising, audio/video calls, instant messaging). Not all are activated on every academic deployment. Only the extensions activated on the server side appear in your interface.
Specifically, the Montpellier academy activates messaging, shared calendar, and address book modules. Video calling or online presence functions, documented in the Oracle help, are not necessarily available. If a button does not appear in your interface, it means the corresponding extension has not been deployed on the academic server, not a bug in your browser.
The shared calendar deserves special attention. It allows the creation of events visible to other staff in the academy, provided that sharing rights are configured. Calendar sharing works only between @ac-montpellier.fr accounts, not with external addresses.
Convergence Academic Account Security: Password and Session
The initial password is assigned during account creation by the IT department of the rectorate or DSDEN. Upon first login at the portal webmail.ac-montpellier.fr, the system requires a password change.
We regularly observe account lockouts related to three errors:
- Entering the old password on an outdated mobile client, which generates failed authentication attempts in a loop and locks the account
- Using a browser that auto-fills an outdated password stored in its internal manager
- Logging in from a network that blocks the SSL/TLS ports required by the academic server, causing a timeout mistakenly interpreted as an access denial
In case of a lockout, the reset procedure goes through the academy’s support portal, not through a standard “forgot password” link. No recovery mechanism by personal address is provided: resetting requires validation by the academic IT service.
Session Duration and Logout
The webmail session expires after a defined period of inactivity on the server side. If you leave the tab open without interaction, re-login will be required. On a shared workstation (teachers’ lounge, library), manual logout via the dedicated button remains the only guarantee that the session is truly closed.
Difference Between Academic Webmail and University Messaging in Montpellier
The Convergence account of the academy and the student account of the University of Montpellier are two distinct systems. Online content frequently mixes these two scopes, creating confusion among newly assigned staff.
A researcher affiliated with the University of Montpellier has a university address managed by the university’s IT department. A secondary school teacher assigned to a high school in the academy uses Convergence webmail with an @ac-montpellier.fr address. The two systems do not share directories, authentication, or servers.
A staff member who holds both affiliations (a part-time lecturer at the university and a full-time teacher in a school, for example) must manage two separate accounts, with two distinct passwords and two different interfaces. No automatic redirection gateway exists between the two.
The Convergence Montpellier webmail covers staff from the rectorate, DSDEN, academic inspections, and the Réseau Canopé. Anyone who does not fall under the academy in the administrative sense does not have access to Convergence, even if they work in an establishment located in Montpellier.
