Breadcrumbs

What happens when a message is blocked?

In your delivery reporting you will always see a standard error code and status detail when a message is blocked.

The exact standard error and description depend on which Safeguard feature blocked the message and are described in the sections below (Destination Management, IP Address Restrictions, Rate Limiting, Safeguard Plus).


Destination Management

If you send a message to a country that is not allowed by your Safeguard Destination Management configuration:

  • The message is cancelled by Safeguard.

  • In the delivery reporting you will see:

    • Standard error:
      28 / Message blocked by Safeguard Destination management

    • Standard error description:
      Used when the message was blocked because of security configuration - destination management, please check settings or contact the account manager

You can use this information to:

  • Recognize that the message was blocked by Destination Management, not by the operator.

  • Check whether this country should be allowed and, if needed, update your Traffic destination restrictions in Channels.

  • Adjust your own application logic to avoid sending to countries that are blocked.


IP Address Restrictions

If Safeguard blocks a message because the request originates from an IP address that is not allowed:

  • The request is blocked at our Gateway before it is processed further, so we do not log the request details.

  • For security reasons, we cannot share additional technical details on reason of the blocked request.


Rate Limiting

If you exceed a Safeguard sending limit (either per recipient or per customer account):

  • The message is cancelled by Safeguard.

  • In the delivery reporting you will see:

    • Standard error:
      47 / Message blocked by Safeguard

    • Status error description:
      Used when the message was blocked because of security configuration, please check settings or contact the account manager

Typical situations:

  • Recipient limits – too many messages to the same recipient in a time window (for example, more than 10 messages per day or 1 message per hour).

  • Customer/account limits – too many messages sent by your account in a time window (for example, more than X messages per minute/hour/day).

You can use this information to:

  • Recognize that the message was blocked by Rate Limiting.

  • Review your configured limits in Safeguard and decide whether they match your expected traffic.

  • Adapt your application to:

    • spread traffic more evenly over time, or

    • respect the configured maximum per recipient or per account.


Safeguard Plus / AI Anomaly Detection (AIT Detection)

If you use Safeguard Plus and we detect suspicious or artificially inflated traffic (AIT), Safeguard can monitor or block that traffic depending on your configuration:

When suspicious traffic is blocked:

  • The message is cancelled by Safeguard.

  • In the delivery reporting you will see a status like:

    • Standard error:
      Used when the Safeguard AIT Detection Service determines that the message's trustscore is too low

    • Standard error description:
      85 / The message was blocked by the Safeguard AIT Detection Service because its trust score was below the configured threshold

When suspicious traffic is monitored only:

  • The message is delivered (not cancelled).

  • Safeguard Plus will still generate internal signals that can help us:

    • spot unusual behavior,

    • adjust your configuration,

    • or turn monitoring into blocking if needed.

You can use this information to:

  • Recognize that the message was blocked by AI anomaly detection and not by country, IP, or rate limits.

  • Investigate whether the traffic pattern looks like fraudulent / AIT traffic.