X.7.1 Email Bounce Error [Delivery not authorised, message refused]

4.7.1 Email Bounce Error

Reason

Message Sender Blocked By Receiving Server: Delayed Message

The email message has not yet been delivered because the recipient’s email provider is not accepting messages from this sender. This usually means that the receiving system has security or policy concerns with regard to either the specific sender, recipient, or the sender’s email system.

How to fix?

Retry the email message see if it was a one-time problem or if the same error occurs. Otherwise, contact the sender’s email support team as the email system may have a security issue. This typically requires help-desk support.

4.7.1- Official definition from ITEF

For the code that starts from 4.X.X

A persistent transient failure is one in which the message as sent is valid, but persistence of some temporary condition has caused abandonment or delay of attempts to send the message. If this code accompanies a delivery failure report, sending in the future may be successful.

For the code that starts from X.7.1

The sender is not authorised to send to the destination. This can be the result of per-host or per-recipient filtering. This memo does not discuss the merits of any such filtering, but provides a mechanism to report such. This is useful only as a permanent error.

5.7.1 Email Bounce Error

Reason

Message Sender Blocked By Receiving Server: Message Not Delivered

The message could not be delivered because the recipient’s email provider is not accepting messages from this sender. This usually means that the receiving system has security or policy concerns with regard to either the specific sender, recipient, or the sender’s email system.

How to fix?

Retry the email message see if it was a one-time problem or if the same error occurs. Otherwise, contact the sender’s email support team as the email system may have a security issue. This typically requires help-desk support.

5.7.1- Official definition from ITEF

For the code that starts from 5.X.X

A permanent failure is one which is not likely to be resolved by resending the message in the current form. Some change to the message or the destination must be made for successful delivery.

For the code that starts from X.7.1

The sender is not authorised to send to the destination. This can be the result of per-host or per-recipient filtering. This memo does not discuss the merits of any such filtering, but provides a mechanism to report such. This is useful only as a permanent error.