The academic messaging system of Strasbourg relies on the Partage portal, which centralizes authentication for webmail and associated applications. Depending on whether one uses a desktop browser, a smartphone, or a dedicated email client, the login procedure and session retention vary. This article measures these discrepancies, compares the available protocols, and identifies documented bottlenecks.
IMAP and SMTP settings for AC Strasbourg messaging: technical table
The values below, published by academic resources, condition any configuration on a third-party client. Without these exact parameters, the connection fails or generates certificate errors.
| Parameter | Incoming server (IMAP) | Outgoing server (SMTP) |
|---|---|---|
| Server address | imap.ac-strasbourg.fr | smtps.ac-strasbourg.fr |
| Security | SSL | SSL |
| Port | 993 | 465 |
| Identifier | Academic email address | Academic email address |
| Password | Email password | Email password |
The IMAP protocol synchronizes messages between the server and each device. An email read on a smartphone appears as read on the webmail. Ports 993 (IMAP) and 465 (SMTP) are the only ones referenced in the academic documentation.
Generic guides sometimes mention ports 587 or 143. Nothing confirms their compatibility with the Strasbourg infrastructure.
The procedure for logging into AC Strasbourg messaging details the steps specific to the Partage portal, particularly the management of the session token depending on the network used.
Webmail vs IMAP client: session and reliability discrepancies
The academic webmail, accessible via webmail.ac-strasbourg.fr, works without installation on any device with a browser. However, the session expires after a period of inactivity, and a reconnection is required from outside the institution’s network.
An IMAP client (Thunderbird, Mail app on iOS, native Android client) maintains the connection permanently after the initial setup. The IMAP client does not go through the Partage portal for each consultation, which eliminates the repeated entry of credentials.
Concrete differences depending on the device
On a desktop browser, the session token remains active longer. On a smartphone, closing the browser or putting the device to sleep often results in the loss of this token. Mobile webmail then becomes inconvenient for regular consultation.
- On PC via browser, the session persists as long as the token is valid.
- On smartphone via browser, the session is volatile: each return to webmail after sleep may require new authentication.
- On smartphone or tablet via IMAP client, the connection remains active and new message notifications work in the background.
For daily mobile use, the IMAP client offers superior reliability to webmail. Webmail remains relevant as a backup solution on a shared workstation or temporary device.
Configuration on Android and iOS: points of divergence
Both systems accept the IMAP and SMTP settings of the academy. However, the input procedure differs in several respects.
On Android
The Gmail app or native mail client asks for the account type (IMAP), then the server addresses, ports, and security type. Selecting SSL and not STARTTLS for both servers avoids the most common certificate errors. The identifier field must contain the full academic email address.
On iOS (iPhone and iPad)
Apple’s Mail app offers a similar form. After choosing “Other” as the account type, the same parameters need to be filled in. iOS sometimes attempts automatic detection, which fails with academic servers.
Disabling this detection and manually entering imap.ac-strasbourg.fr and smtps.ac-strasbourg.fr remains the most reliable method.
Academic identifier and password: frequent blockages
The email identifier follows the format first.last. In case of homonymy, the academy assigns a distinct identifier to differentiate the concerned accounts. The NUMEN is necessary to set the password during the first login.
After changing the password, providing an alternative email address and a phone number in the account settings facilitates recovery in case of forgetfulness. Without this information, resetting goes through academic support, with variable processing times.
Storage quota and folder management on webmail
The academic mailbox has a limited storage capacity. When the quota is reached, new incoming messages may be rejected. Regularly checking the space used from webmail prevents this situation.
The Partage webmail allows the creation of subfolders and the configuration of automatic sorting filters based on the sender or subject. These filters reduce the risk of saturating the main folder.
- Deleting large messages with attachments after downloading them locally quickly frees up space.
- An automatic archiving filter for recurring administrative messages keeps the inbox readable.
- The trash consumes quota as long as it is not emptied: regularly emptying it is necessary.
IMAP configuration on each device offers synchronized access without moving messages outside the academic infrastructure. For consultation on multiple devices, this method remains the most suitable.
