Setting up an email client with an ac-versailles.fr address is not just about entering a username and password. The transition of the Versailles academy to Microsoft 365 has changed the authentication method, the allowed ports, and the required encryption level. This article compares the settings to apply on Outlook and Gmail, identifies compatibility gaps between the two clients, and details the blocking points related to security hardening.
IMAP and SMTP Ports for ac-versailles.fr Email: Comparative Table for Outlook and Gmail
The most common confusion revolves around the choice of SMTP port. Two values coexist in the academic documentation, and their behavior differs depending on the client used. The table below summarizes the documented server settings for the Versailles academy.
| Parameter | Outlook (desktop and mobile) | Gmail (adding account) |
|---|---|---|
| Incoming server | messagerie.ac-versailles.fr | messagerie.ac-versailles.fr |
| Incoming protocol | IMAP | IMAP (via Google) |
| Incoming port | 993 SSL/TLS | 993 SSL/TLS |
| Outgoing server | messagerie.ac-versailles.fr | smtp.ac-versailles.fr |
| Outgoing port | 587 (STARTTLS) or 465 (SSL/TLS) | 587 (TLS) |
| Username | [email protected] | [email protected] |
| Authentication | OAuth2 / Microsoft 365 | Password (limited) |
The key point to remember: port 993 in IMAP with SSL/TLS encryption is the standard on both clients for receiving. Sending, however, diverges.
Outlook accepts both port 465 and 587. In contrast, Gmail enforces port 587 with STARTTLS when adding an external sending address. If you select port 465 in Gmail, sending fails silently, without an explicit error message.
A detailed guide allows you to configure ac Versailles email on Outlook and Gmail by following each step with the correct server settings.
OAuth2 on Outlook vs Simple Password on Gmail: Security Gap
The deployment of Microsoft 365 in the Versailles academy has made OAuth2 authentication mandatory for connections from an email client. This protocol replaces the direct entry of a password with a secure web login window managed by Microsoft.
Outlook, as a Microsoft product, natively supports OAuth2. When adding an ac-versailles.fr account, the software automatically redirects to the academic authentication page. No additional manipulation is necessary.
Gmail does not handle OAuth2 for third-party accounts added via the “Check other email accounts” feature. The interface requests a standard password. With the hardening of academic security rules, clear-text authentication is gradually being blocked on the server side. The result: IMAP connection from Gmail may work one day and fail the next, with no changes on your part.
Practical Consequences Depending on the Client
- On Outlook desktop or mobile, the OAuth2 connection renews automatically. The authentication token expires periodically, but Outlook refreshes it in the background without intervention.
- On Gmail, the lack of OAuth2 for external accounts means that a change in server policy can cut access without warning. Receiving may continue to work while sending via SMTP is already blocked.
- On Thunderbird, OAuth2 support exists but requires manually selecting “OAuth2” in the authentication settings when creating the account, and then recreating the account if an old password-based configuration was in place.
This asymmetry explains why the majority of malfunction reports come from users trying to centralize their academic mail in Gmail.
TLS Encryption and GDPR Compliance on Versailles Academic Email
The issue goes beyond mere configuration convenience. Recent documents from the academy specify that any access to the Versailles webmail from a personal workstation must go through an end-to-end TLS tunnel. Old configurations using unencrypted ports or partial encryption are no longer compliant.
In practice, this means three things for configuring an email client:
- The POP3 protocol, still offered by some tutorials, should be discarded. IMAP is the recommended protocol by the academy, as it synchronizes messages without deleting them from the server, facilitating multi-device access and limiting data loss.
- Old configurations on port 143 (unencrypted IMAP) or port 25 (unencrypted SMTP) must be removed. They not only fail: they transmit credentials in clear text over the network.
- The expected identifier format is the full address [email protected], not the short format (pnom or agent number). An error on this point returns an “unknown identifier” message while the password is correct.
Check Your Existing Configuration
If your ac-versailles.fr email was already configured before the transition to Microsoft 365, the connection may seem to work for receiving while being non-compliant. The client may be using a residual token or a local cache that masks the problem.
To verify, delete the account in your client, then recreate it by explicitly selecting IMAP on port 993 with SSL/TLS and SMTP on port 587 with STARTTLS. On Outlook, choose the account type “Microsoft 365” instead of “Manual IMAP”: this forces the use of OAuth2 from the start.
Redirection from ac-versailles.fr to Gmail: Why It’s No Longer Reliable
Many teachers circumvented client configuration by enabling automatic redirection from the academic webmail to their personal Gmail address. This method worked smoothly for a long time.
Google’s anti-spam filtering rules now frequently classify messages redirected from a third-party domain as suspicious. Emails from the rectorate or academic services end up in Gmail’s spam folder or are silently rejected. Redirection no longer guarantees the receipt of all messages.
The most reliable solution remains to configure Outlook with OAuth2 as the primary client for academic email, and to reserve Gmail for personal exchanges. If the use of Gmail is essential, direct IMAP consultation (as long as it works) remains preferable to redirection, as it at least allows for the detection of missing messages by comparing with the webmail.
The choice of client thus depends less on an interface preference than on a technical constraint: Outlook supports OAuth2, Gmail does not for third-party accounts. This data conditions the reliability of access to academic email in the medium term.