The Convergence webmail is the professional messaging system used by staff at the Academy of Lyon. Access relies on academic authentication and encrypted protocols. When the connection fails, the usual reflex is to check the password, but the problem often lies elsewhere: in the browser, in the URL used, or in an incorrect identifier format.
Connection denied despite a correct password: the real technical causes
A valid password does not guarantee access to the Convergence webmail. Several technical layers intervene between entering the credentials and displaying the inbox.
The first cause of blockage is the browser cache and expired session cookies. Privacy extensions (tracker blockers, built-in VPNs, anti-fingerprinting modes) interfere with the authentication mechanism. The webmail then loads a blank page or returns a generic error unrelated to the password.
The second cause is the access URL itself. The IT department of the Academy of Lyon has closed unencrypted access. Old HTTP links or shortcuts saved years ago redirect to an error page. Only the HTTPS address (webmail.ac-lyon.fr) still works. An outdated bookmark in the favorites bar is enough to reproduce the problem indefinitely.
The third common trap is the format of the identifier. The login field expects the full academic identifier, not the email address, not the NUMEN, not just the part before the at sign. These three values are distinct, and confusing them leads to an authentication denial that the user mistakenly interprets as a password issue.
When the connection fails repeatedly, it may be useful to consult the detailed solutions for accessing the Convergence webmail of the Academy of Lyon to isolate the exact source of the blockage.
Encrypted IMAPS and SMTPS protocols: settings on a mail client
Configuring the Convergence webmail on third-party software (Thunderbird, Outlook, mobile app) requires precise settings. Unsecured protocols are no longer accepted by the servers of the Academy of Lyon.
Receiving and sending settings
The incoming server uses the IMAPS protocol (IMAP over SSL/TLS). The outgoing server operates exclusively on SMTPS (SMTP over SSL/TLS). Any attempt to connect on unencrypted ports fails without an explicit message in some mail clients, complicating diagnosis.
Three configuration errors occur regularly:
- The encryption type is set to “STARTTLS” instead of the native “SSL/TLS,” causing a timeout or silent rejection of the connection.
- The username entered in the client differs from the academic identifier expected by the server (automatic addition of the domain @ac-lyon.fr by the software, creating a duplicate).
- The port is left at the software’s default value instead of the specific port associated with the SSL/TLS encryption of the academic server.
When the settings seem correct but synchronization does not work, testing the connection via the webmail in a browser first confirms that the account itself is active.
Password reset: a procedure governed by the academy
Recovering a forgotten password on the Convergence webmail does not work like on a public service. No automatic reset via personal email is possible.
The procedure involves identity verification with the institution’s secretariat or academic support. This circuit exists for security reasons: academic accounts provide access to sensitive administrative data (report cards, evaluations, institutional correspondence).
Processing times and contact points
The processing time depends on the period. Outside of peak times (back-to-school, class councils, exam sessions), the reset generally takes a few working days. During these periods, the volume of requests extends the timelines.
There are two entry points to initiate the procedure:
- The institution’s secretariat, which can forward the request to the academic IT department after verifying the identity of the requester.
- The academic IT support, reachable by phone or via a ticket form on the support platform of the Academy of Lyon.
In all cases, having your academic identifier and a document justifying your assignment speeds up the procedure.
Browser cleaning: the action that resolves most blockages
Before contacting support, a targeted cleaning of the browser is sufficient in most situations. The action takes less than two minutes and eliminates the most common technical causes.
Open the browser settings, go to the “Privacy” or “Browsing Data” section, then delete cookies and cache. Targeting the recent period rather than the complete history avoids losing active sessions on other sites.
After cleaning, completely close the browser (not just the tab), restart it, then manually enter the URL in HTTPS. This sequence forces the browser to establish a new clean session with the authentication server.
If the problem persists after this action, temporarily disabling extensions (ad blockers, security extensions) helps determine if one of them interferes with loading the login page.
The Convergence webmail of the Academy of Lyon relies on a strict authentication architecture. Most blockages do not stem from the password but from the local technical environment: cluttered browser, outdated URL, identifier in the wrong format, or poorly configured encryption settings on a third-party client. Checking these four points in order covers nearly all cases before any request for academic support.