cancel
Showing results for 
Search instead for 
Did you mean: 

delivery failed message in SCOT

former_member201054
Contributor
0 Kudos


Hi ,

we could able to send mail from SCOT and user receives it. But along with it they get delivery failed message also.

why is the devlivery failed message coming to the user eventhough they get actual message correctly.

Please help me out to resolve the issue.

how to track it down.

Note: Users able to open actual message without an issue

Thanks a ton

0 Kudos

Hi everyone, pls i am new to the group and i need some assistance from you guys.

the below screenshot is the error message i got while trying to install scot on my test environment, pls your option will be well appreciate, thank you all in anticipation.

Former Member
0 Kudos

I saw your posted comment. Please raise a new question and follow our rules of engagement: https://community.sap.com/resources/rules-of-engagement. I suggest using the "I have a similar question" option under the question to get started. Feel free to take our Q&A tutorial at: https://developers.sap.com/tutorials/community-qa.html. With these tips you'll be able to prepare questions that draw responses from our members.

Best,

Your SAP Community moderator

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

Hi,

Follow the note: http://scn.sap.com/docs/DOC-47897

It's been years since I was looking at connections between SAP and MS-Exchange and email send errors.

Which SAP version? Is it MS-Exchange as the SMTP server or something else? If something else, is that ESMTP compliant?

In SCOT, use menu option: "Settings" > "Confirmation of Receipt". It's a fairly self-explanatory screen.

Search SAP documentation for "DSN" (delivery status notification), that's the industry standard term for this functionality. The more popular definition of DSN is data source name (a logical DB identifier), that's not the one you want.

I don't remember if a 'full mailbox' error will come back to SOST with that same error message, or if it will simply indicate 'undeliverable' (and it might vary based on the remote SMTP server type which replied).

Background:

http://email.about.com/library/weekly/aa082597.htm

SAP:

http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/789

http://wiki.sdn.sap.com/wiki/display/Snippets/Read +receipt+and+delivery+receipt+request+from+SAP+for +external+mails

Have you looked at all the send failures (for 1 day as an example) and assessed how many of those would benefit from being resent, as is? What I remember is, almost all email send failures I checked occurred because of a malformed target email address (I've checked 1000s of email/fax send failures in SOST, back in the day). Resending the same malformed item again & again is not going to resolve anything, even if you had an ABAPer code a program that would resubmit failures for you. I'm sure an ABAPer could create such a program, but I'm not aware of any standard functionality that would do the same automatically (of course, you can resend failures manually from within SOST).

BR,

Prabhakar

AtulKumarJain
Active Contributor
0 Kudos

Hi Daniel,

Please check below thread ,it will help you.

https://scn.sap.com/thread/1800291

Best Regards,

Atul

Former Member
0 Kudos

Hi,

Can you please try to put trace in SMICM and see if you record some thing.

So you don't see any issue in SOST.

Thanks

RishI Abrol

Sriram2009
Active Contributor
0 Kudos