This article covers the most common errors that may occur in SMTP setup and how to resolve them.
Looking for SMTP setup instructions? You'll find them in the SMTP setup article.
1. General troubleshooting steps
If you are experiencing general delivery issues where emails fail to send but you don't see a specific error, try these initial troubleshooting steps:
- Double-check your SMTP settings: Ensure that your port, host, and encryption type (SSL/TLS) comply with your provider's recommended guidelines.
- Disconnect and reconnect: Many connection handshake anomalies can be resolved by resetting the sync. Navigate to Settings > My Settings > Email, select Disconnect, and then reconnect your SMTP.
2. MS Exchange SMTP issues
2.1. Authentication unsuccessful / SMTP Client Authentication disabled (error 535 5.7.139)
The error message 535 5.7.139 Authentication unsuccessful, SmtpClientAuthentication is disabled for the Tenant (or basic authentication is disabled) means that Microsoft has disabled Authenticated SMTP (SMTP AUTH) for your organization's tenant or for your specific user mailbox. Microsoft disables SMTP AUTH by default on newer tenants for security purposes. Additionally, enabling "Microsoft Security Defaults" can block this protocol.
How to solve it:
-
Enable Authenticated SMTP for the user:
- Your Microsoft 365 IT Administrator must log in to the Microsoft 365 Admin Center.
- Go to Users > Active Users and select your specific user profile.
- Open the Mail tab, and under Email apps, click Manage email apps.
- Check the box for Authenticated SMTP and click Save changes.
- Verify tenant-level settings: Your IT Administrator should ensure that SMTP AUTH is not disabled globally at the organization level or blocked by Microsoft Security Defaults / Conditional Access policies.
-
Allow propagation and test:
- Wait 15 to 30 minutes for Microsoft's server changes to propagate.
- Try sending an email again from Scoro.
- If you've completed the above steps and email sending still fails after the full propagation period has elapsed, disconnect and reconnect your SMTP setup, then try sending an email again.
2.2. Client not authenticated to send mail (Error 530 5.7.57)
The error SMTP ERROR: MAIL FROM command failed: 530 5.7.57 Client not authenticated to send mail is a broad, general authentication failure. While it can be linked to disabled Authenticated SMTP (as described in Error 535 5.7.139 above), it is often triggered when Microsoft rejects the sending request due to account licensing issues, email address mismatches, cached session credentials, or incorrect manual SMTP parameters.
How to solve it:
-
Confirm active Exchange Online mailbox & SMTP AUTH:
- Ensure your Microsoft account has an active Exchange Online license assigned.
- Verify that Authenticated SMTP (SMTP AUTH) is enabled for the mailbox and tenant in your M365 Admin Center. For more guidance, see the Authentication unsuccessful error section.
-
Match sender address or grant "Send As" permissions:
- Confirm that the sender email address in your Scoro profile matches the primary email of the connected Microsoft 365 mailbox.
- If you are attempting to send from an alias or secondary email address, your IT Admin must grant Send As delegation permissions for that address. For more guidance, see the Send As Denied error section.
-
Disconnect and reconnect using Incognito mode:
Browser session caching can accidentally log you into the wrong Microsoft account during the OAuth flow. To resolve it:- Go to Settings > My Settings > Email and click Disconnect.
- Open an Incognito or Private browsing window, log back into Scoro, navigate to Settings > My Settings > Email, and reconnect your Microsoft Exchange integration using the correct credentials.
-
Verify settings for manual SMTP connections:
- If you are configuring a custom/manual SMTP connection rather than using the standard Microsoft Exchange OAuth integration, verify that your server settings match Microsoft's required parameters:
-
Server / Host:
smtp.office365.com -
Port:
587 -
Encryption / Security:
TLS(orSTARTTLS)
-
Server / Host:
- If you are configuring a custom/manual SMTP connection rather than using the standard Microsoft Exchange OAuth integration, verify that your server settings match Microsoft's required parameters:
2.3. Invalid_grant (error AADSTS65001)
If you use MS Exchange through Entra Enterprise and receive an invalid_grant error (error code AADSTS65001) while setting up your Microsoft Exchange SMTP server, it means that the Scoro application doesn't have the necessary administrator consent in your Entra Admin Center settings.
How to solve it:
-
Grant the permission:
- In the Entra Admin Center, select Show all to display all Admin Centers.
- In the side menu, navigate to Entra ID > Enterprise apps.
- Click on the Scoro app, then open the Permissions section in the side menu.
- Click the blue Grant admin consent button. The permissions request screen will appear – click the Accept button.
- Retry the setup: Try setting up your MS Exchange SMTP in Scoro again. Since the Scoro app now has admin permissions, the SMTP setup should work successfully.
For more detailed guidance, see the Grant tenant-wide admin consent to an application article on Microsoft Learn.
2.4. Send as Denied (error 5.2.252)
The error message 5.2.252 SendAsDenied; userA@domain.com not allowed to send as userB@domain.com occurs when you attempt to send an email using an alias, shared mailbox, or another user's email address as your "From" address, but your authenticated Microsoft account does not have permission to send on behalf of that email address.
There are two ways to solve this issue:
-
Match your "From" address:
- The simplest fix is to ensure the "From" address in your Scoro settings matches the primary email address of your authenticated Microsoft mailbox.
-
Grant Send As delegation:
- If you need to send emails using an alias or another address, your IT Administrator must log into the Exchange Admin Center or M365 Admin Center and grant Send As permissions to your authenticated mailbox for the target alias/address.
- It can take up to 60 minutes for permission updates to propagate across Microsoft's systems. You do not need to disconnect or reconnect your SMTP connection in Scoro for this change to take effect.
2.5. Application client secret expired (Error AADSTS7000222)
If you see the error AADSTS7000222: The provided client secret keys for app are expired, this indicates that the security credential (client secret) for Scoro’s app registration in Microsoft Entra has expired. This is an internal Scoro platform credential—not a setting, policy, or configuration issue within your own Microsoft 365 tenant or user account. Because the application key has expired on Scoro's side, disconnecting and reconnecting your integration will not resolve this error until Scoro updates the credential.
To resolve this issue, please contact our Support team via this contact form.