Lỗi máy chủ smtp 5.5 1 authentication required năm 2024
|
That was a message from the gmail server. It is talking about the outgoing server which you are using on that particular email address.
on the right you will see a list of your outgoing servers. You should have one for each mail account.
If using:
then use:
If using:
then use:
If this is used by a POP mail account:
If this is used by an IMAP mail account:
Now make sure the gmail account is actually using the correct outgoing server.
See images below as guide. In my case I'm using an imap connection. I only have one gmail email address, so I've left it as 'Google Mail'. But the info would be in the same location even if using pop. I've also included another image of a pop mail account, just to show how I edited the outgoing server to have a Description field to help identify when I had two accounts using same server name. When you have ensured all is correct, click on 'OK' to save and close Account Settings. Exit Thunderbird and allow a little time for background processes to complete. Start Thunderbird. If you still get the error then try loging on to webmail via a captcha. As advised in the info you received. You are trying to send an email or validate your email, and getting the error, “Cannot send mail. The SMTP server requires a secure connection or the client was not authenticated. The server response was: 5.5.1 Authentication Required. Please try again.” This message typically appears if the email or password or both are incorrect. Please re-check them all. This message can also appear if you use Gmail and Google is blocking the sign-in attempts due to Security Standards. In that case, you will need to generate App Password for your Gmail Account to validate the Email. Here’s how: Gmail Help Sign in Google Help
Send feedback on... This help content & information General Help Center experience
Gmail No Authentication Provided Error 503 5.5.1 can occur most explicitly when a user doesn’t provide authentication information that is required by the server. This occurs in situations where the email client is not set to authenticate with the server before sending mail. As a result, the server refuses to accept the request to send the email, which leads to the Error. The second cause mentioned is incorrect username or password. Cabello suggests that the credentials inserted into the email client are different from what the server has saved or demands to enter for authentication . The reason for it could be a recent password change, a typos while setting up the tool, or lack of precision in matching configuration in the email client with the data the server expects to get. Although the credentials used are correct, they should be properly configured in the email client based on the server’s requirements. For instance, some servers only accept authentications while the encryption method such as SSL/TLS is in use, whereas others have security-enabled ports used for logging in securely. When the above configurations are not correctly set up, the server fails to recognize the authentications. Another instance in which an email client might stop working and produce the 503 5.5.1 error code is when the servers update their authentication policies and become more secure. If such a change happens and my settings in the email client are not updated to the new requirements, my previously functional configurations might suddenly stop working and will start resulting in the 503 5.5.1 error. Changes caused by updates to email clients or scripts that automate email sending — whether introduced by bugs or alterations to the configuration due to an error, they might become of hindrance to successful authentication issues. “Blacklist checks” – the tool that checks whether an email address could be potentially blacklisted. Being blacklisted is a significant factor in email deliverability, and identifying this issue in advance will save much of the time and effort that would otherwise need to be poured to remediating a problem like that. |
