The Convergence webmail of the Academy of Lyon is based on a Zimbra infrastructure adapted to the constraints of the educational network. Access is via https://webmail.ac-lyon.fr, but the authentication chain and the IMAP/SMTP connection settings have specific features that generic guides do not cover. Here we detail the technical points that really cause problems during configuration.
Academic Identifier and Disassociation from Email Address
The first source of error when connecting to the Convergence webmail in Lyon is the disassociation between the email identifier and the email address. The address follows the format [email protected], but the login identifier (the LDAP login) is generally constructed on the model “flastname”: the first letter of the first name followed by the last name.
You may also like : How to Optimize Your Website Structure with an Effective Sitemap
Entering the full email address in the identifier field causes a silent rejection on some email clients. The server exclusively expects the short login. This distinction is not always clearly indicated on the portal’s login page, which explains the majority of support tickets related to authentication.
To retrieve a forgotten identifier, the procedure goes through the academic support service accessible from assistance.ac-lyon.fr. Password recovery via the portal auth.valere.ac-lyon.fr is not activated for academy staff, who must use the dedicated channel. A complete guide on authenticating to Convergence webmail Lyon details each step of this recovery procedure.
You may also like : How to Choose a Good Locksmith to Secure Your Home Effectively
IMAP and SMTP Settings for an External Email Client
Configuring Thunderbird, Outlook, or a mobile client to retrieve an ac-lyon.fr mailbox requires precise settings. The servers do not respond on standard unencrypted ports, and the expected security protocol differs depending on the direction of the flow.
Incoming IMAP Server
- Server address: the IMAP server of the Academy of Lyon handles incoming connections with mandatory STARTTLS encryption. Without enabling STARTTLS, the connection is refused without an explicit error message in most clients.
- Identifier: the short login (flastname), never the full address. Some versions of Outlook attempt to autodiscover the configuration and pre-fill the email address, which causes a failure.
- Password: the academic password, the same as that used for the ENT portal and other academy services.
Outgoing SMTP Server
The SMTP server also requires STARTTLS. We recommend checking that the client is not configured for pure SSL/TLS (port 465), as the academic server expects a STARTTLS negotiation on the dedicated port. Confusing SSL/TLS and STARTTLS remains the most common error during SMTP configuration.
The “sender” field must exactly match the address [email protected]. Any discrepancy between the sending address and the authenticated address triggers a rejection on the server side, a classic anti-spoofing measure on institutional messaging systems.
Password Security and Threat Context on Academic Webmails
Professional messaging systems in the public sector are subject to increasingly targeted phishing campaigns. Recent attacks against French public organizations confirm that phishing remains the primary method for compromising institutional email accounts, with techniques that are becoming increasingly difficult to distinguish from legitimate communication.
On the Convergence webmail, the legitimate login page is found only on the domain ac-lyon.fr. Any login page hosted elsewhere is a phishing attempt. We observe that fake forms closely replicate the Convergence interface, specifically targeting educational staff who are not familiar with the browser’s security indicators.
The strengthening of authentication mechanisms in public systems over recent years has led to increased requirements for password quality. A robust academic password combines at least sufficient length, varied characters, and no reuse on other services. Never use the academic password on a personal site.
Troubleshooting Connection Errors to the Convergence Portal
Several scenarios can cause a blockage during authentication without an explicit error message.
- Error “incorrect identifier or password” even though the credentials are correct: check that the browser has not saved the full email address instead of the short login. Clear the field and manually enter the format flastname.
- Blank page or looping redirection: the browser cache sometimes retains an expired session cookie. Delete cookies from the domain ac-lyon.fr and restart the connection.
- Connection impossible from an external network: some corporate proxies block the ports used by the webmail. A test from a mobile connection can quickly isolate network filtering.
- Expired password after changing it on another academic service: the password is synchronized across all ENT services. After a reset, a propagation delay of a few minutes may explain a temporary rejection.
The academic support portal remains the entry point for cases not resolved by these checks. Staff do not have access to the “lost password” function of the public form visible on auth.valere.ac-lyon.fr.
The daily management of Convergence webmail Lyon does not pose any particular technical difficulties once the initial connection is established. The friction point almost always focuses on the distinction between identifier/email address and the choice of encryption protocol in external clients. Mastering these two parameters avoids the vast majority of blockages.