Support article
The Server Does Not Support the Authentication Methods: Fix
Fix the email server authentication error by reviewing username, password, ports, encryption and SMTP, IMAP or POP3 settings.
What this error means
The message “Your server does not support any of the authentication methods supported by this client” appears when the mail program cannot find a compatible way to identify itself with the server.
It usually happens when sending or receiving messages from applications such as Thunderbird, Outlook, Apple Mail or a mobile mail client. In most cases, the problem is the authentication method, the encryption type, the port or the configured username.
Important check: update your mail client before changing any other settings. Older versions may use protocols and security methods that the server no longer supports.
Why it happens
The most common causes are:
- An incorrect authentication method was selected, such as OAuth2, NTLM, Kerberos or encrypted password.
- The port does not match the chosen security type.
- The username does not contain the full email address.
- The password saved in the program is incorrect or outdated.
- The SMTP server is not configured to require authentication.
- The mail client is outdated and uses old security protocols that the server no longer supports.
- Connection details from another domain or a previous configuration are being used.
How to fix it
1. Update your mail client
This is one of the most important checks. Older mail clients may use encryption protocols and authentication methods that are no longer compatible with the server’s security configuration.
Update Thunderbird, Outlook, Apple Mail or your device’s mail app to the latest available version. Then:
- Close the program completely.
- Restart the device.
- Open the mail client again.
- Try sending and receiving a message.
If you are using an old operating system version, it may also be incompatible with current security protocols. In that case, consider updating the system or testing the account from a newer device.
2. Check the username and password
Verify that the username is, normally, the full email address:
user@yourdomain.com
Re-enter the account password. Do not use the hosting panel access password unless it expressly matches the mailbox password.
You can check the credentials by trying to log in to webmail. If you cannot log in there either, change the email account password from the hosting panel.
3. Review the incoming mail settings
The most common secure settings are:
IMAP
Port: 993
Connection security: SSL/TLS
Authentication method: Normal password
POP3
Port: 995
Connection security: SSL/TLS
Authentication method: Normal password
The server name is usually a host like mail.yourdomain.com, although you should always use the one shown in your service’s setup information or in the hosting panel.
Important: “Normal password” does not mean the password travels unprotected when the connection uses SSL/TLS. The encryption protects the communication between the program and the server.
4. Review the outgoing SMTP mail server
Check that the SMTP server has authentication enabled.
The most common secure combinations are:
Port 465: SSL/TLS
Port 587: STARTTLS
Authentication method: Normal password
Username: full email address
Do not combine port 465 with STARTTLS, or port 587 with direct SSL/TLS, unless the configuration provided for your service indicates otherwise.
5. Change the authentication method
In many mail clients, the error disappears after selecting:
Authentication method: Normal password
Avoid choosing OAuth2, NTLM, Kerberos, GSSAPI or encrypted password, except when the mail service expressly indicates you must use one of those methods.
6. Delete the saved password
The client may keep an old password even if you have entered a new one.
In Thunderbird, you can remove it from:
Settings > Privacy & Security > Saved Passwords
Find the entries related to the account, delete them and try to send or receive mail again. The program will prompt for the password again.
In other clients, delete the saved password or recreate the account if there is no equivalent option.
7. Check the device’s date and time
An incorrect date or time can cause failures when validating the server’s SSL certificate. Enable automatic date, time and time zone settings.
8. Test from another network or device
If the configuration is correct, try temporarily:
- From webmail.
- From another internet connection.
- From another device.
- Temporarily disabling the antivirus mail scanning.
Do not permanently disable the antivirus or firewall. This test is only meant to identify whether either of them is interfering with the connection.
Configuration in Thunderbird
To review the account:
- Open Account Settings.
- Go to Server Settings.
- Check the server, port, SSL/TLS and authentication method.
- Open Outgoing Server (SMTP).
- Edit the server associated with the account.
- Select the correct port and encryption.
- Use Normal password as the authentication method.
- Enter the full email address as the username.
Configuration in Outlook
In classic Outlook for Windows:
- Open the account settings.
- Select the account and go to the advanced options.
- Check the incoming and outgoing mail ports.
- Enable the My outgoing server (SMTP) requires authentication option.
- Select Use same settings as my incoming mail server.
- Review the encrypted connection type.
- Save the changes and test again.
The exact location of these options may vary depending on the Outlook version.
Common issues
Mail comes in, but does not go out
Normally, the SMTP server does not have authentication enabled or uses an incompatible port and encryption combination. Check ports 465 and 587 especially.
Mail goes out, but does not come in
Check the IMAP or POP3 server, the port and the password. Also confirm that the mailbox has not reached its available quota.
Webmail works, but the program does not
The credentials are probably correct. The problem is usually in the server details, the port, the encryption or the authentication method configured in the client.
The password is correct, but the error still appears
The program may be reusing an old password. Delete the saved credentials and enter them again.
The error appeared after changing the password
Update the password on both the incoming server and the SMTP server. Some programs store both credentials separately.
What to do if the problem continues
If the error persists, contact support and provide:
- The affected email address.
- The program and version you are using.
- Whether the error appears when sending, receiving or both.
- The name of the configured servers.
- The ports and encryption types selected.
- A screenshot of the full message.
Never send your password by email or include it in a screenshot.
The miHosting.com support team can help you check your service’s connection details.
Frequently asked questions
Which authentication method should I choose?
For a standard email account, you should normally select Normal password. Use another method only when your service’s documentation expressly indicates it.
Is it insecure to use “Normal password”?
No, as long as the connection is protected with SSL/TLS or STARTTLS. In that case, the communication travels encrypted.
Should I use port 465 or 587?
Both are used for secure SMTP. Port 465 usually works with SSL/TLS and 587 with STARTTLS. Use whichever one appears in your service’s configuration.
Why does webmail work but not Thunderbird or Outlook?
Webmail already knows the server’s internal configuration. An external program needs you to correctly enter the server, port, encryption and authentication.
Do I need to delete and recreate the account?
It is usually not necessary. First check the connection details and delete the saved passwords. Only recreate the account when the configuration is damaged or you cannot modify it correctly.
Conclusion
This error is usually resolved by setting the authentication method to Normal password, using the full email address as the username and matching the port to the encryption type.
Start by updating the mail client, since older versions may use security protocols that the server no longer supports. Then check the saved password, SMTP authentication, ports and encryption type.
If the problem continues, provide support with the configuration details and the full message, but never your password.