🧡 Skip to main content🔍 Skip to search
Event icon · error

This Error Event is part of Automation Workshop Service Events.

Event ID · 2501

"Could not send notification email"

Overview

The error indicates that Automation Workshop has failed to send notification email (i.e., success or error reports). Error message contains error description that allows identifying the particular cause of failure.

Event examples

See some examples of the Could not send notification email Event messages:

  • Could not send notification email: command DATA failed (550 5.7.0 Requested action not taken: too many emails per second).
  • Could not send notification email: could not connect to SMTP server.
  • OAuth2 response failed (501-5.5.2 Cannot Decode response. For more information, go to; 501 5.5.2 https://support.google.com/a/answer/3221692 … - gsmtp).
  • OAuth2 response failed (334 status:400 · schemes:Bearer · scope:https://mail.google.com/).
  • OAuth2 response failed (535 5.7.3 Authentication unsuccessful [GV3P280CA0033.SWEP280.PROD.OUTLOOK.COM 2025-03-19T14:49:33.156Z 08DD40EF4BF17246]).

Solution

Check your email server and email settings options. See popular SMTP server settings on how to determine server settings for outgoing e-mail or test SMTP server connection to troubleshoot typical server connection problems.

If OAuth 2.0 authentication is not working, start by verifying that your SMTP server supports OAuth 2.0 and that the correct server address and port are used. Make sure the OAuth credentials are valid, authorized, and include the required scopes (check with your email provider documentation).

Additional OAuth 2.0 common issues—check for any expired or revoked tokens, and reauthorize the application (registered on your cloud provider) if needed. Finally, ensure the system has a working internet connection and that the URLs to the authorization or token endpoints are correct.

Summary

Common causes of the SMTP error:

  • FROM address not allowed (you must use the same address as for authentication).
  • TO address not permitted.
  • Authentication required to send outside your organization.
  • SSL or TLS encrypted connection required to send emails.
  • User consent is not given for OAuth 2.0 credentials (additional authorization is required).

More relaying debugging…

Popular SMTP settings

The art of automation. A 90-second journey.

We are here to help…

If you have any questions, please do not hesitate to contact our support team.