If you have access to the transaction code SOST you can monitor incoming and outgoing emails in SAP.
Alternatively you could also use the following transaction codes:
- SOIN BCS: Inbound Send Requests (SMTP)
- SOSG Send Request Overview (Groups)
- SOSB Send Request Overview (Users)
By default SAP shows you the “outgoing emails” sent from SAP.
In the first tab “Period” you can define the period that you want to monitor.
In the Second tab “Send Status” you can choose to only show “Errors”.
If you take a look at such outgoing emails containing an error you will probably see many different error message types.
If you select such an email and press the “glasses”, you see more details:
On the tab “Recipient list” you’ll see the addressee and further below you will see the error messages:
If you click on the error message “No Delivery to xxx as recipient unknown” itself you see more technical details:
If we take a look at the most frequent error messages in our system we identify the following ones:
1. Message no. XS802
No delivery to xxx, as recipient unknown
This means the email address that was used in the field “TO” (recipient) is incorrect.
Potential causes:
- The person you tried to email no longer works at a particular company and therefore the email address is no longer valid
- You made a typo when manually entering the email address (and as such the email address is not valid)
Check: You can use free online services to check whether an email address is a valid one or not. Just do a simple Google search on “Email Validation”
2. Message no. XS838
No delivery XXX due to problems with system resources
Cause: as far as I could see once again an invalid email address entered (wrong domain, or non-existing email address)
3. Message no. XS806
No delivery to XXX, invalid recipient address
Cause: Again, using the email validation tool I only could notice that the email addresses used were BAD (not valid).
4. Message no. XS812
No delivery to XXXX
As far as I could verify, most of the email addresses used were actually valid.
Actually you will see different “subtype errors” if you look at the details, such as:
- 557 Syntax error
- _550 Requested action not taken: mailbox unavailable550 responses typically mean either the users mailbox was unavailable at the time the message delivery was attempted or the mailbox doesn't exist. Try sending the message to the recipient again and see if you get a 550 error. If you receive a 550 message the second time then I would double check with the recipient to make certain that particular mailbox is still active and go from there
- 554 delivery error: dd This user doesn't have a yahoo.com accountThis error message seems to be related to “auto forwarding” to a Yahoo account or the fact that there is a problem
at that time with a Yahoo account itself.
If someone registered with it before but hasn't used it for a while, yahoo disables that account and bounces back all emails sent there.
- 554 5.4.6 Hop count exceeded - possible mail loopI found back some technical information about this, but rather technical:
http://supportweb.ciaops.net.au/blog/archive/2012/06/29/hop-count-exceeded-possible-mail-loop.aspx
Other info found back was:
Why am I getting an "Exceeded Hop count" failure email?
Question Background:
Sometimes I get an exceeded hop count message when I send mail to external email addresses. I have looked at the headers of the message, and it seems to be looping on my mail server, why might this be?
Answer:
if the domain that you are sending the mail to has an incorrect MX record configured, this can cause the problem - specifically if they have an MX record configured to point to the IP address 127.0.0.1
In these circumstances, GMS will look up the address, and then connect to the 127.0.0.1 address to deliver the mail. Because this is the local host IP address, GMS connects to itself and delivers the email. This then results in the mail loop, and the error message "Exceeded hop count".
The problem does not lie with GMS, but rather with the remote server, and as such, you will need to contact the administrator of the remote server to inform them of the problem.
- message size xxx exceeds size limit xxx of serverThis depends on the max message size in SMTP. This is in the System Admin settings under Protocol Settings
- 510 5.1.0 User unknown.
5. Message no. XS802
The message from the node could not be delivered to recipient xxx as the recipient is unknown.
As far as I could verify, this message is also triggered for invalid email addresses that were defined as recipient address.
6. Message no. XS610
Currently no delivery to xxx, as transfer attempt failed
In these cases for some reason the mail could not be sent out yet. I have done several cases where I did perform a “Repeat Send” in SOST.
And then manually triggered the sending
In some cases the email get’s send out correct, in other cases the email will receive another error message (as this time the sending did work, and the feedback error message could be that the email address used is invalid).
7. Message no. XS612
Currently no delivery to XXX
I only had 1 error of this type, but was able to reprocess it, using the “Repeat send” option, and then trigger the sending manually.
8. Message no. XS832
Message in node cannot be processed due to authorization problem
Diagnosis
The node refused message processing.
Procedure
Use the troubleshooting programs of the node to examine the precise cause of the authorization problem. You may need to consult the SAP Hotline or the contact person for the communication system (node) you are using.
At this point I also managed to reprocess those emails, using the “Repeat send” option, and then trigger the sending manually. However, as the actual sending only takes place using the repeat send, once again you might encounter another error message.