Internet Mail goes into nobody's SAP Inbox

[Former Member]

Hi

Recently I've find internet mail goes into nobody's SAP Inbox.

I've read SAP note 455140 before and tired GOOGLE but find no similar question and solution.

This issue happens in the domain. I send mail on one PC of the domain, it then delivered by Exchange Server to SAP Application Server. SAP can receive the mail but it goes into nobody's SAP inbox.

I am sure of that because I could find the mail title in table SOOD. However, the owner(receiver) is not the right one or even existed.

Our platform is Netweaver 7.0

Mail Server is MS Exchange Server.

Some information of table SOOD entries.

The Owner A-0000048081 is supposed to be the receiver, but that's not the right SAP ID.

The I-MAILSRM is configured in SICF (SAP Connect) to creat inbound Mail.

Owner type Owner year Owner number Owner User Type User year User number Created

&AD U0 010000048081 A-0000048081 USR 32 000000004800 I-MAILSRM

Definitely we've maintained the profile properly becasue SAP could receive internet mail.

We've also maintained user master by put in E-Mail Address.

I don't know how SAP match the SAP User to Receiver. Does it matter if the User Name in Exchange Server is not the same to SAP User Master?

In our case, I could not accept to use some solution like maitain inbound distribution. That could not fix the abnormal entries in SOOD, and we need the right entries in SOOD.

Has someone meet this kind of issue before? Thanks very much for any information may help.

Best Regards!

Edited by: Changchun Huang on Jan 5, 2009 7:32 AM

[Former Member]

There is an good document which will guide you for an inbound email configuration below is the link.

https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/10dfad5a-5398-2b10-568b-d3d999d4...

Regards,

Sreenivas

[Former Member]

Hi, Sreenivas

Thanks very much for your answer. Definitely it's very helpful. But that is still not full fill my requirement.

There are 6 steps in the manual (it's a good manual with good example, that's pretty good).

The first 4 steps has been described in SAP note 455140, we've go through it.

The step 5 seems to like the standard solution to offline workflow approval config of inbound processing,

I have talked to function team again. However, this is not the same to our case. We developed a program to run at background to select,process and then delete the mail, not put the first step in inbound processing. I think this is not the problem, just another kind of solution.

And the step 6 to define routing rules on MS Exchange server helps me to confirm that it has nothing to do with this case. Since our SAP App Server can received e-mail as I said before.

By the way, How is the comm.Meth, should it be Remote Mail or E-Mail?

How is the user type? Would that impact?

Edited by: Changchun Huang on Jan 6, 2009 1:35 AM

Edited by: Changchun Huang on Jan 6, 2009 2:50 AM

[Former Member]

Hi

It sounds like no SAP User has been identified for the stated SMTP recipient.

Have you maintained SO28 and if so what did you enter? Also check [this|http://help.sap.com/saphelp_nw70/helpdata/EN/55/a8b538891b11d2a25a00a0c943858e/frameset.htm]

You may have to use the distribution list exit to map the SMTP to the SAP USER master programatically. This should solve your problem.

Regards

Gareth

Edited by: Gareth Ellem on Jan 6, 2009 3:05 PM

Edited by: Gareth Ellem on Jan 6, 2009 3:07 PM

[Former Member]

Thanks Gareth

Obviously you've provide a good analysis, however, but that's not for my case.

In my first post, I've declare that we've tried config inbound distribution and it does not work.

And I have to say we are using a system user with user type "service" to receive the workflow offline approval mail.

I've double checked our configuration and compared to both SAP note 455140 and the manual, the most different I think is the user master. Our user type is "service" and communicate method is "E-Mail" not "Remote mail". However, I don't know if that impact. I've no authority to change user master to do test since I am not security guys. If I want to request for a test, I need to make sure if that does matter.

Anyway, thanks very much for your kindly help.

Best Regards!

[Former Member]

Hi Changchun,

Out of my mind.

User type is not a matter; it could be any unless the authorizations matter.

Request to post the trace (you can find at menu u2018Utilitiesu2019 @ SCOT), which may help us in more analysis of the problem. (Check whether trace is switch on for inbound)

(As of SAP Web AS 6.20, each SMTP server has to be activated (Service/Virt. Host  Activate) after being created or changed) I donu2019t know is this applicable to the version of yours, but if possible please.

Regards,

Sreenivas .Y

[Former Member]

Hi, Sreenivas

Below is one trace of inbound mail. I could not find definitely error information. How can I read that? Thanks very much!

PS: I have replaced the real domain name to <domain>.

if_smtp_extension~handle_request G SAPconnect Inbound Processing Started

if_smtp_extension~handle_request G Message Successfully Analyzed According to SMTP/ESMTP

if_smtp_extension~handle_request G Messages ID:

if_smtp_extension~handle_request G Return Coverage for Status Messages: H

if_smtp_extension~handle_request G Length of E-Mail Data Received: 1222

if_smtp_extension~handle_request G Sender First 50 Characters: <Amy_Anselmo@<domain>.com>

if_smtp_extension~handle_request G Recipient of First 60 Chars Plus Status Request (SAPconnect -> BCS)

if_smtp_extension~handle_request G <sapsrpea@srmhau.<domain>.com> (->N)

if_smtp_extension~handle_request G BCS Inbound Processing Will Now Be Called

INBOUND_PROC_ENTRY G INBOUND_PROC_ENTRY: Mime-Parser starten

CL_BCOM_MIME->AS_REFERENCE G MIME Parser Started

CL_BCOM_MIME->AS_REFERENCE G Instance of Type CL_BCOM_MIME_MESSAGE_SMTP Generated

CL.MIME_MESSAGE_SMTP->SET_MIME G Header field name: X-PMWIN-VERSION

CL.MIME_MESSAGE_SMTP->SET_MIME G Header field name: X-MIMEOLE

CL.MIME_MESSAGE_SMTP->SET_MIME G Header field name: RECEIVED

CL.MIME_MESSAGE_SMTP->SET_MIME G Header field name: RECEIVED

CL.MIME_MESSAGE_SMTP->SET_MIME G Header field name: FROM

CL.MIME_MESSAGE_SMTP->SET_MIME G From: Header Addresses

CL.MIME_MESSAGE_SMTP->SET_MIME G Structure: MIME_ADR

CL.MIME_MESSAGE_SMTP->SET_MIME G Header field name: TO

CL.MIME_MESSAGE_SMTP->SET_MIME G To: Header Addresses

CL.MIME_MESSAGE_SMTP->SET_MIME G Structure: MIME_ADR

CL.MIME_MESSAGE_SMTP->SET_MIME G Header field name: DATE

CL.MIME_MESSAGE_SMTP->SET_MIME G Date: Wed, 7 Jan 2009 18:07:55 -0500

CL.MIME_MESSAGE_SMTP->SET_MIME G UTC Time Stamp: 01/07/2009 23:07:55

CL.MIME_MESSAGE_SMTP->SET_MIME G Header field name: SUBJECT

CL.MIME_MESSAGE_SMTP->SET_MIME G Subject: #EBP_GEN_REPLY#Approval of the work item

CL.MIME_MESSAGE_SMTP->SET_MIME G Header field name: THREAD-TOPIC

CL.MIME_MESSAGE_SMTP->SET_MIME G Header field name: THREAD-INDEX

CL.MIME_MESSAGE_SMTP->SET_MIME G Header field name: MESSAGE-ID

CL.MIME_MESSAGE_SMTP->SET_MIME G Message-ID: C58A9FFB.3A00A%Amy_Anselmo@<domain>.com

CL.MIME_MESSAGE_SMTP->SET_MIME G Header field name: ACCEPT-LANGUAGE

CL.MIME_MESSAGE_SMTP->SET_MIME G Header field name: CONTENT-LANGUAGE

CL.MIME_MESSAGE_SMTP->SET_MIME G Header field name: X-MS-HAS-ATTACH

CL.MIME_MESSAGE_SMTP->SET_MIME G Header field name: X-MS-TNEF-CORRELATOR

CL.MIME_MESSAGE_SMTP->SET_MIME G Header field name: ACCEPTLANGUAGE

CL.MIME_MESSAGE_SMTP->SET_MIME G Header field name: CONTENT-TYPE

CL.MIME_MESSAGE_SMTP->SET_MIME G Header field name: CONTENT-TRANSFER-ENCODING

CL.MIME_MESSAGE_SMTP->SET_MIME G Header field name: MIME-VERSION

CL.MIME_MESSAGE_SMTP->SET_MIME G Header field name: RETURN-PATH

CL.MIME_MESSAGE_SMTP->SET_MIME G Header field name: X-ORIGINALARRIVALTIME

INBOUND_PROC_ENTRY G INBOUND_PROC_ENTRY: Mime-Parser succeeded

INBOUND_PROC_ENTRY G Message ID: C58A9FFB.3A00A%Amy_Anselmo@<domain>.com

INBOUND_PROC_ENTRY G SMTP Envelope RCPT TO: sapsrpea@srmhau.<domain>.com

INBOUND_PROC_ENTRY G DSN Request: H

INBOUND_PROC_ENTRY G store_mime: suppressed

INBOUND_PROC_ENTRY G SMTP Envelope MAIL FROM: <Amy_Anselmo@<domain>.com>

INBOUND_PROC_ENTRY G From: Amy_Anselmo@<domain>.com

INBOUND_PROC_ENTRY G To: SAPSRPEA@srmhau.<domain>.com

INBOUND_PROC_ENTRY G Disposition notification: Not requested

INBOUND_PROC_ENTRY G GET_CONTENT_AS_MIME: Successfull

CL_BCOM_MIME->AS_REFERENCE G MIME Parser Started

CL_BCOM_MIME->AS_REFERENCE G Content Type Found: text/plain

CL_BCOM_MIME->AS_REFERENCE G Instance of Type CL_BCOM_MIME_SINGLE_TEXT Generated

CL_BCOM_MIME_SINGLEPART->SET_MIM G CONTENT-TYPE:text/plain

CL_BCOM_MIME_SINGLEPART->SET_MIM G CONTENT-TRANSFER-ENCODING:quoted-printable

CL_DOCUMENT_BCS->BUILD_DOC_TREE G Step: Tree building

CL_DOCUMENT_BCS->MAKE_TEXT_NODE G Content type: Text plain

CL_DOCUMENT_BCS->MAKE_TEXT_NODE G Content information:

CL_SEND_REQUEST_BCS->EXIT_PROCES G EXIT_PROCESSING: Exitprocessing was started

IBND_PROC_POST_DECR G Internal delivery: DELIVER_TO_RECIPIENTS

CL_SEND_REQUEST_BCS->DELIVER_TO_ G RECIPIENT

CL_SEND_REQUEST_BCS->DELIVER_TO_ G Structure: BCSS_RETE

CL_SEND_REQUEST_BCS->DELIVER_TO_ G TRANSF SREQ: N

CL_SEND_REQUEST_BCS->DELIVER_TO_ G SUBMIT: TO ALL

if_smtp_extension~handle_request G BCS Inbound Processing Was Successful. Status Will Now Be Returned

if_smtp_extension_{handle_request G if_smtp_extension}handle_request Will Now Be Exited

[Former Member]

Hi Changchun,

Thanks for the log, did you check whether mail ID "SAPSRPEA@srmhau.<domain>.com" exists for any user account, simple way to check is at table 'adr6' field 'SMTP_ADDR' give the mail ID "SAPSRPEA@srmhau.<domain>.com" pick the personal number from the record and check at table 'adr7' for user ID.

If the "SAPSRPEA@srmhau.<domain>.com" is not for any user the mail may not get delivered.

Also please let me know your Basis version and Patch levels.

Regards,

Sreenivas .Y

[Former Member]

Thanks Sreenivas

I've checked the table ADR6 (for E-Mail Addresses (Business Address Services)) and ADR7 (Remote Mail Addresses (SAP - SAP - Communication; BAS)).

There should be a problem in ADR6 since there are two entries for this user. One if for the upper case character and the other is lower case character. And in SAP User Master, it's lowercase character, but in MS Exchange Server, it's uppercase character. that might be the problem.

Our Basis Version and patch level: SAPKB70013

I appriciate your kindly help very much. I should send mai to request a test. If that pass, I will confirm the result and set this question to be resolved. Thanks very much!

PS: I'm sorry for the late response since I am not in office these two days.

Best Regards!

Edited by: Changchun Huang on Jan 11, 2009 1:18 AM

[Former Member]

please check where the user master record (SU01D) have the same mail ID.

and i believe the upper/lower case should not be a problem.

also check SAP Note 1243419 - Incoming e-mails not transferred to application.

Thanks,

Sreenivas .Y

[Former Member]

Hi, Sreenivas

There is no short dump and program temination in my case. I think there might be something wrong in table ADR6.

There are 5 entries in ADR6 and only 1 entry with Person number 15893 match USR21.

And only this one have the perfect right E-Mail address to user master.

The other 4 entries all have the the same SMTP_SRCH but different SMTP_ADDR. (This was pointed out by my colleague.)

My thought is: if SAP search for the right entry and only pick the first one, this might be the problem. In other words, the point is, how does SAP Address Management work with ADR6. Seems if we send SAP mail with wrong E-Mail address, that would also create entries in ADR6.

Part of data in ADR6:

Client Address number Person number From Sequence number Standard addr. Do not use Home address

010 0000010599 0000015893 0001.01.01 001 X X

010 0000015895 0000048082 0001.01.01 001 X X

010 0000015895 0000048359 0001.01.01 001 X X

010 0000015895 0000048361 0001.01.01 001 X X

010 0000015895 0000082555 0001.01.01 001 X X

Data in USR21:

Client User Person number Address number Cost center Start menu

010 WF-BATCHSRP 0000015893 0000010599 563

Best Regards!

Edited by: Changchun Huang on Jan 12, 2009 8:12 AM

[Former Member]

Thanks Sreenivas

Finally I think your first post has answered my question.

I've made a mistake on understanding the table SOOD.

Below is the response from SAP, I think there are something E-mail address issue between SAP and MS exchange server. And more complicated, the z* program was developed based on this wrong situation.

Dear customer

It is a normal behaviour that there are several addresses with the same

string in the SMTP_SEARCH field within ADR6. To choose the correct

address the following steps are performed. First all addresses with the

same string within SMTP_SEARCH are taken into account (within

SMTP_SEARCH only capital letters are used). In a second step the string

within field SMTP_ADDR is compared with the string which is searched

(field SMTP_ADDR is case sensitive). If they match an address is found

if not the next address is checked.

Hopefully I was able to explain that it is a normal behaviour that

there are several addresses within ADR6 which have the same content in

field SMTP_SEARCH.

2009.02.12 - 16:36:32 AUSWA - Reply by SAP

Dear customer,

your message was forwarded to the next level of support. I will try to

answer your question concerning the owner within table SOOD.

When an e-mail is sent from the outside into the SAP system a SOOD

entry is created for the document. Within the fields OWNTP, OWNYR,

OWNNO and OWNNAM the address number of the sender address is stored.

The recipient is not stored within this field. So it is correct that

the fields are filled in the way you provided within the attached

screenshots. Hopefully this does answer your question concerning the

SOOD table.

I checked also the two entries of table ADR6 which you attached in the

document. You can see that the field SMTP_ADDR looks different (capital

letters versus lower case letters). Therefore two entries for the

'same' address exist within ADR6.

If there are further questions concerning these tables please let me

know.

Best Regards!

Edited by: Changchun Huang on Feb 19, 2009 1:25 AM