Skip to main content
All CollectionsErrors in Trulyinbox
How to fix SMTP/IMAP "Could not authenticate" error?
How to fix SMTP/IMAP "Could not authenticate" error?
TrulyInbox avatar
Written by TrulyInbox
Updated over a year ago

While connecting your email account using the SMTP and IMAP method, if you come across the error "Could not authenticate", let's see how you can fix this easily:

SMTP / IMAP Error: Could not authenticate

1. Your email address or password is wrong!

In some cases, there are chances that you enter the wrong email ID or password which can lead to this issue. Moreover, if you use a different username for the email account, ensure it is entered correctly and verified by your email service provider.

2. The 2-factor authentication is enabled for the email account.

To know more about 2-factor authentication, check this article: What is two-factor authentication and how to manage it?

To use multifactor authentication, you will need to use an app password in your email settings instead of your regular password. To update the app password, remove the old one and create a new one in your email account settings. Note that the app password does not expire, but your email service provider may stop authenticating it if it has been in use for a long time.

3. Confirm your SMTP/IMAP server address, Port number with your email service provider.

Check your SMTP/IMAP hostname and verify it with the details provided by your email service provider. Moreover, for the port numbers you use, make sure you use the right encryption (SSL | TLS | None) with the details.

Generic port numbers with encryption type for SMTP: 25 (Encryption as "None"), 465 (SSL/TLS), 587 (TLS/None)

Generic port numbers with encryption type for IMAP: 143 (SSL/TLS), 993 (SSL/TLS)

4. Share the error log with your email service provider.

Once you have verified all the settings as configured properly but are still not able to connect your email account, copy the error log by clicking on "Show error log" as shared in the screenshot below, and share it with your email service provider's support team to troubleshoot this further.

Did this answer your question?