The webmail of the Toulouse academy, accessible via the Convergence platform, centralizes the professional exchanges of all staff within the academy. Configuring this mailbox on various devices requires mastering a few specific steps, particularly managing the academic identifier and server settings. Several recurring blocking points arise, and they are not always related to pure technical issues.
Academic Identifier and Temporary Password: What Blocks Before Configuration
The majority of difficulties encountered by users of the Toulouse webmail do not occur when entering IMAP or SMTP settings. They appear earlier, right from the account activation phase.
During the first login, the identifier is based on the NUMEN associated with a temporary password that must be changed via the MaMamia platform. This step requires setting up security questions. As long as it is not completed, any attempt to configure on a third-party mail client (Outlook, Thunderbird, mobile application) fails silently.
Several academies have documented the switch to an identifier of the “pnom” type (first letter of the first name followed by the last name) for the webmail, distinct from the initially used NUMEN. Updated guides in 2026 on the Convergence portals detail this transition. An article dedicated to the Toulouse webmail on Geek Network summarizes the connection and configuration steps adapted to this evolution.
A common pitfall: attempting to configure a mail client with the old NUMEN/temporary password pair. The server refuses the connection without an explicit error message, which wrongly directs one towards a technical settings issue.
IMAP and SMTP Settings for Toulouse Academy Webmail: Stabilized Values
Once the academic identifier is active and the final password is in place, the technical configuration on a mail client relies on two protocols: IMAP for receiving, SMTP for sending.
The server values for the Toulouse academy have been standardized with SSL/TLS encryption. Here are the officially communicated parameters:
- Incoming server (IMAP): convergence.ac-toulouse.fr, port 993, SSL/TLS security, full identifier in the form [email protected]
- Outgoing server (SMTP): convergence.ac-toulouse.fr, port 465 or 587 depending on the client, SSL/TLS security, same identifier
- Authentication required for sending: yes, with the same credentials as for receiving
The choice between port 465 and port 587 for SMTP depends on the client used. Thunderbird generally favors port 587 with STARTTLS. Native mobile applications (Mail on iOS, Gmail on Android) accept both, but port 465 with direct SSL poses fewer compatibility issues in practice.
A Recurring Error on the Username
Some clients require a “username” distinct from the email address. For Convergence Toulouse, the identifier to enter is the full address, not the short login. Entering only “pnom” without the domain @ac-toulouse.fr results in an authentication rejection that the software sometimes attributes to a wrong password.
Mobile Configuration of Toulouse Webmail: IMAP Behavior and Data Consumption
Configuring Convergence on a smartphone introduces a variable that setup guides rarely mention: the default behavior of the IMAP protocol in mobility.
In IMAP, the mail client continuously synchronizes the headers and content of messages with the server. On a Wi-Fi network, this synchronization goes unnoticed. On a limited mobile plan, it can consume data in the background without the user realizing it, especially if the mailbox contains large attachments.
Two settings can help limit this phenomenon:
- Reduce the frequency of automatic synchronization (switch from “push” or “every 15 minutes” to “every hour” or “manual”)
- Disable automatic downloading of attachments, loading them only on demand
- On Android, check in the app settings that mobile data synchronization is not enabled by default
On iOS, the native Mail app correctly manages academic IMAP accounts. On Android, the Gmail app also works, but it sometimes requires going through manual configuration (option “Other”) rather than automatic detection, which does not always recognize the domain ac-toulouse.fr.
Convergence Webmail in a Browser: When the Mail Client is Not Necessary
The question of configuring on a dedicated client deserves to be posed differently: in what cases is the webmail accessible directly via the browser sufficient?
Convergence offers a complete web interface, accessible from any browser at the academic portal address. This interface allows reading, writing, and organizing messages without installing anything. For occasional use or on a shared workstation (teachers’ lounge, library), webmail in the browser remains the safest option since no identifier is stored locally.
The IMAP/SMTP configuration on a dedicated client is justified in two specific cases: managing multiple mail accounts in a single interface, or the need to check messages offline. Outside of these situations, Convergence webmail meets common needs without the risk of misconfiguration.
Security of Identifiers on a Personal Device
Configuring academic messaging on a personal smartphone means that professional identifiers are stored on a device not managed by the institution. In case of loss or theft, immediately change the password via MaMamia to invalidate access from the compromised device. This precaution remains the only measure accessible without intervention from the academic IT service.
Biometric or code locking of the mail app does not protect the identifiers themselves, only access to the interface. This distinction is significant for staff handling sensitive data related to students.
Ultimately, configuring the Toulouse webmail via Convergence relies on two often-overlooked prerequisites: a correctly activated academic identifier and a final password validated on MaMamia. Without these two elements, no technical settings will establish the connection. Once this foundation is in place, the IMAP and SMTP settings work reliably on most current mail clients.