When a teacher from the Toulouse academy tries to add their Convergence account on a smartphone, the blockage rarely occurs at the password stage. The problem is more often found in the encryption settings or in a poorly formatted identifier. This guide covers the exact settings, common errors, and points of caution specific to the academic messaging system of Toulouse on mobile.
Convergence Toulouse Authentication: the Identifier Format that Blocks
The majority of connection failures on mobile stem from confusion about the identifier to enter. On the Convergence webmail, accessible via a browser, the connection often works with the shortcut firstname.lastname. On a mobile email client (Gmail, Outlook, Apple Mail), this shortcut is not always sufficient.
Several field reports indicate that the full address [email protected] must be entered in the identifier field of the mobile client, including for the outgoing SMTP server. Using only the short login (without the domain) causes a silent error: the application shows “connected” but sends or receives nothing.
Before any technical manipulation, one must also have activated their account via the Arena portal or the identity management tool of the academy. Without this prior activation, the configuration on mobile fails or remains in a synchronization loop, even if the entered settings are correct. To configure the academic messaging system of Toulouse smoothly, this verification is the true starting point.
IMAP and SMTP Settings of the Toulouse Academy: Ports and Encryption
The academies that have switched to Convergence now use a secure IMAP protocol. Here are the settings to enter for an academic email account from Toulouse on mobile:
- Incoming server (IMAP): imap.ac-toulouse.fr, port 993, SSL/TLS encryption
- Outgoing server (SMTP): smtp.ac-toulouse.fr, port 465 with SSL/TLS or port 587 with STARTTLS depending on the email client used
- Identifier: full academic address ([email protected])
- Password: that of the Convergence account, the same as used on the webmail
Encryption is mandatory. Unencrypted ports (143 for IMAP, 25 for SMTP) no longer work. If your email application offers “None” or “No security” in the encryption type, the connection will be refused by the academic server.
Difference between SSL/TLS and STARTTLS on Mobile
On port 465, the connection is encrypted from the start (SSL/TLS). On port 587, the connection starts unencrypted and then switches to encrypted via STARTTLS. Both work, but port 465 with SSL/TLS causes fewer problems on recent Android and iOS clients.
Some applications (notably the Gmail app on Android) only offer “SSL/TLS” in their dropdown menu, without a distinct STARTTLS option. In this case, staying on port 465 avoids any ambiguity.
Common Connection Errors to ac-toulouse Messaging on Smartphone
Once the settings are entered, several situations can still block synchronization. They are not all related to a typing error.
The Unrecognized Security Certificate
On some older Android phones or those whose system has not been updated, the SSL certificate of the server ac-toulouse.fr may not be recognized. The application then displays a security warning. Manually accepting the certificate allows you to continue, but the long-term solution remains to update the phone’s operating system to have up-to-date root certificates.
The Synchronization Loop
This problem occurs when the account has been added without prior activation on the academic portal, or when the password has expired. Convergence imposes periodic password renewal, and expiration is not always clearly indicated on mobile. The webmail displays an explicit message, while the mobile client just keeps spinning endlessly.
Empty Inbox Despite a Successful Connection
If the application indicates that the account is connected but displays no messages, the default selected IMAP folder is likely incorrect. Some email clients create a local “Inbox” folder instead of pointing to the server’s “INBOX” folder. Checking the folder settings in the account settings resolves the issue in most cases.
Convergence Toulouse Webmail: When the Mobile Browser Suffices
Configuring a native email client is not always the best option. The Convergence webmail, accessible from the smartphone’s browser, offers direct access to the inbox without IMAP or SMTP setup.
This approach has a concrete advantage: no email data is stored locally on the phone. For a personal device also used by other household members, this is a significant security point. In case of loss or theft, no academic messages are found on the device.
The limitation of mobile webmail lies in notifications. Without a configured native application, the phone does not signal the arrival of new messages. You must open the browser and reconnect manually. For occasional use (one-time consultation, responding to an urgent message during vacations), webmail is sufficient. For daily follow-up, IMAP configuration remains more practical.
Security of Academic Identifiers on a Personal Device
Adding a work account on a personal smartphone raises a question rarely addressed in tutorials: the separation between personal and professional data.
On Android, the “work profile” feature (available via Android Enterprise) allows for isolating the academic account in a contained space. On iOS, MDM configuration profiles offer similar isolation, but their deployment depends on the academy.
Storing the academic password in the personal browser’s password manager is not recommended. If the browser synchronizes passwords with a personal Google or Apple account, the academic identifier ends up stored on third-party servers, outside the scope of the National Education.
The best practice is to use a dedicated password manager or, if not possible, to avoid checking “remember password” when logging into webmail from the mobile browser. This detail may seem trivial, but it determines whether your identifiers remain under your control or not.