Akeonet, also known as Akeo, is an Internet service provider that offers its subscribers an email address. Setting up this email account on an email client (Outlook, Thunderbird, mobile application) requires entering specific server settings. Without these values, sending or receiving messages fails, even if the username and password are correct.
IMAP and SMTP Settings for Configuring Akeonet Email
Most guides simply mention that you need to “configure the incoming and outgoing server.” The real bottleneck lies in the choice of protocol, port, and type of encryption.
For receiving messages via IMAP, the server to enter is akeonet.com, on port 993, with SSL/TLS encryption. This protocol synchronizes messages between the server and all devices connected to the same account.
For sending via SMTP, the server is smtp.akeonet.com. Two ports work: 465 with SSL/TLS, or 587 with STARTTLS. If the connection fails on port 465, it is recommended to switch to 587 with STARTTLS. This information, rarely documented in common tutorials, prevents most sending errors.
A summary table helps to find these values at the time of configuration, regardless of the email client used:
| Function | Server | Port | Encryption |
|---|---|---|---|
| Receiving (IMAP) | akeonet.com | 993 | SSL/TLS |
| Sending (SMTP) | smtp.akeonet.com | 465 | SSL/TLS |
| Sending (Alternative SMTP) | smtp.akeonet.com | 587 | STARTTLS |
To access Akeonet mail from a browser, simply go to the webmail interface without any local configuration, but setting it up on a dedicated client remains preferable for daily use.
Akeonet Account Security: Password and Two-Factor Authentication
The technical setup is not limited to servers. Akeonet has strengthened its security requirements, which may be surprising during the initial setup.
During the first login, the initial password must be changed. The new password requires a minimum of 12 characters, combining uppercase letters, lowercase letters, numbers, and symbols. A password that is too simple will be rejected by the system.
Two-factor authentication (2FA) has become standard on Akeonet email. After entering the username and password, a verification code is sent via SMS or generated through an authentication app. This additional step blocks access even if a third party obtains the password.
In practical terms, this means that when configuring the account on an email client, it is sometimes necessary to generate a specific application password, distinct from the main password. This point is almost never mentioned in tutorials, and it causes repeated login failures for users trying to log in with their usual webmail password.
Checks to Perform Before Configuration
- Change the initial password via Akeonet webmail and ensure it meets the 12-character minimum with the four required character types.
- Enable 2FA from the client area, choosing between receiving via SMS or authentication app depending on the reliability of the mobile network.
- Check if the email client used (Outlook, Thunderbird, iOS or Android app) supports application passwords, and generate one if the connection with the main password fails.
Common Errors When Setting Up on Outlook and Thunderbird
Even with the correct settings, some errors persist. Identifying them before starting saves valuable time.
On Outlook, the automatic setup wizard attempts to detect the servers. With Akeonet, this detection often fails. You need to switch to manual configuration and fill in each field (incoming server, port, encryption, outgoing server). Letting Outlook guess the settings usually results in an error like “unable to connect to the server.”
On Thunderbird, the software sometimes defaults to port 143 (IMAP without encryption). This port does not work with Akeonet. You need to force port 993 with SSL/TLS. The same reflex applies to SMTP: Thunderbird may suggest port 25, which is blocked by most ISPs.
Quick Diagnostics in Case of Failure
If the connection fails after entering the correct settings, three checks can help isolate the problem:
- Test the connection to Akeonet webmail directly from a browser: if it works, the problem is related to the email client and not the account itself.
- Check that the local firewall or antivirus is not blocking ports 993, 465, or 587. Some antivirus programs intercept SSL connections and cause certificate errors.
- Ensure that the “username” field contains the full address ([email protected]) and not just the part before the at sign.
The “username” field is the most common source of error. Some email clients do not clearly display what they expect, and an incomplete username is enough to cause authentication to fail.
Mobile Configuration of Akeonet Email on iOS and Android
On smartphones, the configuration uses the same server settings as on a computer. The difference lies in the menus, which vary by system.
On iOS (native Mail app), you need to choose “Other” as the account type, then manually enter the IMAP and SMTP servers. The “Automatically Detect” option does not recognize Akeonet.
On Android, the built-in Gmail app offers an “Other (IMAP)” account addition. The incoming server, port, and security fields appear after entering the address. Selecting SSL/TLS for IMAP and STARTTLS for SMTP (port 587) yields the best results on most recent Android devices.
Once the account is added, the sync frequency can be adjusted. A 15-minute interval is sufficient for regular use without a notable impact on battery life.
Configuring an Akeonet account relies on stable settings, but the recent tightening of security (2FA, password requirements) adds steps that older tutorials do not cover. Keeping the port table handy and checking the exact format of the username remains the most reliable way to avoid issues.
