In SAP system, we can see some email gets failed with message  with system resources in SOST tcode. Below is in detail about error and solution of that

Error message:
Some emails cannot be sent from the system
In SOST these emails have error status ‘XS838 – No delivery to RECIPIENT due to problems with system resources’ or ‘XS812 – No delivery to RECIPIENT’
The long text of the message shows: 552 5.3.4 Error: message file too big

Cause:
This issue is caused by the size limit settings at mail server level. We know this from the long text of the XS838 error where one can see ‘552 5.3.4 Error: message file too big’.

This is a reply from the mail server and not from the SAP system, we know this from SMTP reply code 552, which means: 552 Requested mail action aborted: exceeded storage allocation

5.X.X Permanent Failure: 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.

X.3.4 Message too big for system: The message is larger than per-message size limit. This limit may either be for physical or administrative reasons. This is useful only as a permanent error.

Solution:
Contact your mail server administrator and ask them to change the mail server size limit settings so the mail server can accept larger mails from the SAP system.

One thought on “No delivery to RECIPIENT due to problems with system Resources

  1. Actually i have a similar error message. Kindly help with resolution.
    —————————————————————————————————————————————————
    No delivery to xyz@abd.co.in
    Message no. XS812
    Diagnosis
    The message was processed correctly in the SAP system. An error occurred in a subsequent system. The message was not delivered to the recipient xyz@abc.co.in
    Information from external system (if available)
    smtp.office364.com:587
    554 5.5.5 Mailbox full. Visit https://aks.ms/mailboxfull for more information.: STOREDRV. Submission

    Please share your comment how to resolve the issue.

Leave a Reply

Your email address will not be published. Required fields are marked *