The Convergence Bordeaux messaging system serves as the daily digital entry point for several tens of thousands of agents in the academy. Email, calendar, address books: the tool centralizes professional exchanges on a web interface accessible from courrier.ac-bordeaux.fr. Behind this familiar facade, several technical peculiarities shape the real experience of users, from the nightly shutdown to mobile synchronization constraints.
Nightly Shutdown of Convergence Bordeaux: A Little-Documented Constraint
The official guides of the academy describe the connection and features without mentioning a point that significantly affects daily practice. The Convergence web interface is shut down every night between midnight and 5 a.m. This scheduled unavailability affects browser access, but it also disrupts certain IMAP synchronizations on mobile devices configured for continuous message retrieval.
For staff who prepare their lessons in the evening or check their messages early in the morning, this interruption window creates a blind spot. An email client installed on a computer (Thunderbird, Outlook) keeps a local copy of already downloaded messages, which mitigates the inconvenience. However, a smartphone configured only for IMAP will be unable to send or receive mail during the maintenance window.
Those looking to understand the Convergence Bordeaux messaging system in detail will find that this time constraint is absent from the official documentation of the rectorate, even though it explains a significant portion of the incident reports on the Amerana platform.
Mobile Access and SSL/TLS Security Settings for Academic Messaging
Configuring Convergence on a phone is not just about entering an address and a password. The Bordeaux academy requires encrypted connections, with no unsecured alternatives. The technical settings to be entered in a mobile client follow a precise scheme.
- Receiving protocol: IMAP on port 993 in SSL/TLS, the only mode accepted by academic servers for reading incoming messages.
- Sending protocol: SMTP on port 465 in SSL/TLS, with mandatory authentication using the full academic identifier (format [email protected]).
- Login identifier: the complete academic email address, not just the short username. A common mistake is to enter only the part before the at symbol, which results in an immediate rejection.
- Password: that of the academic messaging system, changeable via the Macadam tool without going through phone support.
On both Android and iOS, the SSL certificate of the academic server is generally recognized by the built-in certificate stores. If the phone displays a security warning upon the first connection, it often indicates a misconfigured port or protocol setting, not a certificate issue.
Convergence Bordeaux and the Amerana Platform: The Troubleshooting Circuit
When a blockage occurs (expired password, full mailbox, rejected attachment), two paths coexist. The first goes through Macadam, the autonomous password reset utility. The second goes through the shared support platform Amerana, common to the academies of Bordeaux, Limoges, and Poitiers since January 2018.
Amerana can be reached by phone during business hours or online at all times via the academic portal. Authentication on the support portal uses the same credentials as the messaging system. An agent whose password is blocked thus finds themselves in a circular deadlock: unable to log into Amerana online without the password they are trying to reset.
Macadam remains the only autonomous recourse in case of password loss, provided that a personal recovery address or phone number has been previously registered. Without this precaution, contacting phone support at 05 16 526 686 becomes the only option.
Antispam Filtering and Quarantine on the Academic Webmail Bordeaux
The antispam system of the academic messaging intercepts suspicious emails before they reach the inbox. Filtered messages are placed in quarantine, a space distinct from the “Junk Mail” folder visible in the Convergence interface.
The distinction is significant. The “Junk Mail” folder in Convergence receives messages that the local filter classifies as questionable but not dangerous. The quarantine, on the other hand, retains messages blocked upstream by the server, even before their distribution. Staff awaiting a legitimate message that has not been received must check both locations, knowing that the quarantine is not always directly accessible from the web interface depending on the periods.
Precautions Related to Attachments
The academy imposes restrictions on the size and type of attachments allowed. Executable files are systematically blocked. Compressed archives containing certain formats are also intercepted. These rules, rarely detailed in error messages, lead to misunderstandings when a sending fails without a clear explanation on the sender’s side.
Usage Charter and Limits of the Academic Digital Framework
The use of the academic messaging system is governed by a charter regulating the information system, published by the Bordeaux academy. This document reminds that the professional mailbox is reserved for exchanges related to the function performed. Personal use, although marginally tolerated, does not benefit from any additional confidentiality guarantees.
The question of the right to disconnect also arises in this context. The University of Bordeaux has published a guide to good digital practices that recommends separating personal and professional digital lives and organizing work time by incorporating email management. No technical obligation limits the sending of messages outside of business hours, but institutional recommendations encourage delaying non-urgent sends.
The Convergence Bordeaux messaging system fulfills its role as a secure channel for academic exchanges. Its constraints (nightly shutdown, strict mobile configuration, sometimes circular troubleshooting circuit) remain manageable once identified. The point that deserves evolution concerns the transparency of the official documentation regarding these technical limitations, which is still too scattered between the SRASI guide, the usage charter, and the Amerana sheets.
