Setting up the acmontpellier webmail on a mobile device requires manually entering the IMAP and SMTP settings. The auto-detection offered by mail applications often defaults to unsecured ports or weak encryption modes, leading to authentication errors or blocked sends. This guide compares the settings based on the system (Android, iOS) and details the most common blocking points.
IMAP and SMTP settings for acmontpellier webmail: comparative table by protocol
The academic messaging system of Montpellier uses the same standards as most French academies, but the exact values of the fields vary. Here are the settings to enter during manual configuration.
| Parameter | Incoming server (IMAP) | Outgoing server (SMTP) |
|---|---|---|
| Server address | imap.ac-montpellier.fr | smtp.ac-montpellier.fr |
| Port | 993 | 465 or 587 |
| Security type | SSL/TLS | SSL/TLS |
| Username | firstname.lastname (academic ID) | firstname.lastname (academic ID) |
| Authentication | Normal password | Normal password |
The IMAP port 993 with SSL/TLS ensures end-to-end encryption for receiving emails. For sending, port 465 works in most cases. Some older Android devices only offer port 587: it remains compatible as long as STARTTLS is selected as the security type.
A often overlooked point: the username is not the complete email address. You must enter only the ID (firstname.lastname), without the suffix @ac-montpellier.fr. Adding the domain will systematically result in an authentication refusal.
For a step-by-step illustrated procedure, you can configure acmontpellier webmail with Info Geeks, which details each input screen on the main mail applications.
Manual configuration on Android or iOS: the differences that change everything
The native mail applications on Android and iOS handle the input of settings differently. These differences explain why a configuration that works on an iPhone fails on a Samsung, and vice versa.
Mail App on iOS (iPhone and iPad)
Apple’s Mail app offers an “Other” field when adding an account. This is the only reliable path for academic messaging. The “Exchange” or “Google” mode attempts auto-detection, which fails with the servers of the Montpellier academy.
- Go to Settings, then Mail, then Accounts, then Add Account, and select “Other”
- Enter the full email address ([email protected]), the password, and then proceed to manual entry
- Enter the IMAP and SMTP settings from the table above, ensuring that the “Host name” field matches the server (imap.ac-montpellier.fr / smtp.ac-montpellier.fr)
- Ignore the certificate warning that sometimes appears during the first connection, then confirm
On iOS, background synchronization is enabled by default. Notifications for new emails arrive in real-time without additional manipulation.
Gmail App or native client on Android
On Android, the Gmail app includes an “Other” mode accessible via Settings, then Add Account. However, some manufacturer overlays (Samsung Email, Huawei Email) offer their own assistant that attempts auto-detection before allowing manual entry.
Force the manual configuration mode from the first screen to prevent the app from testing unsecured ports. On Samsung Email, you must select “IMAP” (and not “Exchange” or “Microsoft 365”) to access the free input fields.
The default SMTP port offered by Gmail is often 587. If sending emails fails with this port, switching to 465 with SSL/TLS resolves the issue in the vast majority of cases.
Authentication errors on Montpellier academic messaging: quick diagnosis
Three situations account for nearly all configuration failures.
The first: the academic password has expired or has been changed without the mobile application being updated. The webmail still works in the browser (cached session), but the mail client refuses the connection. The solution involves the Arena portal or the academy’s account management interface to reset the password, then re-enter it on the mobile.
The second: the “username” field contains the complete email address instead of just the ID. This error is the most common because Gmail and Outlook usually require the full address for personal accounts. For the Montpellier academy, only the ID without the domain is accepted.
The third: the security type is set to “None” or “STARTTLS” instead of “SSL/TLS” for the incoming server. Some Android devices default to “None.” Without encryption, the academy’s IMAP server rejects the connection.
Notifications and synchronization of acmontpellier webmail on mobile
Once the IMAP configuration is complete, receiving emails in the background and real-time notifications work just like for personal messaging. This is one of the concrete advantages of the IMAP protocol compared to simply checking via the mobile browser.
The synchronization frequency can be set in the account settings within the mail application. Synchronizing every 15 minutes is a good compromise between responsiveness and battery consumption. The “push” mode, available on iOS and certain versions of Gmail, offers instant reception but puts more strain on the battery.
The IMAP protocol also synchronizes folders: sent messages, drafts, trash. Everything that is read or deleted on the mobile is reflected on the webmail, and vice versa. This bidirectionality prevents duplicates and messages marked as unread when they have already been processed.
The last point to check after configuration: sending a test email from the mobile to a personal address. If the email arrives, the SMTP server is correctly configured. If sending fails but receiving works, the problem lies exclusively with the outgoing server settings (port or security type).
