On this page
Short answer
535 5.7.3 Authentication unsuccessful is Exchange Online refusing an SMTP AUTH login to smtp.office365.com, before any email is sent. Microsoft's checklist covers the username and password, SMTP AUTH switched off for the mailbox, MFA, security defaults and Conditional Access policies that block legacy authentication. With OAuth2, also check the token's scope and the app's permissions: Microsoft's OAuth guide shows the same line for a failed token login.
What the error says
535 5.7.3 Authentication unsuccessful is Exchange Online's reply when a tool logs in to smtp.office365.com over SMTP AUTH and the login fails. Microsoft's troubleshooting page for apps and devices lists it under "Error: Authentication unsuccessful". Its OAuth guide shows the same line as the sample failure of an AUTH XOAUTH2 login.
The reply comes at login, before the email leaves your tool, so the cause sits in the account or the tenant's settings. The code itself names none: RFC 4954 defines 535 5.7.8 for invalid credentials, and Microsoft's 5.7.3 doesn't say which check failed.
5.7.3 and the replies next to it
Reply | What it tells you |
|---|---|
535 5.7.3 Authentication unsuccessful | The login failed; no reason given |
535 5.7.139 Authentication unsuccessful, followed by a reason | The text names the cause: see 535 5.7.139 |
5.7.57 Client not authenticated to send mail | Listed by Microsoft together with 5.7.3, same checks |
550 5.7.30 Basic authentication is not supported for Client Submission | Microsoft's announced reply to password logins once Basic auth for SMTP AUTH is permanently disabled |
What Microsoft says to check
For password logins, that troubleshooting page lists:
Username and password. Sign in to Outlook on the web with the same account and send a test email; this also shows whether the mailbox is blocked for spam.
SMTP AUTH on the mailbox.
Get-CASMailbox -Identity <EmailAddress> | Format-List SmtpClientAuthenticationDisabledin Exchange Online PowerShell; if it saysTrue, runSet-CASMailbox -Identity <EmailAddress> -SmtpClientAuthenticationDisabled $false.MFA on that mailbox. Microsoft suggests turning off per-user MFA for the account, since "Legacy authentication doesn't support multifactor authentication" (security defaults).
Security defaults. With them on, "SMTP AUTH is already disabled in Exchange Online" (SMTP AUTH page). Microsoft's caution on turning them off: "Don't do this step unless you understand the risks that are involved."
Conditional Access. Exclude the sending mailbox from any policy that blocks legacy authentication.
TLS. The tool must support TLS 1.2 or later.
Steps 3 to 5 lower sign-in protection, so they are the admin's decision. Microsoft's setup guide recommends OAuth for apps.
When the login uses OAuth2
With AUTH XOAUTH2, the reply doesn't say whether the token, the app's permissions or a tenant setting failed. Check the login against the OAuth guide:
Scope. A user token needs
https://outlook.office.com/SMTP.Send. An app-only token needs theSMTP.SendAsApppermission with admin consent and the scopehttps://outlook.office365.com/.default.Service principal. For app-only access, an admin runs
New-ServicePrincipalandAdd-MailboxPermissionin Exchange. The guide warns: "Using the incorrect Object ID will cause an authentication failure."SMTP AUTH switches. OAuth runs over the same protocol. A Microsoft Q&A thread shows an OAuth login getting 535 5.7.139 with "disabled for the Tenant".
Exchange Server 2016 and 2019
We found no Exchange Server documentation page for this code. An archived Microsoft blog post (2018, SharePoint to on-premises Exchange) shows 535 5.7.3 Authentication unsuccessful for a login on port 25, where the Default Frontend connector doesn't have the Exchange users permission group by default.
Per Receive connectors, authenticated clients log in to the Client Frontend connector on port 587, which by default offers Basic authentication only after TLS. Without the ms-Exch-SMTP-Submit permission, which its Exchange users group grants, "the MAIL FROM and AUTH commands will fail." Check the port, TLS and that connector's permission groups.
Free guide19 min read
Send 100,000 cold emails a month
Domains and mailboxes you need, DNS, warmup, lists, copy and follow-ups, with a launch checklist, sent to your inbox.
What it means for cold email
In a sequencer, a mailbox with 5.7.3 sends nothing, warmup included, until its login works. One failing mailbox points to its password or its own SMTP AUTH setting; a whole tenant failing on the same day points to security defaults, Conditional Access or the organization's SMTP AUTH switch.
Smartlead and Instantly both ask for SMTP AUTH on the mailbox. Smartlead, which connects Outlook with OAuth, wants Authenticated SMTP and IMAP on in the Microsoft 365 admin center and a 20 to 30 minute wait; Instantly's guide wants the same settings and an hour.
Password connections have a date: Basic authentication for SMTP AUTH goes off by default in existing tenants at the end of December 2026 (Exchange Team Blog, January 27, 2026). The schedule is in Microsoft 365 new-tenant limits.
Questions
Is 535 5.7.3 the same as 535 5.7.139?
Both are failed SMTP AUTH logins at Exchange Online. 535 5.7.139 adds the reason after a comma, such as SMTP AUTH disabled for the tenant or security defaults blocking the user. 5.7.3 gives none.
Will this error start after December 2026?
Microsoft hasn't published which reply tools get when the Basic auth default changes. For the final removal, its April 2024 post names 550 5.7.30. The SMTP AUTH clients report (Exchange admin center > Reports > Mail flow) shows who still logs in with a password.
What we recommend at Outreach2day
We don't sell Microsoft 365 mailboxes: Outreach2day mailboxes are standard SMTP/IMAP on our own infrastructure, so these Exchange Online settings don't apply to them, and their logins work in any sending tool. We recommend up to 25 cold emails per mailbox a day after 14 days of warmup.
Sources
- Microsoft Learn: Fix issues with printers, scanners, and LOB apps that send email using Microsoft 365: learn.microsoft.com/en-us/troubleshoot/exchange/email-delivery/fix-issues-with-printers-scanners-and-lob-applications-that-send-email-using-off
- Microsoft Learn: Authenticate an IMAP, POP or SMTP connection using OAuth: learn.microsoft.com/en-us/exchange/client-developer/legacy-protocols/how-to-authenticate-an-imap-pop-smtp-application-by-using-oauth
- Microsoft Learn: Enable or disable SMTP AUTH in Exchange Online: learn.microsoft.com/en-us/exchange/clients-and-mobile-in-exchange-online/authenticated-client-smtp-submission
- Microsoft Learn: How to set up a multifunction device or application to send email using Microsoft 365: learn.microsoft.com/en-us/exchange/mail-flow-best-practices/how-to-set-up-a-multifunction-device-or-application-to-send-email-using-microsoft-365-or-office-365
- Microsoft Learn: Security defaults in Microsoft Entra ID: learn.microsoft.com/en-us/entra/fundamentals/security-defaults
- Microsoft Learn: Receive connectors in Exchange Server: learn.microsoft.com/en-us/exchange/mail-flow/connectors/receive-connectors
- Microsoft Learn (archived blog): Is SMTP Auth Really Working?: learn.microsoft.com/en-us/archive/blogs/mikelee/is-smtp-auth-really-working
- Exchange Team Blog: Updated Exchange Online SMTP AUTH Basic Authentication Deprecation Timeline: techcommunity.microsoft.com/blog/exchange/updated-exchange-online-smtp-auth-basic-authentication-deprecation-timeline/4489835
- Exchange Team Blog: Exchange Online to retire Basic auth for Client Submission (SMTP AUTH): techcommunity.microsoft.com/blog/exchange/exchange-online-to-retire-basic-auth-for-client-submission-smtp-auth/4114750
- RFC 4954: SMTP Service Extension for Authentication: rfc-editor.org/rfc/rfc4954
Related answers
- What Does 535 5.7.139 Mean, and How Do I Fix It?Outlook and Microsoft
- Why Is Outlook Blocking or Junking My Cold Emails?Outlook and Microsoft
- What Does 550 5.7.233 Mean, and How Do I Fix It?Bounces and errors
- What Does a 550 5.7.1 Bounce Mean, and How Do I Fix It?Bounces and errors
In depth on the blog
- Microsoft 365 Cold Email After MC1454397: New-Tenant Limits8 min read
- SMTP for Cold Email: Mailbox, Relay or Self-Hosted7 min read
- Microsoft 365 and Outlook Sending Limits9 min read

