The INRAE messaging system relies on a Microsoft Exchange infrastructure accessible via Outlook or a web browser. When the connection fails, the cause is rarely just the password. Encryption protocols, port settings, expired cookies, or misconfigured multi-factor authentication: each technical layer can block access independently of the others.
TLS Protocols and INRAE Email Clients: The Invisible Breakdown
A common scenario occurs: webmail works from the browser, but Outlook or Thunderbird refuses the connection on the same machine. The usual reflex is to check the password or contact support, while the problem lies with the TLS protocol used by the email client.
Further reading : How to Easily Access Your AMU Email at Aix-Marseille University
When the INRAE infrastructure disables an old TLS protocol to enhance security, any software that does not support the required version silently loses access to the Exchange server. No explicit error message appears in most cases: Outlook simply shows “disconnected” or “incorrect password”.
The check is quick. Just ensure that the email client and operating system are up to date. A Thunderbird or Outlook that has not been updated for several months becomes the weak link, even if the credentials are correct. For a deeper diagnosis, quick solutions on SOS Technologies detail the checks to be made on each workstation.
Read also : Discover how to boost your business with innovative solutions for entrepreneurs
IMAP and SMTP Ports for INRAE Email: Check Server Configuration
Connecting to INRAE email outside of webmail requires two specific ports. Any different value results in either an immediate rejection or a synchronization that fails without a visible alert.
- Port 993 for IMAP with TLS/SSL encryption, used for receiving messages and synchronizing folders
- Port 587 for SMTP with TLS encryption, dedicated to sending emails from a local client
- The name of the Exchange server must exactly match that provided by your INRAE center’s IT department; any typo in the server address generates a certificate error
In Thunderbird, these settings can be found in the account properties, under the “Server Settings” tab. In Outlook, the path is File then Account Settings. A common mistake is to leave port 143 (unencrypted IMAP) or 25 (unencrypted SMTP) inherited from an old configuration. These ports are now blocked by the infrastructure.
Multi-Factor Authentication and Cookies: Two Browser-Related Blockages
Access to INRAE webmail goes through a centralized authentication portal (CAS). This portal stores a session token in the browser cookies. When this token expires or becomes corrupted, the login page loops without ever completing.
The first action to try is to delete the browser cookies, as recommended by the INRAE authentication page itself. In Firefox: Settings, Privacy & Security, then Manage Data. In Chrome: Settings, Privacy, Clear Browsing Data. Targeting only the cookies related to the domain inrae.fr is sufficient, but a complete cleanup also works.
Blocked Multi-Factor Authentication
Multi-Factor Authentication (MFA) adds a layer of verification beyond the password. If the authentication app on the phone is no longer synchronized (phone change, reinstallation, time zone discrepancy), the generated code will be systematically rejected.
Before contacting support, check that the phone’s time is set to automatic mode. A discrepancy of a few minutes between the device and the server is enough to invalidate each generated TOTP code. This point is often overlooked and represents a significant portion of MFA blockages.
Non-Compliant INRAE Password: A Silent Cause of Rejection
The INRAE authentication portal indicates that some passwords do not meet the security rules imposed since the update campaign launched by the institution. An old password, never changed since this campaign, may be accepted on some services but rejected on others.
The behavior is confusing: the VPN connection works, but the webmail rejects it, or vice versa. The reason is that each service applies its own validation policy. The solution is to reset the password via the dedicated portal, adhering to current complexity criteria (length, special characters, absence of dictionary words).
Contacting INRAE Support: The Right Channels When Nothing Works
If none of the previous checks restore access, the INRAE service center can be reached at 01 42 75 96 80, Monday to Friday between 8 AM and 6 PM, excluding public holidays. An email to [email protected] also allows you to open a ticket by specifying the relevant identifier.
The IT team at your center (SIIR) or the IP-PRI of your unit serves as a local relay often faster for issues related to workstation configuration or the site’s Wi-Fi network.
When contacting, specifying three elements speeds up processing: the email client used (Outlook, Thunderbird, webmail), the exact error message displayed, and when the problem occurred (after an update, a password change, a move to another site). A well-detailed ticket reduces the resolution time compared to a vague report.