About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.
When a scanner, printer or line-of-business application connects to smtp.office365.com and the server answers "535 5.7.3 Authentication unsuccessful" (or "5.7.57 Client not authenticated to send mail"), Microsoft's troubleshooting checklist begins with one setting: whether authenticated SMTP, called SMTP AUTH, is enabled on the sending mailbox. Microsoft's SMTP AUTH page adds a second, organisation-wide setting.
Check the mailbox setting first, because it overrides the organisation setting. If SMTP AUTH is on and the error remains, the next checks are security defaults, Conditional Access, multifactor authentication on that mailbox, and whether the device supports TLS 1.2. If the device cannot meet the requirements, Microsoft documents four other ways to send: SMTP relay, Direct Send, High Volume Email and Azure Communication Services Email.
What the error means
The Microsoft troubleshooting page lists "535 5.7.3 Authentication unsuccessful" and "5.7.57 Client not authenticated to send mail" under one heading, "Error: Authentication unsuccessful", with the same four checks for both. It also lists "535 5.7.139 Authentication unsuccessful, federated STS service was unreachable." and "535 5.7.139 Authentication unsuccessful, the federated STS URL does not support HTTPS." and describes them as relating to federation gateway servers hosted on-premises by customers. A 5.7.139 message that names SMTP client authentication being disabled does not appear on the Microsoft Learn pages cited here. Read the full text of your own error rather than matching on the code alone.
SMTP AUTH is the protocol used for SMTP client submission, "typically on TCP port 587". Microsoft says these settings apply only to mailboxes hosted in Exchange Online. There are two switches: an organisation-wide setting, and a per-mailbox setting that overrides it. For organisations created after January 2020, Microsoft states SMTP AUTH is disabled, though it can be enabled per mailbox. If security defaults are on, SMTP AUTH is already disabled. If an authentication policy disables basic authentication for SMTP, clients cannot use SMTP AUTH "even if you enable the settings outlined in this article."
Microsoft also notes client SMTP submission with Basic authentication "is scheduled for deprecation" and recommends modern authentication (OAuth). Treat an SMTP AUTH fix with a stored password as a temporary bridge.
Likely causes
| Cause | What you see | How to confirm |
|---|---|---|
| SMTP AUTH disabled on the mailbox | 535 5.7.3 or 5.7.57 | Get-CASMailbox shows SmtpClientAuthenticationDisabled as True |
| Organisation-wide SMTP AUTH off, mailbox inherits | Same error; mailbox value is blank | Get-TransportConfig shows True; mailbox value blank means "use organisation setting" |
| Security defaults enabled | SMTP AUTH disabled even after the settings are changed | Entra ID properties, Manage security defaults |
| Conditional Access blocks legacy authentication | Sign-in blocked for the mailbox | Policy that blocks legacy authentication; mailbox listed under users |
| Multifactor authentication on the mailbox | Device cannot answer a prompt | MFA status for the user in the admin centre |
| Device cannot do TLS 1.2 or later | Connection or sign-in fails | Device firmware; Microsoft requires TLS 1.3 or 1.2 |
| Device sends without credentials | "Client was not authenticated to send anonymous mail during MAIL FROM" | No password entered; device may not support client submission |
| Sender address differs from the sign-in mailbox | "5.7.60 SMTP; Client does not have permissions to send as this sender." | Sender address versus login account; Send As permission |
| Port blocked | No 220 greeting when testing | Telnet test below |
Prove the cause before changing anything
All of these read settings.
Check the mailbox in Exchange Online PowerShell:
Get-CASMailbox -Identity <EmailAddress> | Format-List SmtpClientAuthenticationDisabledMicrosoft's meanings: False is enabled, True is disabled, blank means use the organisation setting.
Check the organisation setting:
Get-TransportConfig | Format-List SmtpClientAuthenticationDisabledList every mailbox with SMTP AUTH enabled, to find out what depends on it:
$Users = Get-CASMailbox -ResultSize unlimited $Users | where {$_.SmtpClientAuthenticationDisabled -eq $false}Test the credentials by signing in to Outlook on the web with the device's username and password and sending a test message. Microsoft says this confirms the mailbox is active and has not been blocked for sending spam.
Test the network path from a computer on the same network as the device. Install the Telnet client, run
telnet, then typeopen smtp.office365.com 587(or 25 if that is the port set). A response line that begins220and names a Microsoft ESMTP service means the connection is open. If it does not connect, a firewall or ISP may be blocking the port.Check the device settings against Microsoft's table: server
smtp.office365.com(not an IP address), port 587 recommended or 25, TLS/StartTLS enabled, and the mailbox's sign-in. Microsoft says a device that defaults to port 465 "doesn't support the required versions of TLS."Read the device's own SMTP log for the full error text, and compare it with the headings in the troubleshooting page.
Fix
Mailbox has SMTP AUTH off.
Disruptive step: enabling SMTP AUTH on a mailbox allows password-based SMTP sign-in for that account. Back out with $true (disabled) or $null (follow the organisation setting).
Set-CASMailbox -Identity <EmailAddress> -SmtpClientAuthenticationDisabled $false
Organisation setting is off and many mailboxes depend on it. Prefer per-mailbox enablement for the few accounts that need it.
Disruptive step: Set-TransportConfig -SmtpClientAuthenticationDisabled $false turns SMTP AUTH on for the whole organisation, except mailboxes explicitly set to $true. Back out by setting $true. Microsoft's recommendation is the reverse: disable it organisation-wide and enable it only for accounts that still need it.
Security defaults or Conditional Access. Microsoft's troubleshooting page lists turning off security defaults and excluding the mailbox from a Conditional Access policy that blocks legacy authentication.
Disruptive step: disabling security defaults removes protections for every user in the tenant. Microsoft's own caution says do not do this step "unless you understand the risks that are involved." Back out by setting Enable security defaults to Yes again. Excluding one mailbox from the Conditional Access policy is narrower; back out by removing the exclusion.
Multifactor authentication on the mailbox. Microsoft's steps include disabling MFA on that mailbox.
Risk: that mailbox then relies on its password alone. Back out by re-enabling MFA once you move the device to another method.
Advice, not a Microsoft step: use a dedicated, low-privilege mailbox for the device, never a person's.
Old device, TLS below 1.2. Update firmware. If the device cannot be updated, Microsoft documents an opt-in.
Disruptive step: setting AllowLegacyTLSClients to True on Set-TransportConfig (or the matching Exchange admin centre option) lets legacy TLS 1.0 and 1.1 clients submit to the separate endpoint smtp-legacy.office365.com. It accepts weaker encryption. Back out by setting it to False once the device is retired.
Sender differs from sign-in account (5.7.60). Microsoft says the sign-in account needs Send As permission on the other mailbox, or you should use SMTP relay instead.
Device cannot sign in at all. Microsoft's comparison table offers other methods:
- SMTP relay: port 25 to your MX endpoint, authenticated by an inbound connector using a certificate or a static public IP address that is not shared. It does not need a licensed mailbox. The device must send from an address in an accepted domain.
- Direct Send: no Microsoft 365 setting, port 25, to your MX endpoint, but it delivers only to recipients in your Microsoft 365 organisation. Microsoft recommends it only for advanced customers.
- High Volume Email: internal recipients only, port 587, with an HVE account.
- Azure Communication Services Email: Microsoft's suggested route for sending to internal and external recipients.
Disruptive step: creating an inbound connector for SMTP relay lets any host presenting that certificate or IP address send as your domain. Back out by turning the connector off or deleting it. Add the sending IP to your SPF record, as Microsoft directs.
Example (illustrative): scan01 at 10.0.20.40 in CONTOSO signs in as scan@contoso.com and fails with 535 5.7.3. Get-CASMailbox returns True for that mailbox. The administrator sets it to $false for that one mailbox, leaves the organisation setting alone, and the next test works. Later a statement application on the same mailbox sends 12 recipients per message. Under Microsoft's limit of 10,000 recipients a day, 10,000 / 12 is 833 messages (833.3, rounded down), so the application is moved to SMTP relay.
Confirm the fix
- Re-run the
Get-CASMailboxcheck and confirm the value is False for the intended mailbox only. - Send a test from the device to an internal and an external address (client submission allows both).
- Look in Sent Items for the mailbox; Microsoft lists "Saves to Sent Items folder" as a client SMTP submission feature, not a relay one.
- Recheck the mailbox list from step 3 so you know exactly which accounts can use SMTP AUTH.
What to watch afterwards
- Microsoft's limits for client SMTP submission are 10,000 recipients per day and 30 messages per minute. A burst from a scanner can hit the per-minute limit.
- Re-run the list of SMTP AUTH-enabled mailboxes monthly. Remove any that are no longer needed.
- Plan a move from Basic authentication to OAuth or another method, because Microsoft states it is scheduled for deprecation.
- If the device's public IP changes, update the SPF record and any relay connector.
Read next
Related articles you may want next.
- HostingOutbound email as a hidden dependency of hosted business applicationsWhat breaks in hosted LOB workflows when SMTP relay, authentication or sender policy fails—even when interactive login still works.Read article
- HostingApplication Email Rejected or Junked After a Server Move: SPF, DKIM, DMARC and PTRApplication mail bouncing or junked after a migration? Read Authentication-Results, then fix SPF, DKIM, DMARC alignment, PTR and Microsoft 365 relay settings for the new path.Read article
- TroubleshootingOutbound mail times out after a move: the new host cannot reach port 25Mail queued and port 25 times out after moving to Azure, AWS or Google Cloud? Prove the block with a TCP test and switch to an authenticated relay.Read article
Risks and limits
These commands have not been run or lab-tested. Settings can change; the Microsoft pages cited carry dates from 2025 to 2026. The Learn pages say client submission with Basic authentication is scheduled for deprecation and give no date. The Exchange Team post "Updated Exchange Online SMTP AUTH Basic Authentication Deprecation Timeline" (27 January 2026) says that at the end of December 2026 SMTP AUTH Basic Authentication will be disabled by default for existing tenants, that administrators will still be able to enable it, and that Microsoft will announce the final removal date in the second half of 2027. Read that post before you build anything long-lived on SMTP AUTH with a password. The troubleshooting page uses the SMTP error texts as they appear on that page; your tenant may word them differently.
Microsoft's page "highly" recommends disabling SMTP AUTH organisation-wide and enabling it only for accounts that still need it. Enabling it widens what a stolen mailbox password can do.
Sources
- Enable or disable SMTP AUTH in Exchange Online — Microsoft Learn, page dated 2026-09-16, accessed 18 November 2026
- How to set up a multifunction device or application to send email using Microsoft 365 or Office 365 — Microsoft Learn, page dated 2026-09-16, accessed 18 November 2026
- Fix issues with printers, scanners, and LOB apps that send email using Microsoft 365 — Microsoft Learn, page dated 2025-06-25, accessed 18 November 2026
- Updated Exchange Online SMTP AUTH Basic Authentication Deprecation Timeline — Microsoft Exchange Team blog, posted 27 January 2026, accessed 18 November 2026
This article was originally published on .