logo
search
Send & Receive Issues

Fix SMTP Error 530 5.7.57 When Sending SAP Mail via Exchange Online

Chanuka GeekiyanageChanuka Geekiyanage Oct 13, 2026 869 views

Question details

The user needs to resolve an authentication error preventing emails from being sent from SAP through the Exchange Online SMTP server.

Fix SMTP Error 530 5.7.57 When Sending SAP Mail via Exchange Online
Product
Exchange Online
Device & OS
not provided
Scenario
Sending outbound emails from an SAP system via Exchange Online (smtp.office365.com).
Observed behavior
The system fails to send email and throws SMTP Error 530 5.7.57, indicating that the client was not authenticated.
Before you start

Ensure you have administrative access to both your SAP SCOT configuration interface and the Microsoft 365 Admin Center.

Solution 1Recommended

Verify SAP SCOT Client Submission Settings

Ensure that SAP is configured with the correct server endpoint, port, and valid mailbox credentials for Exchange Online.

SMTP Error 530 5.7.57 is primarily an authentication issue. When using smtp.office365.com, the SAP system must authenticate with a valid, licensed Microsoft 365 email account.

1
Access SAP SCOT

Log into your SAP system and run transaction code SCOT to open the SAPConnect administration menu.

2
Configure the SMTP Node

Locate the SMTP node, double-click it, and set the Mail Host to smtp.office365.com with the Mail Port set to 587.

3
Enable Security

Ensure that the 'Security' setting is configured to use STARTTLS (TLS encryption).

4
Update Credentials

Navigate to the Authentication section and enter the exact username and password of the Microsoft 365 mailbox you intend to send from.

Verify SAP SCOT Client Submission Settings
Sender matching required: When using SMTP client submission, the 'From' address on emails generated by SAP must exactly match the Microsoft 365 account used for authentication.
Free Microsoft Office alternative

Enhance Your Daily Workflow with WPS Office

While resolving Exchange Online server configurations, consider utilizing WPS Office for your daily document creation. It is a powerful, lightweight, and completely free alternative to Microsoft Office that easily handles all your productivity needs.

  1. 1. Download the Installer: Visit the official WPS Office website to download the free installation package.
  2. 2. Install WPS Office: Run the installer and follow the simple on-screen prompts to set up the software.
  3. 3. Open Your Documents: Launch WPS Office and instantly open your existing Microsoft Office files with perfect formatting.
Fully compatible with Microsoft Word, Excel, and PowerPoint formats.Lightweight installation that runs smoothly without heavily taxing system resources.Built-in PDF editor to create, convert, and sign documents effortlessly.Familiar tabbed interface requiring zero learning curve for seamless migration.
QA img-9

Frequently Asked Questions

Why am I getting Error 530 5.7.57 in Exchange Online?

This error signifies that your application (in this case, SAP) failed to authenticate with the smtp.office365.com server. Common causes include incorrect passwords, SMTP AUTH being disabled for the account, or organizational policies blocking basic authentication.

Can I use basic authentication for SMTP in Microsoft 365?

Microsoft strongly discourages basic authentication and blocks it by default in new tenants via Security Defaults. If your SAP system only supports basic authentication, you must disable Security Defaults (not recommended) or create an Exchange SMTP relay via IP whitelist.

How do I check if Security Defaults are blocking my SAP emails?

Log into the Microsoft Entra admin center, navigate to Identity > Properties, and click 'Manage security defaults'. If enabled, it blocks basic authentication across the tenant, which will prevent older SAP systems from using SMTP client submission.

Can SAP send emails using Modern Authentication (OAuth 2.0)?

Yes, newer versions of SAP S/4HANA and SAP NetWeaver support OAuth 2.0 for SMTP. Check your SAP documentation and patch levels to see if you can configure Modern Authentication, which complies with Microsoft 365 security standards.