{"id":3875,"date":"2024-05-01T12:59:24","date_gmt":"2024-05-01T12:59:24","guid":{"rendered":"https:\/\/www.warmy.io\/blog\/how-to-fix-smtp-email-error-534-solved\/"},"modified":"2026-07-21T08:01:14","modified_gmt":"2026-07-21T08:01:14","slug":"how-to-fix-smtp-email-error-534-solved","status":"publish","type":"post","link":"https:\/\/www.warmy.io\/blog\/how-to-fix-smtp-email-error-534-solved\/","title":{"rendered":"SMTP Error 534: How to Fix It [SOLVED]"},"content":{"rendered":"\n<p><strong>TL;DR: <\/strong>SMTP Error 534 means the receiving server rejected your login credentials during SMTP authentication, almost always because Gmail, Outlook, or Yahoo now require an app password or OAuth instead of a plain password. Update your email client with the correct password type and current SMTP settings for your provider, and the error clears immediately. If it persists, the account itself may be locked, restricted, or temporarily unreachable.<\/p>\n\n\n\n<p>Errors involving <a href=\"https:\/\/www.warmy.io\/blog\/what-is-smtp-and-how-does-the-smtp-server-work\" target=\"_blank\" rel=\"noopener noreferrer\">SMTP<\/a> emails can be detrimental to communication and the reliability of digital messages, and as such, it is vital to resolve them as quickly as possible. The Simple Mail Transfer Protocol is used by all email systems to send messages from one server to another.<\/p>\n\n\n\n<p>An error in the SMTP prevents emails from being delivered to their intended destinations and could cause a communication breakdown, potentially resulting in a setback in your business. Understanding and solving SMTP errors is crucial because they have a high impact on the dependability and efficiency of email services. This article specifically focuses on the SMTP Email Error 534, and we will provide a thorough explanation of what might have caused this problem, as well as a detailed process on how to solve it.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Decoding SMTP email error 534<\/h2>\n\n\n\n<p>SMTP Email Error 534 happens when the email client or server\u2019s authentication mechanism fails to validate the user\u2019s credentials during the SMTP authentication procedure. This issue frequently appears as a notice indicating that the authentication attempt was unsuccessful, preventing the email from being delivered successfully.<\/p>\n\n\n\n<p>Users may encounter error messages similar to the following:<\/p>\n\n\n\n<p>\u2013 \u201cSMTP Error (534): Authentication failed.\u201d<br>\u2013 \u201cError 534: 5.7.14 Please log in via your web browser and then try again.\u201d<br>\u2013 \u201cAuthentication unsuccessful. Error code: 534.\u201d<\/p>\n\n\n\n<p>These messages typically appear when attempting to send emails through email clients like Outlook, Thunderbird, or mobile email apps, indicating a failure to authenticate the user\u2019s account with the SMTP server. Resolving this error involves identifying and addressing the underlying authentication issues to ensure successful email transmission.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Identifying common causes of SMTP email error 534<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Authentication Issues<\/h3>\n\n\n\n<p>Incorrect or obsolete login credentials might cause authentication problems, resulting in Error 534. This frequently happens when users enter wrong usernames, passwords, or security tokens when attempting to send emails.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Security Settings<\/h3>\n\n\n\n<p>Security mechanisms employed by email clients or servers, such as two-factor authentication or app-specific passwords, might occasionally interfere with SMTP authentication operations, resulting in Error 534.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Server Configuration Problems<\/h3>\n\n\n\n<p>Misconfigured SMTP servers may deny email clients\u2019 authentication attempts, resulting in Error 534. Issues including erroneous SSL\/TLS certificates, incorrect SMTP port settings, and blacklisted IP addresses can all contribute to authentication difficulties.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Firewall or Antivirus Interference<\/h3>\n\n\n\n<p>Excessively restrictive firewall settings or aggressive antivirus software may block SMTP communication, preventing successful authentication and returning Error 534.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Network Connectivity Issues<\/h3>\n\n\n\n<p>Unstable or inconsistent internet connections can impair communication between email clients and SMTP servers, resulting in authentication failures and error 534.<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p><strong>Pro Tip: <\/strong>Before changing any passwords, send a test email and read the full bounce-back message. The extended code after \u201c534\u201d (for example \u201c5.7.14\u201d or \u201c5.7.9\u201d) tells you whether Gmail, Outlook, or Yahoo is asking for a browser sign-in, an app password, or a different authentication method, so you fix the right thing on the first try.<\/p>\n<\/blockquote>\n\n\n\n<h2 class=\"wp-block-heading\">Detailed solutions for resolving SMTP email error 534<\/h2>\n\n\n\n<p>SMTP Email Error 534 requires particular changes to authentication settings and configurations in popular email providers such as Gmail, Outlook, and Yahoo. The following are step-by-step instructions for resolving this problem on each platform:<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">For Gmail<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li><p><strong>Check Account Credentials.<\/strong>&nbsp;Ensure that the username and password entered for the Gmail account are correct. Update the password if necessary.<\/p><\/li>\n\n\n\n<li><p><strong>Switch to OAuth or an App Password.<\/strong> Google permanently removed the \u201cLess secure app access\u201d setting, so a plain username and password no longer authenticates Gmail SMTP for personal accounts or Workspace accounts. Connect modern email clients with OAuth 2.0, or generate an app-specific password if your client only supports basic authentication. See <a href=\"https:\/\/support.google.com\/a\/answer\/14114704\" rel=\"noopener\" target=\"_blank\" rel=\"noopener noreferrer\">Google\u2019s guide on moving from less secure apps to OAuth<\/a> for the exact steps.<\/p><\/li>\n\n\n\n<li><p><strong>Use App Passwords.<\/strong>&nbsp;If two-factor authentication is enabled, generate an app-specific password for the email client attempting to send emails via SMTP. Use this password instead of the account\u2019s regular password.<\/p><\/li>\n\n\n\n<li><p><strong>Update SMTP Server Settings.<\/strong>&nbsp;Verify that the SMTP server settings are configured correctly. Use the following settings:<\/p>\n<ul class=\"wp-block-list\">\n<li>Server: smtp.gmail.com<\/li>\n\n\n\n<li>Port: 465 (SSL) or 587 (TLS)<\/li>\n\n\n\n<li>Authentication: Yes (using your Gmail account credentials)<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><p><strong>Check Firewall\/Antivirus Settings.<\/strong>&nbsp;Ensure that firewall or antivirus software is not blocking SMTP traffic to Gmail\u2019s servers. Whitelist the email client or disable any settings that may interfere with email transmission.<\/p><\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\">For Outlook<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li><p><strong>Verify Account Credentials.<\/strong>&nbsp;Double-check the username and password for the Outlook email account. Update the password if necessary.<\/p><\/li>\n\n\n\n<li><p><strong>Check SMTP Authentication Settings.<\/strong>&nbsp;In Outlook account settings, ensure that the SMTP authentication method is set to \u201cPassword\u201d or \u201cNormal password.\u201d<\/p><\/li>\n\n\n\n<li><p><strong>Enable Two-Factor Authentication.<\/strong>&nbsp;If two-factor authentication is enabled, generate an app-specific password for the email client attempting to send emails via SMTP. Use this password instead of the account\u2019s regular password.<\/p><\/li>\n\n\n\n<li><p><strong style=\"font-size: revert; color: initial;\">Update SMTP Server Settings.<\/strong><span style=\"font-size: revert; color: initial;\">&nbsp;Verify that the SMTP server settings are configured correctly. Use the following settings:<\/span><\/p>\n<ul class=\"wp-block-list\">\n<li>Server: smtp-mail.outlook.com<\/li>\n\n\n\n<li>Port: 587<\/li>\n\n\n\n<li>Encryption method: STARTTLS<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><p><strong>Review Firewall\/Antivirus Settings.<\/strong>&nbsp;Ensure that firewall or antivirus software is not blocking SMTP traffic to Outlook\u2019s servers. Adjust settings as necessary to allow SMTP communication.<\/p><\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\">For Yahoo<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li><p><strong>Confirm Account Information.<\/strong>&nbsp;Check that the Yahoo email account username and password are entered correctly. Update the password if needed.<\/p><\/li>\n\n\n\n<li><p><strong>Use an App Password. <\/strong>Yahoo disables sign-in from apps that use outdated, password-only authentication by default, so \u201cless secure sign-in\u201d is no longer a reliable fix. Generate a third-party app password from Yahoo Account Security instead, and use that in place of your regular password. <a href=\"https:\/\/help.yahoo.com\/kb\/SLN27791.html\" rel=\"noopener\" target=\"_blank\" rel=\"noopener noreferrer\">Yahoo\u2019s guide to securely accessing Yahoo Mail<\/a> walks through the exact steps.<\/p><\/li>\n\n\n\n<li><p><strong>Generate App Passwords.<\/strong>&nbsp;If two-step verification is enabled, generate an app password specifically for the email client attempting to send emails via SMTP. Use this app password instead of the account\u2019s regular password.<\/p><\/li>\n\n\n\n<li><p><strong>Update SMTP Server Settings.<\/strong>&nbsp;Ensure that the SMTP server settings are configured correctly. Use the following settings:<\/p>\n<ul class=\"wp-block-list\">\n<li>Server: smtp.mail.yahoo.com<\/li>\n\n\n\n<li>Port: 587<\/li>\n\n\n\n<li>Encryption method: TLS<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><p><strong>Adjust Firewall\/Antivirus Settings.<\/strong>&nbsp;Make sure that firewall or antivirus software is not blocking SMTP traffic to Yahoo\u2019s servers. Modify settings to allow SMTP communication.<\/p><\/li>\n<\/ol>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p><strong>Pro Tip: <\/strong>Gmail and Yahoo have both retired plain username-and-password sign-in for third-party email clients, and Microsoft is moving Exchange Online the same direction. Whenever your client offers a choice, pick OAuth 2.0 over an app password: it is more secure and it will not need to be regenerated the next time a provider tightens its authentication rules.<\/p>\n<\/blockquote>\n\n\n\n<p>Not sure if authentication issues like this one are quietly hurting your sender reputation too? <a href=\"https:\/\/app.warmy.io\/signup\" rel=\"noopener\" target=\"_blank\" rel=\"noopener noreferrer\">Start a free Warmy trial<\/a> and let Adeline AI monitor your authentication, warmup, and inbox placement in one place.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Understanding related SMTP errors: 533 and 535<\/h2>\n\n\n\n<p>While SMTP Email Error 534 indicates an authentication failure during the SMTP authentication process, similar errors like 533 and 535 may also occur, each with its own distinct characteristics and solutions. For a full breakdown of every SMTP status and reply code, including the ones covered here, see Warmy\u2019s <a href=\"https:\/\/www.warmy.io\/blog\/smtp-error-codes-and-messages\/\" target=\"_blank\" rel=\"noopener noreferrer\">SMTP error codes and messages guide<\/a>. Many of these authentication and delivery issues connect to broader global <a href=\"https:\/\/www.warmy.io\/blog\/mastering-global-email-deliverability-in-2024-2025\/\" target=\"_blank\" rel=\"noopener noreferrer\">email deliverability practices<\/a>, not just a single provider\u2019s settings.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">SMTP Error 533 &#8211; Email Address Rejected<\/h3>\n\n\n\n<p>SMTP Error 533 typically occurs when the recipient\u2019s email address is rejected by the SMTP server. This rejection may be due to the email address being invalid, misspelled, or flagged as suspicious. Common causes include:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Misspelled recipient email address.<\/li>\n\n\n\n<li>Invalid or non-existent recipient email address.<\/li>\n\n\n\n<li>Blocked email address due to suspected spam or abuse.<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\">To resolve SMTP Error 533<\/h4>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Double-check the recipient\u2019s email address for accuracy and correct any spelling errors.<\/li>\n\n\n\n<li>Ensure that the recipient\u2019s email address is valid and exists.<\/li>\n\n\n\n<li>If the email address is flagged as suspicious, contact the recipient or the email service provider to resolve the issue.<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\">SMTP Error 535 &#8211; Incorrect Authentication Credentials<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li><p>SMTP Error 535 occurs when the authentication credentials provided by the user are incorrect or invalid. This error is similar to SMTP Error 534 but specifically pertains to the authentication process. Common causes include:<\/p>\n<ul class=\"wp-block-list\">\n<li>Incorrect username or password.<\/li>\n\n\n\n<li>Account security settings blocking authentication attempts.<\/li>\n\n\n\n<li>Two-factor authentication failure.<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n\n\n\n<h4 class=\"wp-block-heading\">To resolve SMTP Error 535<\/h4>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Verify that the username and password used for authentication are correct.<\/li>\n\n\n\n<li>Check account security settings to ensure that authentication attempts are not being blocked.<\/li>\n\n\n\n<li>If two-factor authentication is enabled, generate an app-specific password for the email client and use it for authentication.<\/li>\n<\/ol>\n\n\n\n<h2 class=\"wp-block-heading\">Benefits of using email warm-up services like Warmy.io<\/h2>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"768\" src=\"https:\/\/www.warmy.io\/blog\/wp-content\/uploads\/2026\/06\/Warmy-Homepage-1024x768.png\" alt=\"Warmy Homepage\" class=\"wp-image-7290\" title=\"\" srcset=\"https:\/\/www.warmy.io\/blog\/wp-content\/uploads\/2026\/06\/Warmy-Homepage-1024x768.png 1024w, https:\/\/www.warmy.io\/blog\/wp-content\/uploads\/2026\/06\/Warmy-Homepage-300x225.png 300w, https:\/\/www.warmy.io\/blog\/wp-content\/uploads\/2026\/06\/Warmy-Homepage-768x576.png 768w, https:\/\/www.warmy.io\/blog\/wp-content\/uploads\/2026\/06\/Warmy-Homepage-1536x1152.png 1536w, https:\/\/www.warmy.io\/blog\/wp-content\/uploads\/2026\/06\/Warmy-Homepage.png 1920w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<p>Using email warm-up services like Warmy.io offers several benefits, particularly for businesses and individuals who rely on email marketing or regular bulk email communications. Take a look at <a href=\"https:\/\/www.warmy.io\/blog\/what-makes-warmy-io-different\/\" target=\"_blank\" rel=\"noopener noreferrer\">what makes Warmy different<\/a> for the full picture of how the platform works.<\/p>\n\n\n\n<p>Here\u2019s how such services can enhance email performance and reliability:<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Preventing SMTP Email Errors<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Gradual Increase in Sending Volume.<\/strong>&nbsp;<a href=\"https:\/\/www.warmy.io\/\" target=\"_blank\" rel=\"noopener noreferrer\">Warmy.io<\/a> and similar services gradually increase the volume of emails sent from a new or inactive email account. This helps in establishing a reputation with Internet Service Providers (ISPs) as a legitimate email sender, which prevents SMTP (Simple Mail Transfer Protocol) errors related to spam suspicion or abrupt high volume sending. This is the same gradual approach covered in Warmy\u2019s<a href=\"https:\/\/www.warmy.io\/blog\/warming-up-a-new-domain-a-comprehensive-guide\/\" target=\"_blank\" rel=\"noopener noreferrer\"> guide to warming up a new domain<\/a>.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Enhancing Email Deliverability<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Consistent Engagement.<\/strong>&nbsp;By sending emails to a list of email addresses that are designed to engage (open, reply to, and mark the email as important), Warmy.io helps in building and maintaining a positive sender reputation.<\/li>\n\n\n\n<li><strong>Avoidance of <a href=\"https:\/\/www.warmy.io\/blog\/how-to-bypass-spam-filters\" target=\"_blank\" rel=\"noopener noreferrer\">Spam Filters<\/a>.<\/strong>&nbsp;Regular engagement with these controlled email addresses trains email algorithms to recognize the sender\u2019s emails as legitimate, thereby avoiding the spam folder.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Scanning for Blacklists<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Monitoring Email Health.<\/strong> Warmy.io continuously monitors whether an email domain or IP address gets blacklisted. Being on a blacklist can drastically affect email deliverability. Early detection allows users to take corrective actions before it impacts their email campaigns or regular communications.&nbsp;<\/li>\n<\/ul>\n\n\n\n<p>To see if your domain is on the blacklist, just do a<a href=\"https:\/\/www.warmy.io\/free-tools\/email-deliverability-test\" target=\"_blank\" rel=\"noopener noreferrer\"> free email deliverability test<\/a><\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"825\" height=\"527\" src=\"https:\/\/www.warmy.io\/blog\/wp-content\/uploads\/2024\/07\/Screenshot_5.png\" alt=\"dashboard\" class=\"wp-image-7063\" title=\"\" srcset=\"https:\/\/www.warmy.io\/blog\/wp-content\/uploads\/2024\/07\/Screenshot_5.png 825w, https:\/\/www.warmy.io\/blog\/wp-content\/uploads\/2024\/07\/Screenshot_5-300x192.png 300w, https:\/\/www.warmy.io\/blog\/wp-content\/uploads\/2024\/07\/Screenshot_5-768x491.png 768w\" sizes=\"auto, (max-width: 825px) 100vw, 825px\" \/><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\">Authenticating Emails<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>SPF and DMARC Record Generators.<\/strong>&nbsp;Email authentication is crucial to verify that the emails are indeed from the claimed domain and to prevent email spoofing. Warmy.io provides tools to generate proper <a href=\"https:\/\/www.warmy.io\/free-tools\/spf-generator\" target=\"_blank\" rel=\"noopener noreferrer\">SPF<\/a> (Sender Policy Framework) and <a href=\"https:\/\/www.warmy.io\/free-tools\/dmarc-generator\" target=\"_blank\" rel=\"noopener noreferrer\">DMARC<\/a> (Domain-based Message Authentication, Reporting, and Conformance) records. These protocols help in establishing the authenticity of the outgoing emails, which is favored by ISPs and enhances deliverability.<\/li>\n\n\n\n<li><strong>Improved Trust with Recipients.<\/strong>&nbsp;When emails are authenticated, they are less likely to be marked as spam by email servers, which not only improves deliverability but also the trust level recipients have in your communications.<\/li>\n<\/ul>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"727\" src=\"https:\/\/www.warmy.io\/blog\/wp-content\/uploads\/2024\/06\/DMARK-generator-1024x727.png\" alt=\"DMARK generator\" class=\"wp-image-6950\" title=\"\" srcset=\"https:\/\/www.warmy.io\/blog\/wp-content\/uploads\/2024\/06\/DMARK-generator-1024x727.png 1024w, https:\/\/www.warmy.io\/blog\/wp-content\/uploads\/2024\/06\/DMARK-generator-300x213.png 300w, https:\/\/www.warmy.io\/blog\/wp-content\/uploads\/2024\/06\/DMARK-generator-768x545.png 768w, https:\/\/www.warmy.io\/blog\/wp-content\/uploads\/2024\/06\/DMARK-generator.png 1172w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p><strong>Pro Tip: <\/strong>SPF and DKIM only help if DMARC alignment actually passes. After changing either record, pull a fresh DMARC aggregate report. A misaligned SPF or DKIM record can silently cause the same kind of authentication rejection behind errors like 534.<\/p>\n<\/blockquote>\n\n\n\n<h3 class=\"wp-block-heading\">Comprehensive Reporting and Feedback<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Deliverability Insights. <\/strong>Services like Warmy.io offer detailed analytics and reports on email performance, which include deliverability rates, engagement rates, and more. This feedback is invaluable for tweaking email strategies to achieve optimal outcomes.<\/li>\n<\/ul>\n\n\n\n<figure class=\"wp-block-embed is-type-video is-provider-youtube wp-block-embed-youtube wp-embed-aspect-16-9 wp-has-aspect-ratio\"><div class=\"wp-block-embed__wrapper\">\n<iframe title=\"Email Deliverability Test Dashboard | Onboarding\" width=\"500\" height=\"281\" src=\"https:\/\/www.youtube.com\/embed\/iU5zczpixAk?feature=oembed\" frameborder=\"0\" allow=\"accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share\" referrerpolicy=\"strict-origin-when-cross-origin\" allowfullscreen><\/iframe>\n<\/div><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">Conclusion<\/h2>\n\n\n\n<p>Given the above discussion, using email warm-up services such as <a href=\"https:\/\/www.warmy.io\/\" target=\"_blank\" rel=\"noopener noreferrer\">Warmy.io<\/a> is necessary for enhancing email deliverability and avoiding SMTP Email Error 534. They allow for a gradual rise in email volume to establish a positive sender\u2019s reputation, facilitate continuous subscriber engagement to escape from spam filters, or check for blacklists and verify emails through SPF and DMARC records. By increasing the trust of ISPs and email recipients and delivering detailed performance metrics, the approach helps to achieve an email strategy that works seamlessly without constraints.<\/p>\n\n\n\n<p>Still seeing authentication errors after working through these steps? <a href=\"https:\/\/www.warmy.io\/book-a-demo\" target=\"_blank\" rel=\"noopener noreferrer\">Book a free demo<\/a> with Warmy\u2019s team!<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"965\" height=\"643\" src=\"https:\/\/www.warmy.io\/blog\/wp-content\/uploads\/2024\/07\/Experts.png\" alt=\"warmy experts\" class=\"wp-image-6923\" title=\"\" srcset=\"https:\/\/www.warmy.io\/blog\/wp-content\/uploads\/2024\/07\/Experts.png 965w, https:\/\/www.warmy.io\/blog\/wp-content\/uploads\/2024\/07\/Experts-300x200.png 300w, https:\/\/www.warmy.io\/blog\/wp-content\/uploads\/2024\/07\/Experts-768x512.png 768w\" sizes=\"auto, (max-width: 965px) 100vw, 965px\" \/><\/figure>\n","protected":false},"excerpt":{"rendered":"<p>TL;DR: SMTP Error 534 means the receiving server rejected your login credentials during SMTP authentication, almost always because Gmail, Outlook, or Yahoo now require an app password or OAuth instead of a plain password. Update your email client with the correct password type and current SMTP settings for your provider, and the error clears immediately. [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":8136,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[104],"tags":[],"class_list":["post-3875","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-email-deliverability"],"acf":[],"lang":"en","translations":{"en":3875},"pll_sync_post":[],"_links":{"self":[{"href":"https:\/\/www.warmy.io\/blog\/wp-json\/wp\/v2\/posts\/3875","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.warmy.io\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.warmy.io\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.warmy.io\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.warmy.io\/blog\/wp-json\/wp\/v2\/comments?post=3875"}],"version-history":[{"count":5,"href":"https:\/\/www.warmy.io\/blog\/wp-json\/wp\/v2\/posts\/3875\/revisions"}],"predecessor-version":[{"id":8227,"href":"https:\/\/www.warmy.io\/blog\/wp-json\/wp\/v2\/posts\/3875\/revisions\/8227"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.warmy.io\/blog\/wp-json\/wp\/v2\/media\/8136"}],"wp:attachment":[{"href":"https:\/\/www.warmy.io\/blog\/wp-json\/wp\/v2\/media?parent=3875"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.warmy.io\/blog\/wp-json\/wp\/v2\/categories?post=3875"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.warmy.io\/blog\/wp-json\/wp\/v2\/tags?post=3875"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}