Home › Exchange Online › 550 5.7.57

Exchange Online · 550 5.7.57 · Exchange Online / Microsoft 365

Exchange Online Error 550 5.7.57 SMTP AUTH Disabled

SMTP AUTH is disabled due to Basic Auth deprecation; re-enable for specific mailbox or migrate to OAuth.

Error Details

FactValueSourceNote
Exact error string550 5.7.57 SMTP AUTH is disabled for the client submission endpointSMTP server response-> EAC Message Trace
Build range affectedExchange Online / Microsoft 365Microsoft documentation
Registry key involved
Relevant service/endpoint URLsmtp.office365.com:587SMTP server configuration-> for port 587
Log line signatureEvent ID 1035 or 12020 in Application.evtxWindows Event Viewer-> MSExchangeTransport source

Log Files to Check

What This Error Actually Means

The error code 550 5.7.57 indicates that the sending client attempted to use SMTP authentication (SMTP AUTH) on port 587 with Basic Authentication, but this method has been disabled either for the specific mailbox or at the organization level in Exchange Online. This is part of Microsoft's ongoing deprecation of Basic Authentication as part of their Modern Auth migration initiative. The error originates from the smtp.office365.com:587 endpoint and affects any client attempting to send email using this deprecated authentication method.

Affected Versions and Scope

This issue impacts all tenants in Exchange Online / Microsoft 365 where the organization-wide setting SmtpClientAuthenticationDisabled is set to $true. This includes any mailbox that has been individually configured with SmtpClientAuthenticationDisabled set to $true in its CAS mailbox settings. The deprecation of Basic Authentication for SMTP AUTH was enforced by Microsoft starting October 2022, and this error will occur regardless of the client's operating system or application type.

Where To Look First: Logs and Event IDs

To diagnose this issue, start by examining the following logs:

Root Causes

1. Organization-wide SMTP AUTH Disabled

If the tenant-wide setting SmtpClientAuthenticationDisabled is set to $true, all mailboxes in the organization are blocked from using SMTP AUTH, regardless of individual mailbox settings. This can be verified with the PowerShell cmdlet:

Get-TransportConfig | Select-Object SmtpClientAuthenticationDisabled

2. Specific Mailbox SMTP AUTH Disabled

A particular mailbox may have been individually configured to disable SMTP AUTH, even if the organization-wide setting is enabled. Check this with:

Get-CASMailbox -Identity [email protected] | Select-Object SmtpClientAuthenticationDisabled

3. Legacy Devices or Applications Using Basic Auth

Devices such as printers, scanners, or line-of-business applications that rely on port 587 and Basic Authentication will fail if they have not been updated to use OAuth 2.0.

4. Migrated Shared Mailboxes or Service Accounts

Shared mailboxes or service accounts migrated from on-premises Exchange may retain their previous configuration, including disabled SMTP AUTH settings.

Fix Procedure

  1. Re-enable SMTP AUTH for a specific mailbox:
  2. Set-CASMailbox -Identity [email protected] -SmtpClientAuthenticationDisabled $false

    Verify the change with:

    Get-CASMailbox -Identity [email protected] | Select-Object SmtpClientAuthenticationDisabled
  3. Re-enable SMTP AUTH at the organization level (if disabled tenant-wide):
  4. Set-TransportConfig -SmtpClientAuthenticationDisabled $false

    Note: Microsoft may re-enforce this setting for some tenants, so document any business need for Basic Auth.

  5. Migrate to OAuth 2.0:
  6. Register an Entra ID application with the SMTP.Send permission and update the client to use OAuth 2.0 credentials for authentication.

  7. Use Direct Send (port 25):
  8. Configure devices to relay directly to the MX record of the recipient domain without using SMTP AUTH. This bypasses Exchange Online submission but only works for external recipients.

  9. Configure an SMTP Relay in EAC:
  10. Navigate to Exchange admin center > Mail flow > Connectors and create a new connector specifying the sending IP address to allow internal relaying without authentication.

Important: Re-enabling SMTP AUTH at the organization level may expose your tenant to security risks if legacy devices cannot be updated. Ensure all clients using Basic Auth are either migrated or properly secured.

Error Code Variants

Error CodeDescription
550 5.7.57SMTP AUTH disabled for the client submission endpoint (this error)
550 5.7.16Relay access denied, typically due to incorrect authentication or relay configuration
550 5.2.0Invalid RCPT TO command, unrelated to authentication but often confused with this error

Verification

To confirm the fix:

  1. Send a test email from the affected device or application.
  2. Check the Message Trace in EAC for the sender's address. The result should show Delivered without the 5.7.57 error.
  3. Review the Application event log on any sending server to ensure no new events with ID 1035 or 12020 are logged after the fix.

Prevention

To avoid recurrence:

  1. Monitor for any re-enforcement of the SmtpClientAuthenticationDisabled setting at the organization level using:
  2. Get-TransportConfig | Select-Object SmtpClientAuthenticationDisabled
  3. Regularly audit devices and applications sending email to ensure they use OAuth 2.0 or other supported authentication methods.
  4. Educate users and developers about the deprecation of Basic Auth and the need for modern authentication protocols.
TIP: Use Get-MessageTrace -StartDate (Get-Date).AddHours(-2) -EndDate (Get-Date) to quickly check recent message traces in EAC.

Sources & References

Related Guides

Get new error code fixes by email

Product-specific solutions for Intune, Autopilot, SCCM and Entra ID — straight to your inbox. No spam.