Error Details
| Fact | Value | Source | Note |
|---|---|---|---|
| Exact error string | 550 5.7.57 SMTP AUTH is disabled for the client submission endpoint | SMTP server response | -> EAC Message Trace |
| Build range affected | Exchange Online / Microsoft 365 | Microsoft documentation | |
| Registry key involved | |||
| Relevant service/endpoint URL | smtp.office365.com:587 | SMTP server configuration | -> for port 587 |
| Log line signature | Event ID 1035 or 12020 in Application.evtx | Windows Event Viewer | -> MSExchangeTransport source |
Log Files to Check
C:\Windows\System32\winevt\Logs\Application.evtx
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:
C:\Windows\System32\winevt\Logs\Application.evtxon any on-premises sending server. Filter for events with ID1035or12020, which indicate SMTP AUTH failures.- Exchange Admin Center (EAC) > Mail flow > Message trace, where you can filter by the sender's address and view the server response containing the error code
5.7.57.
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
- Re-enable SMTP AUTH for a specific mailbox:
- Re-enable SMTP AUTH at the organization level (if disabled tenant-wide):
- Migrate to OAuth 2.0:
- Use Direct Send (port 25):
- Configure an SMTP Relay in EAC:
Set-CASMailbox -Identity [email protected] -SmtpClientAuthenticationDisabled $false
Verify the change with:
Get-CASMailbox -Identity [email protected] | Select-Object SmtpClientAuthenticationDisabled
Set-TransportConfig -SmtpClientAuthenticationDisabled $false
Note: Microsoft may re-enforce this setting for some tenants, so document any business need for Basic Auth.
Register an Entra ID application with the SMTP.Send permission and update the client to use OAuth 2.0 credentials for authentication.
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.
Navigate to Exchange admin center > Mail flow > Connectors and create a new connector specifying the sending IP address to allow internal relaying without authentication.
Error Code Variants
| Error Code | Description |
|---|---|
| 550 5.7.57 | SMTP AUTH disabled for the client submission endpoint (this error) |
| 550 5.7.16 | Relay access denied, typically due to incorrect authentication or relay configuration |
| 550 5.2.0 | Invalid RCPT TO command, unrelated to authentication but often confused with this error |
Verification
To confirm the fix:
- Send a test email from the affected device or application.
- Check the Message Trace in EAC for the sender's address. The result should show
Deliveredwithout the5.7.57error. - Review the Application event log on any sending server to ensure no new events with ID
1035or12020are logged after the fix.
Prevention
To avoid recurrence:
- Monitor for any re-enforcement of the
SmtpClientAuthenticationDisabledsetting at the organization level using: - Regularly audit devices and applications sending email to ensure they use OAuth 2.0 or other supported authentication methods.
- Educate users and developers about the deprecation of Basic Auth and the need for modern authentication protocols.
Get-TransportConfig | Select-Object SmtpClientAuthenticationDisabled
Get-MessageTrace -StartDate (Get-Date).AddHours(-2) -EndDate (Get-Date) to quickly check recent message traces in EAC.