When opening a tab to webmail.ac-dijon.fr in private browsing and the page loops without ever displaying the inbox, the issue is neither with the password nor the server. The authentication portal of the Dijon academy relies on a cookie-sharing system between several subdomains, and this mechanism breaks as soon as the browser blocks these cookies.
Understanding this technical point even before entering your username avoids most of the blocks reported by staff.
SSO Cookies and Login Loops on Dijon Webmail
The academic intranet portal (PIA) uses a single sign-on SSO authentication via shared cookies between the ac-dijon.fr subdomains. Specifically, when connecting via pia.ac-dijon.fr, a session cookie is deposited and recognized by webmail.ac-dijon.fr, the ENT, and other services without asking for a password again.
The issue arises in two specific cases. Private browsing deletes cookies upon closing the tab, creating inconsistent sessions. Anti-tracking extensions (uBlock Origin, Privacy Badger) also block these cross-domain cookies by default.
The result is always the same: a redirection loop between the login page and the webmail, or a generic error message that never mentions cookies. To resolve this, you can log in to the Dijon academy webmail by consistently going through the PIA portal rather than using a direct bookmark to webmail.ac-dijon.fr.
- Disable private browsing mode or create explicit exceptions for the ac-dijon.fr subdomains in the content blocker
- Go through pia.ac-dijon.fr and use the “Direct Access” block instead of opening a separate tab to the webmail
- Clear the browser’s cache and cookies if the loop persists, then restart a normal session
Dijon Academic Identifier: format firstname.lastname and special cases
The login identifier follows the format firstname.lastname, now standardized across all academy services (webmail, ENT, ARENA portal). The same username/password pair is used everywhere, simplifying daily management.
The problematic cases are homonyms. When two agents share the same first name and last name, the academy adds a number after the last name (firstname.lastname1, firstname.lastname2). The institution’s secretariat can confirm the exact identifier if there is any doubt.
Initialization with NUMEN or INA code
New staff must initialize their account before any login. The procedure goes through the site id.ac-dijon.fr, where one provides either their NUMEN (for tenured teachers) or their INA code (Agent Numeric Identifier) provided by the secretariat.
One then sets their password. The rules impose a minimum length, special characters, and a mix of uppercase/lowercase letters. The password must be different from that used on personal services since the academic messaging passes through servers managed by the rectorate.
Academic Messaging on Smartphone: IMAP Configuration
The Convergence web interface (or Roundcube depending on the period) works well on a computer, but on a phone, the experience remains limited. Configuring the IMAP protocol on the native mail app of the smartphone provides permanent access to messages without going through the browser.
The parameters to enter in the mail app are as follows:
- Incoming IMAP server: the address provided by the academy, usually on the secure port with SSL/TLS encryption
- Outgoing SMTP server: a distinct address from the incoming server, also with encrypted connection
- Identifier: the same firstname.lastname used on the PIA portal
- Password: the one defined during the account initialization
On iOS, the configuration is done in Settings > Mail > Accounts > Add Account > Other. On Android, the procedure varies by manufacturer, but the path generally goes through Settings > Accounts > Add Account > Email.
Feedback varies on the reliability of push notifications with academic servers. Some staff report a synchronization delay, while others have no issues. Checking that synchronization is set to “push” or on a short interval (every fifteen minutes) improves responsiveness.
Forwarding Emails to a Personal Address: A Misguided Idea
Redirecting academic messages to a Gmail or Orange address seems convenient, but several public email services have tightened their security policies. Emails sent from the ac-dijon.fr servers are sometimes classified as spam or simply not delivered to the personal inbox.
The Dijon Ouest district explicitly discourages this practice. Some emails are no longer forwarded to private messaging due to incompatibilities between security policies. One risks missing an invitation, a meeting report, or information from the rectorate without even realizing it.
The most reliable solution remains to consult the webmail directly via the PIA portal or to configure IMAP access on one’s phone. This way, professional messaging is kept separate from personal messaging, which aligns with the basic rule: professional setting, professional messaging.
For staff using multiple devices, the IMAP protocol synchronizes folders and read messages across all terminals. Deleting an email on the phone also deletes it in the webmail, preventing the accumulation of duplicates generated by automatic forwarding.